Would be good to have a better way for e2e to clean up after itself when things fail in Cx1.
Example:
- scan is stuck and cancelled by e2e
- cancellation fails due to some backend issue, disconnect etc
- delete-project fails due to a still-running stuck scan
Possible solutions:
- retry-on-fail for any test, with optional delay?
- filters on the executable to allow only specific test types similar to the current engine-filter flag
- end-of-test cleanup phase that reruns read,delete statements? or tracks failed delete operations for specific retry? (scan-cancellation success response doesn't guarantee scan cancellation)
Would be good to have a better way for e2e to clean up after itself when things fail in Cx1.
Example:
Possible solutions: