Sha256: f17ed19d600a849eaa08687fa0ca579efa804a98591a6f9a5b76f87184220338
Contents?: true
Size: 1.43 KB
Versions: 11
Compression:
Stored size: 1.43 KB
Contents
Feature: Tracked request data can be deleted
Background: The MockServer has already got a response for greeting and leaving on it.
Given the following template template:
"""
{
"response":{
"body":"Hello"
}
}
"""
And 'response.body' is base64 encoded
And the template is sent using PUT to 'http://localhost:7001/mirage/templates/greeting'
Given the following template template:
"""
{
"response":{
"body":"Goodbye"
}
}
"""
And 'response.body' is base64 encoded
And the template is sent using PUT to 'http://localhost:7001/mirage/templates/leaving'
And GET is sent to 'http://localhost:7001/mirage/responses/greeting'
And GET is sent to 'http://localhost:7001/mirage/responses/leaving'
Scenario: Deleting all requests
And DELETE is sent to 'http://localhost:7001/mirage/requests'
When GET is sent to 'http://localhost:7001/mirage/requests/1'
Then a 404 should be returned
When GET is sent to 'http://localhost:7001/mirage/requests/2'
Then a 404 should be returned
Scenario: Deleting a stored request for a particular response
And DELETE is sent to 'http://localhost:7001/mirage/requests/1'
When GET is sent to 'http://localhost:7001/mirage/requests/1'
Then a 404 should be returned
When GET is sent to 'http://localhost:7001/mirage/requests/2'
Then a 200 should be returned
Version data entries
11 entries across 11 versions & 1 rubygems