Sha256: 59ca49172a77390a39d9abcb590324c1b363d3d994b4ed71d5d8eee6c550508a

Contents?: true

Size: 566 Bytes

Versions: 11

Compression:

Stored size: 566 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.

  By default mirage runs on port 7001.


  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'

Version data entries

11 entries across 11 versions & 1 rubygems

Version Path
mirage-3.0.0.alpha.11 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.10 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.9 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.8 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.7 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.6 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.5 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.4 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.3 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.2 features/server/commandline_interface/start.feature
mirage-3.0.0.alpha.1 features/server/commandline_interface/start.feature