Skip to content

Commit 5b5b47f

Browse files
authored
Update db-size.feature
1 parent f93c39c commit 5b5b47f

File tree

1 file changed

+0
-8
lines changed

1 file changed

+0
-8
lines changed

features/db-size.feature

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -36,56 +36,48 @@ Feature: Display database size
3636
When I run `wp db size --size_format=b`
3737
Then STDOUT should be a number
3838

39-
4039
Scenario: Display only database size in kilobytes for a WordPress install
4140
Given a WP install
4241

4342
When I run `wp db size --size_format=kb`
4443
Then STDOUT should be a number
4544

46-
4745
Scenario: Display only database size in megabytes for a WordPress install
4846
Given a WP install
4947

5048
When I run `wp db size --size_format=mb`
5149
Then STDOUT should be a number
5250

53-
5451
Scenario: Display only database size in gigabytes for a WordPress install
5552
Given a WP install
5653

5754
When I run `wp db size --size_format=gb`
5855
Then STDOUT should be a number
5956

60-
6157
Scenario: Display only database size in terabytes for a WordPress install
6258
Given a WP install
6359

6460
When I run `wp db size --size_format=tb`
6561
Then STDOUT should be a number
6662

67-
6863
Scenario: Display only database size in Kibibytes for a WordPress install
6964
Given a WP install
7065

7166
When I run `wp db size --size_format=KB`
7267
Then STDOUT should be a number
7368

74-
7569
Scenario: Display only database size in Mebibytes for a WordPress install
7670
Given a WP install
7771

7872
When I run `wp db size --size_format=MB`
7973
Then STDOUT should be a number
8074

81-
8275
Scenario: Display only database size in Gibibytes for a WordPress install
8376
Given a WP install
8477

8578
When I run `wp db size --size_format=GB`
8679
Then STDOUT should be a number
8780

88-
8981
Scenario: Display only database size in Tebibytes for a WordPress install
9082
Given a WP install
9183

0 commit comments

Comments
 (0)