WixAutomation - Test State Pattern - Selenium Camp 2017
0 likes597 views
The document discusses the challenges of writing stable end-to-end tests, emphasizing issues like limited coverage due to the absence of beta tests. It provides coding snippets to illustrate the implementation of test management features, including conditional test execution based on testing modes. Additionally, it highlights the importance of test state handling to improve testing reliability.
WixAutomation - Test State Pattern - Selenium Camp 2017
- 4. Writing a stable E2E test is difficult
- 5. Why?
- 6. ● ● ●
- 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