Sha256: 96459682ff8599927f7c0c0efec857f7b1db91a28e70365635ca9c94ff1bc342
Contents?: true
Size: 1.75 KB
Versions: 4
Compression:
Stored size: 1.75 KB
Contents
@command_line
Feature: stop
Scenario: Calling stop without specifying the port when only one instance is running
Given I run 'mirage start -p 7001'
When I run 'mirage stop'
Then mirage should not be running on 'http://localhost:7001/mirage'
Scenario: Calling stop without specifying the port when more than one instance is running
Given I run 'mirage start -p 7001'
Given I run 'mirage start -p 9001'
When I run 'mirage stop'
Then I should see 'Mirage is running on ports 7001, 9001. Please run mirage stop -p [PORT(s)] instead' on the command line
And mirage should be running on 'http://localhost:7001/mirage'
And mirage should be running on 'http://localhost:9001/mirage'
Scenario: stopping on a single instance
Given I run 'mirage start -p 7001'
And I run 'mirage start -p 9001'
When I run 'mirage stop -p 7001'
Then mirage should be running on 'http://localhost:9001/mirage'
Then mirage should not be running on 'http://localhost:7001/mirage'
Scenario: stop more than one instance
Given I run 'mirage start -p 7001'
And I run 'mirage start -p 9001'
And I run 'mirage start -p 10001'
When I run 'mirage stop -p 7001 9001'
Then mirage should be running on 'http://localhost:10001/mirage'
Then mirage should not be running on 'http://localhost:7001/mirage'
Then mirage should not be running on 'http://localhost:9001/mirage'
Scenario: stop all instances
Given I run 'mirage start -p 7001'
And I run 'mirage start -p 9001'
When I run 'mirage stop -p all'
Then mirage should not be running on 'http://localhost:10001/mirage'
Then mirage should not be running on 'http://localhost:7001/mirage'
Then mirage should not be running on 'http://localhost:9001/mirage'
Version data entries
4 entries across 4 versions & 1 rubygems