Step mocking

[hawkeyexl]

Sometimes users don't want to directly trigger an action, such as making an API call that costs money, but they still want to perform the rest of the resulting test. In this case, it might make sense to allow individual steps to mock aspects of their responses, either predefined or based on historical responses. We already support limited mocking of httpRequest actions based on OpenAPI definitions, so the general behavior is already present in the project.

Additionally, users may want to configure how often to actually perform the action to occasionally check that the step indeed does perform as intended.

Steps that could benefit from mocking include:

• httpRequest: response body, response headers, status code
• runShell: stdout, stderr, exitCode
• runCode: stdout, stderr, exitCode