Specify timeout for runShell commands

[JakeSCahill]

runShell commands execute shell commands as part of test scenarios. However, some commands may enter a state where they wait indefinitely for input or a specific condition that does not occur, leading to stalled test executions. This behavior impacts the overall testing workflow, especially in CI/CD environments where automated tests are expected to run to completion within a reasonable timeframe.

Proposed solution
Introduce an optional timeout parameter for runShell test actions. This parameter defines a maximum duration (in seconds) for a test to run. If the command does not complete within the specified timeout, it will be automatically terminated, and the test will proceed based on the predefined failure handling strategy.

// (step {"action":"runShell", "command": "some-long-running-command", "timeout": 60})

Benefits

• Prevents tests from hanging indefinitely.

• Allows test writers to fine-tune the execution behavior of shell commands based on their understanding of the command's expected duration and behavior.

• Reduces the risk of stalled pipeline executions due to hanging tests, contributing to more predictable and efficient CI/CD workflows.

[hawkeyexl]

Accepted. Timeout will likely be in milliseconds to match other timeout/duration parameters in other actions, but the schema matches otherwise.

[hawkeyexl]

Will be available in v2.14.0.