Open perdasilva opened 2 years ago
Although it does not happen very often it may be worth considering in the process that a test may not have been borne but may become flaky due to changes made to the code base (introduction of a race condition or something blocking the deletion of a resource or the tear-down of the environment).
Description
As a maintainer or contributor I don't want to have to keep dealing with flaky tests and I also don't want to introduce any new flaky tests. We should have a process whereby is e2e tests are added or changed we'd need to have a no-flake certification
Acceptance Criteria
make flake-detection test1 test2 test3 --pr=1234
)