Sha256: e1215bf637d8c2461cd8fa8078f0f64b8a08c0c7bb217e7d4f63a4d40728b9ca
Contents?: true
Size: 1.47 KB
Versions: 11
Compression:
Stored size: 1.47 KB
Contents
@command_line
Feature:The client API can be used to stop instances of Mirage running on localhost.
Background:
Given the following require statements are needed:
"""
require 'rubygems'
require 'mirage/client'
"""
Scenario: Stopping Mirage
Given Mirage is running
When I run
"""
Mirage.stop
"""
Then Connection should be refused to 'http://localhost:7001/mirage'
Scenario: Stopping Mirage on custom port
And I run 'mirage start -p 9001'
When I run
"""
Mirage.stop :port => 9001
"""
Then mirage should not be running on 'http://localhost:9001/mirage'
Scenario: Stopping multiple instances of Mirage
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 :port => [9001,10001]
"""
Then mirage should be running on 'http://localhost:7001/mirage'
Then mirage should not be running on 'http://localhost:9001/mirage'
Then mirage should not be running on 'http://localhost:10001/mirage'
Scenario: Stopping all instances of Mirage
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 :all
"""
Then mirage should not be running on 'http://localhost:7001/mirage'
Then mirage should not be running on 'http://localhost:9001/mirage'
Then mirage should not be running on 'http://localhost:10001/mirage'
Version data entries
11 entries across 11 versions & 1 rubygems