With more breaking points and less stability, E2E tests are very hard to maintain. The automation guild at WixEngineering have reduced the amount of flaky tests by utilizing what we define as the “Test State Pattern”, where every test transitions between states according to its behavior.

4. Writing a stable E2E test is difficult

5. Why?

6. ●
●
●

8. @Test
@Test
@Test

10. No Beta tests -
Less coverage

11. @BetaTest(owner = "tzipi")
public void newTest() {
…
}

13. Run X times
per night

14. @Override
public void beforeTest(Description description) {
if (isBetaTestInReleaseRunMode(description) ||
isNonBetaTestInBetaRunMode(description)) {
TestUtils.ignoreTest();
}
}

25. @Override
public void beforeTest(Description description) {
TestState state = getTestState(description);
if (isBetaTestInReleaseRunMode(description, state) ||
isNonBetaTestInBetaRunMode(description, state)) {
TestUtils.ignoreTest();
}
}

36. DB

37. 1 n