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
|
Feature: Delete existing environment variable via API-method
It is quite handy to modify the environment of a process. To make this
possible, `aruba` provides several methods. One of these is
`#delete_environment_variable`. Using this remove an existing variable.
Background:
Given I use the fixture "cli-app"
Scenario: Non-existing variable
Given a file named "spec/environment_spec.rb" with:
"""ruby
require 'spec_helper'
RSpec.describe 'Long running command', :type => :aruba do
before(:each) { delete_environment_variable 'LONG_LONG_VARIABLE' }
before(:each) { run_command('env') }
before(:each) { stop_all_commands }
it { expect(last_command_started.output).not_to include 'LONG_LONG_VARIABLE=1' }
end
"""
When I run `rspec`
Then the specs should all pass
Scenario: Existing variable set from within the test
Given a file named "spec/environment_spec.rb" with:
"""ruby
require 'spec_helper'
RSpec.describe 'Long running command', :type => :aruba do
before(:each) { set_environment_variable 'LONG_LONG_VARIABLE', '1' }
before(:each) { delete_environment_variable 'LONG_LONG_VARIABLE' }
before(:each) { run_command('env') }
before(:each) { stop_all_commands }
it { expect(last_command_started.output).not_to include 'LONG_LONG_VARIABLE' }
end
"""
When I run `rspec`
Then the specs should all pass
Scenario: Existing variable set by some outer parent process
Given a file named "spec/environment_spec.rb" with:
"""ruby
require 'spec_helper'
ENV['REALLY_LONG_LONG_VARIABLE'] = '1'
RSpec.describe 'Environment command', :type => :aruba do
before(:each) { delete_environment_variable 'REALLY_LONG_LONG_VARIABLE' }
before(:each) { run_command('env') }
before(:each) { stop_all_commands }
it { expect(last_command_started.output).not_to include 'REALLY_LONG_LONG_VARIABLE' }
end
"""
When I run `rspec`
Then the specs should all pass
|
