Selenium done right
- 1. Duda Selenium Automation MAIN ASPECTS Aug 2017
- 3. ● About 1500 Selenium tests ● pass rate < 70% ● 3.5 hours for the entire suite ● Once a day ● Maintenance ~ 30% ● No one really cares about automation apart from the QA team ● 2.5 automation developers One Year Ago Now ● Over 3000 Selenium tests ● pass rate > 99% ● Less than 15 minutes for the entire suite ● 30 times a day on different code branches ● Maintenance less than 5% ● Dev is fully committed to keep automation tests clean ● 2.5 automation developers
- 4. What Made The Difference Architecture Change Short Test Flows Stable Tests Only Visualization
- 5. ● Focus on very specific checkpoints: ○ Run faster ○ Easy to debug ○ The failure is clear ● Api or other shortcuts usage for peripheral functions: ○ Get to the required condition via fastest and safest way ● Avoid using complicated flows ○ Only if absolutely a must ○ Avoid test dependencies Atomic Test Flows
- 6. ● Testing the new tests: ○ All new tests shall run successfully on a sanbox 30 times in a row ○ All tests must pass ○ Runtime < 200 sec per class ● Code Review: ○ Code review meeting with automation team ● Only after sandbox and code review, new tests are added to “production” XML (Very) Stable Tests Only
- 7. Visualize – Jenkins Pipeline
- 8. Visualize – Automation Dashboard
- 9. ● Short Test Flows ● Stable Tests Only ● Visualization/Immediate Feedback Wrapping Up
- 10. Selenium Done Right WWHB Design pattern
- 11. About me
- 12. UI Testing Weakness Bad selectors Scattered UI flow Bad waits and sleeps Tests prioritized Obfuscated code in tests Bad log report The small things video Asynchronous Browser Opening video
- 13. ● Automation tests are not scripts - they’re software. ● A software project should have a good design and architecture to overcome future challenges. ● The software developing team should be devoted to maintain a high quality code standard. ● “The chain is strong as its weakest link” ● It’s not enough if it works Automation Is Software
- 14. Like a glove
- 15. ● Clean code should be simple and direct ● Clean code should read like well written prose ● Clean code is when each routine you read is pretty much what you’ve expected ● A function should do one thing, it should do it well and it should do it only ● Clean code always looks like it was written by someone who cares Clean Code Robert Cecil Martin a.k.a Uncle bob
- 16. ● Selector properties ○ Unique ○ Meaningful ○ Low chance of change ● Be the change Selectors & API’s
- 17. WWHB Design Pattern ● What to test ● Where to find the elements ● How to execute the test ● The Browser
- 18. ● What: @Test ● Best practices ○ Small atomic tests - no priority ○ Setups and teardowns in every @Test ○ Think small - every function should be well thought of. In Assert use contains, toLowerCase… ○ Minimal logic in tests, only well written prose ○ Minimal global variables ● Measure your code ○ Test score system: url ○ Old navigation test: url ○ New navigation test: url What
- 19. ● Where: Page Objects ● In test findBy() -> elementfinder class per test -> @FindBy -> enum - > public static class ● Best practice ○ Minimal logic in page objects - only simple actions ○ No cross page object function calls Where THIS IS HUGE!!
- 20. ● How: Logics ● Structure of logics and inheritance ● Obstacles solved as part of the infrastructure, not ad hoc per test (publishSite, setText, Hover, importTemplates) How
- 21. BROWSE R TOUCHER ● The browser is the enemy - no one is doing element.click() element.getCssValue() driver.get() driver.findElement(by) …… Browser THIS IS ALSO HUGE!!!! Test suit
- 22. ● The browser is the enemy - no one is doing element.click() element.getCssValue() driver.get() driver.findElement(by) …… Browser BROWSE R TOUCHER Test suit
- 24. ● Extra: ● Smart waits and ExpectedCondition + stopwatch ● Static functions - no side effects ● Testng-failed.xml for retry ● Sandbox with test randomizer ● FocusOnIframe - open close principle Extra topics
- 25. ● Automation is software ● Clean code ● WWHB design pattern Conclusion
- 26. Thank You!