You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running tests, observing the resulting behaviour and then repeating with slight updates to the test data is an excellent way to learn about a system. It'd be nice to support this use-case by adding an interactive testing facility in the assertion components.
When provoked, a test could throw up a GUI that:
Allows a flow or flows to be selected
Allows those flows to be edited
Allows those flows to be processed via the normal test behaviour
Allows multiple repetitions of the above loop
Captures the flow-edit data in the execution report so that if an interesting behaviour is found we've got a record of it so that it can be easily added to the system model.
The text was updated successfully, but these errors were encountered:
Running tests, observing the resulting behaviour and then repeating with slight updates to the test data is an excellent way to learn about a system. It'd be nice to support this use-case by adding an interactive testing facility in the assertion components.
When provoked, a test could throw up a GUI that:
The text was updated successfully, but these errors were encountered: