forked from cucumber/aruba
-
Notifications
You must be signed in to change notification settings - Fork 2
/
prepend_environment_variable.feature
52 lines (47 loc) · 1.67 KB
/
prepend_environment_variable.feature
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
Feature: Prepend environment variable via "cucumber"-step
It is quite handy to modify the environment of a process. To make this
possible, `aruba` provides several steps. One of these is
`I prepend the values to environment variables:`-step. Using this step prepends
the values. Each variable name and each value is converted to a string.
Otherwise `ruby` would complain about an invalid argument.
Background:
Given I use the fixture "cli-app"
And an executable named "bin/aruba-test-cli" with:
"""
#!/bin/bash
echo $LONG_LONG_VARIABLE
"""
And a file named "features/support/variables.rb" with:
"""
ENV['LONG_LONG_VARIABLE'] = '1'
"""
Scenario: Prepend environment variable by using a step given in table
Given a file named "features/home_variable.feature" with:
"""
Feature: Environment Variable
Scenario: Run command
Given I prepend the values to the environment variables:
| variable | value |
| LONG_LONG_VARIABLE | long_value |
When I run `cli`
Then the output should contain:
\"\"\"
long_value1
\"\"\"
"""
When I run `cucumber`
Then the features should all pass
Scenario: Prepend single environment variable by using a step
Given a file named "features/home_variable.feature" with:
"""
Feature: Environment Variable
Scenario: Run command
Given I prepend "long_value" to the environment variable "LONG_LONG_VARIABLE"
When I run `cli`
Then the output should contain:
\"\"\"
long_value1
\"\"\"
"""
When I run `cucumber`
Then the features should all pass