Sha256: 48bff009dcd86712452d602465251e4ee2c54ba0c4cbc20d33a1392c551af7da
Contents?: true
Size: 1013 Bytes
Versions: 4
Compression:
Stored size: 1013 Bytes
Contents
@command_line
Feature: Mirage is started from the command line.
more than instance of Mirage can be started on different ports at the same time.
Scenario: Starting mirage
Given Mirage is not running
When I run 'mirage start'
Then mirage should be running on 'http://localhost:7001/mirage'
And 'mirage.log' should exist
Scenario: Starting Mirage on a custom port
Given Mirage is not running
When I run 'mirage start -p 9001'
Then mirage should be running on 'http://localhost:9001/mirage'
Scenario: Starting multiple instances of Mirage
Given Mirage is not running
When I run 'mirage start -p 7001'
And I run 'mirage start -p 9001'
Then mirage should be running on 'http://localhost:7001/mirage'
And mirage should be running on 'http://localhost:9001/mirage'
Scenario: Starting Mirage when it is already running
Given Mirage is running
When I run 'mirage start -p 7001'
Then I should see 'Mirage is already running' on the command line
Version data entries
4 entries across 4 versions & 1 rubygems