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
The Retry feature in the CCK makes it explicit that test runners should not retry execution of UNDEFINED steps. The more general notion is that test runners should not retry test cases for which there is no hope of a successful execution.
✨ What's your proposed solution?
The Retry feature in the CCK should be expanded to include scenarios for PENDING and AMBIGUOUS steps to demonstrate that test runners should not attempt to retry execution of those test cases.
⛏ Have you considered any alternatives or workarounds?
No response
📚 Any additional context?
No response
The text was updated successfully, but these errors were encountered:
🤔 What's the problem you're trying to solve?
The Retry feature in the CCK makes it explicit that test runners should not retry execution of UNDEFINED steps. The more general notion is that test runners should not retry test cases for which there is no hope of a successful execution.
✨ What's your proposed solution?
The Retry feature in the CCK should be expanded to include scenarios for PENDING and AMBIGUOUS steps to demonstrate that test runners should not attempt to retry execution of those test cases.
⛏ Have you considered any alternatives or workarounds?
No response
📚 Any additional context?
No response
The text was updated successfully, but these errors were encountered: