-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scenario Values & Reading from Response #178
base: master
Are you sure you want to change the base?
Conversation
I'm using mmock and would like to have a feature that automatically sets the scenario name from the request information, so when is this PR likely to be released? |
This PR did not support replacement tags in the scenario name, but now it does. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #178 +/- ##
==========================================
- Coverage 66.95% 64.27% -2.69%
==========================================
Files 26 30 +4
Lines 1153 1839 +686
==========================================
+ Hits 772 1182 +410
- Misses 330 587 +257
- Partials 51 70 +19 ☔ View full report in Codecov by Sentry. |
7023354
to
06a1a75
Compare
There are use scenarios that require a random value is generated and sent in the
response in one state, and the same value is returned in a future state.
To make this possible a couple of things had to happen.
- a new response filler has been created
-
{{response.body.*}}
-
{{response.cookie.*}}
-
{{response.header.*}}
- this is the same approach that streams uses
-
{{scenario.*}}