Tom
01/16/2023, 2:29 PMJSESSIONID
as an element, you’ll get a unique state machine for every value of the session key, rather than a single global state machine (for this scenario).
I contemplated just making the scenario key templated, but realised it might be good in future to be able to retrieve scenarios by name via the API and see a breakdown by session/token/whatever. So I think the additional key elements should be a list of request parameter types/keys.
So, the JSON API would look something like this:
{
"scenarioName": "To do list",
"requiredScenarioState": "Started",
"scenarioStateKey": [{
"type": "cookie",
"name": "JSESSIONID"
}],
"request": {
"method": "GET",
"url": "/todo/items"
},
"response": {
"status": 200,
"body": "...
}
}
Have any of you experienced this particular issue before?
If so, do you think this be a good solution?Rob Elliot
01/16/2023, 3:11 PMTom
01/16/2023, 3:12 PMRob Elliot
01/16/2023, 3:13 PMscenarioStateKey
- do you expect that to be necessary?Tom
01/16/2023, 3:15 PM"scenarioSessionKey": { "type": "cookie": "name": "JSESSIONID" }
Rob Elliot
01/16/2023, 3:17 PM"scenarioSessionKeys": []
and the former would become a shorthand for the latter with one key.Tom
01/16/2023, 3:21 PM