Sha256: 758de3303fde1c0e9f8764e74f0921579027aac27029d2a5ed8b84428961f1a2
Contents?: true
Size: 1.16 KB
Versions: 15
Compression:
Stored size: 1.16 KB
Contents
#TODO - rename responses directory to templates
@command_line
Feature: Preloading Templates
Mirage can be primed with a set of templates.
By default, Mirage loads any .rb files found in ./mirage on startup. Mirage can also be made to load responses from a directory
of your choosing by using the -d/--defaults option
Responses can be added to the responses directory and used to prime Mirage after Mirage has been started.
Priming causes any modifications to Mirage's current state to be lost.
Scenario: Using the default responses directory
Given the file 'mirage/default_greetings.rb' contains:
"""
prime do |mirage|
mirage.templates.put('greeting', 'hello')
end
"""
And I run 'mirage start'
When GET is sent to '/responses/greeting'
Then 'hello' should be returned
Scenario: Using a custom responses directory
Given Mirage is not running
And the file '/tmp/mirage/default_greetings.rb' contains:
"""
prime do |mirage|
mirage.templates.put('greeting', 'hello')
end
"""
And I run 'mirage start --defaults /tmp/mirage'
And GET is sent to '/responses/greeting'
Then 'hello' should be returned
Version data entries
15 entries across 15 versions & 2 rubygems