Support not replying to every prompt in a scripted client prompt-sequence.
Currently, prompting-client.scripted accepts scripts which have a top-level "prompt-filter" and a "prompts" list, which is a list of json objects with two mandatory fields: "prompt-filter" and "reply". The scripted client expects relevant prompts to match the filters specified in the "prompts" list in order, and for each one, immediately sends back the accompanying reply.
However, to write a spread test which mimics the create_multiple_actioned_by_other_pid integration test, we need to be able to attempt multiple writes (and check that those attempts occurred as expected), and then on a subsequent attempt, reply with a rule which then actions the previous prompts as well.
The docs update and new test data cover the new supported syntax for a prompt-sequence.
Support not replying to every prompt in a scripted client prompt-sequence.
Currently, prompting-client.scripted accepts scripts which have a top-level "prompt-filter" and a "prompts" list, which is a list of json objects with two mandatory fields: "prompt-filter" and "reply". The scripted client expects relevant prompts to match the filters specified in the "prompts" list in order, and for each one, immediately sends back the accompanying reply.
However, to write a spread test which mimics the
create_multiple_actioned_by_other_pidintegration test, we need to be able to attempt multiple writes (and check that those attempts occurred as expected), and then on a subsequent attempt, reply with a rule which then actions the previous prompts as well.The docs update and new test data cover the new supported syntax for a prompt-sequence.
Tracked internally by https://warthogs.atlassian.net/browse/UDENG-4782