-
Notifications
You must be signed in to change notification settings - Fork 27
Expand file tree
/
Copy pathsteps.feature
More file actions
86 lines (66 loc) · 2.75 KB
/
steps.feature
File metadata and controls
86 lines (66 loc) · 2.75 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
Feature: Make sure "Given", "When", "Then" steps work as expected
Scenario: Variable names can only contain uppercase letters, digits and underscores and cannot begin with a digit.
When I run `echo value`
Then save STDOUT as {VARIABLE_NAME}
And save STDOUT as {V}
And save STDOUT as {_VARIABLE_NAME_STARTING_WITH_UNDERSCORE}
And save STDOUT as {_}
And save STDOUT as {VARIABLE_NAME_WITH_DIGIT_2}
And save STDOUT as {V2}
And save STDOUT as {_2}
And save STDOUT as {2_VARIABLE_NAME_STARTING_WITH_DIGIT}
And save STDOUT as {2}
And save STDOUT as {VARIABLE_NAME_WITH_lowercase}
And save STDOUT as {v}
# Note this would give behat "undefined step" message as "save" step uses "\w+"
#And save STDOUT as {VARIABLE_NAME_WITH_PERCENT_%}
When I run `echo {VARIABLE_NAME}`
Then STDOUT should match /^value$/
And STDOUT should be:
"""
value
"""
When I run `echo {V}`
Then STDOUT should match /^value$/
When I run `echo {_VARIABLE_NAME_STARTING_WITH_UNDERSCORE}`
Then STDOUT should match /^value$/
When I run `echo {_}`
Then STDOUT should match /^value$/
When I run `echo {VARIABLE_NAME_WITH_DIGIT_2}`
Then STDOUT should match /^value$/
When I run `echo {V2}`
Then STDOUT should match /^value$/
When I run `echo {_2}`
Then STDOUT should match /^value$/
When I run `echo {2_VARIABLE_NAME_STARTING_WITH_DIGIT}`
Then STDOUT should match /^\{2_VARIABLE_NAME_STARTING_WITH_DIGIT}$/
And STDOUT should contain:
"""
{
"""
When I run `echo {2}`
Then STDOUT should match /^\{2}$/
When I run `echo {VARIABLE_NAME_WITH_lowercase}`
Then STDOUT should match /^\{VARIABLE_NAME_WITH_lowercase}$/
When I run `echo {v}`
Then STDOUT should match /^\{v}$/
Scenario: Special variables
When I run `echo {INVOKE_WP_CLI_WITH_PHP_ARGS-} cli info`
Then STDOUT should match /(wp|wp\.bat) cli info/
And STDERR should be empty
When I run `echo {WP_VERSION-latest}`
Then STDOUT should match /\d\.\d/
And STDERR should be empty
Scenario: Nested special variables
Given an empty directory
When I run `echo {INVOKE_WP_CLI_WITH_PHP_ARGS--dopen_basedir={RUN_DIR}} cli info`
Then STDOUT should match /^WP_CLI_PHP_ARGS=-dopen_basedir=.* ?wp cli info/
And STDERR should be empty
When I run `echo {INVOKE_WP_CLI_WITH_PHP_ARGS--dopen_basedir={RUN_DIR}} eval 'echo "{RUN_DIR}";'`
Then STDOUT should match /^WP_CLI_PHP_ARGS=-dopen_basedir=(.*)(.*) ?wp eval echo "\1";/
@require-mysql-or-mariadb
Scenario: SQL related variables
When I run `echo {MYSQL_BINARY}`
Then STDOUT should match /(mysql|mariadb)/
When I run `echo {SQL_DUMP_COMMAND}`
Then STDOUT should match /(mysqldump|mariadb-dump)/