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 current behavior for when a test phase exceeds a configured timeout is that the phase result itself is reported as TIMEOUT and the entire test is aborted. There are instances where one may want to execute subsequent test phases even when a timeout for a previous phase occurs.
Therefore, propose adding a parameter to determine the behavior for a test phase when its timeout is triggered. The default behavior can still be to abort the test, but an option should be added to continue to the next phase. The phase that timed out can still be marked as TIMEOUT.
The text was updated successfully, but these errors were encountered:
The current behavior for when a test phase exceeds a configured timeout is that the phase result itself is reported as TIMEOUT and the entire test is aborted. There are instances where one may want to execute subsequent test phases even when a timeout for a previous phase occurs.
Therefore, propose adding a parameter to determine the behavior for a test phase when its timeout is triggered. The default behavior can still be to abort the test, but an option should be added to continue to the next phase. The phase that timed out can still be marked as TIMEOUT.
The text was updated successfully, but these errors were encountered: