Sha256: dda1659d7338108762840094ab37e51ca19e45b85f481831e36af6032c2cb80d
Contents?: true
Size: 1.08 KB
Versions: 10
Compression:
Stored size: 1.08 KB
Contents
@command_line
Feature: Mirage is started from the command line.
Mirage logs to mirage.log at the path where Mirage is started from
Background: Mirage usage
Given usage information:
| Usage: mirage start\|stop [options] |
| -p, --port PORT |
| -d, --defaults DIR |
Scenario: Starting with help option
Given I run 'mirage start --help'
Then the usage information should be displayed
Scenario: Starting with an invalid option
Given I run 'mirage start --invalid-option'
Then the usage information should be displayed
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: Stopping Mirage
Given I run 'mirage start'
When I run 'mirage stop'
Then Connection should be refused to 'http://localhost:7001/mirage'
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'
Version data entries
10 entries across 10 versions & 1 rubygems