#
# Copyright (c) 2015-2017 Steven Soloff
#
# This is free software: you can redistribute it and/or modify it under the
# terms of the MIT License (https://opensource.org/licenses/MIT).
# This software comes with ABSOLUTELY NO WARRANTY.
#

Feature: Correlating requests and responses
  In order to know which request triggered a specific response
  As a tool developer
  I want the response to specify the originating request ID as its correlation ID

Scenario: Correlating requests and responses
  Given a request with the ID "aaaa-bbbb-cccc"
    And a request with the expression "5"
  When the evaluate expression service is invoked
  Then the response should contain the correlation ID "aaaa-bbbb-cccc"

#
# Copyright (c) 2015-2017 Steven Soloff
#
# This is free software: you can redistribute it and/or modify it under the
# terms of the MIT License (https://opensource.org/licenses/MIT).
# This software comes with ABSOLUTELY NO WARRANTY.
#

Feature: Correlating requests and responses
  In order to know which request triggered a specific response
  As a tool developer
  I want the response to specify the originating request ID as its correlation ID

Scenario: Correlating requests and responses
  Given a request with the ID "aaaaabbbbbcccccddddd"
    And a request with the expression "5"
  When the evaluate expression service is invoked
  Then the response should contain the correlation ID "aaaaabbbbbcccccddddd"

Change request ID used in acceptance tests
Change request ID used in acceptance tests

Running the "Correlating requests and responses" feature against Heroku
will fail if the request ID does not follow their rules.  Otherwise,
Heroku will ignore the request ID and inject their own.

We were violating the minimum length rule (20 characters).  The tests
have been updated to use a request ID that exceeds this minimum length.
