Page objects: the good, the bad, the ugly
Download as PPTX, PDF0 likes49 views
The document discusses page objects in software testing, emphasizing the need for clean, maintainable code that is human-readable and conveys intent. It highlights best practices like meaningful naming and the DRY principle while addressing the complications of complex page objects. The content concludes with recommended resources for further reading on automated testing and page object design.
Page objects: the good, the bad, the ugly
- 1. PAGE OBJECTS THE GOOD, THE BAD, AND THE UGLY
- 2. WHO AM I? • DAWN CODE, INDESCRIBABLE! • COMP SCI DEGREE FROM CLEMSON, 2001 • TESTER -> PROGRAMMER -> TESTER • LIFELONG LEARNER • MACHINE LEARNER • CURRENTLY QUALITY ENGINEERING MANAGER AT IBM WATSON HEALTH CLINICAL DEVELOPMENT
- 3. IS TEST AUTOMATION CODE REAL CODE? SHOULD AUTOMATION CODE BE WRITTEN FOLLOWING THE SAME CONVENTIONS AS PRODUCTION DEVELOPERS WRITING PRODUCTION CODE?
- 5. DOES THAT MEAN WE SHOULD IGNORE ALL CLEAN CODING PRACTICES? OF COURSE NOT
- 6. THE HAPPY MEDIUM • NO NEED TO GET INTO DEEP, TECHNICAL, PROGRAMMING CONCEPTS • ALSO WE DO NOT WANT TO END UP WITH A PROJECT THAT COSTS MORE TO MAINTAIN THAN IT IS WORTH TO EXECUTE • TESTERS CAN START WITH SOME SMALL PRACTICES THAT WORK TOWARD CLEAN, MAINTAINABLE, CODE
- 7. MAKE CODE HUMAN READABLE • CODE IS READ BY HUMANS, NOT COMPUTERS • CODE SHOULD CONVEY INTENT • NAMES SHOULD BE MEANINGFUL • NAMES SHOULD NOT BE ABBREVIATED
- 9. HOW COULD WE MODIFY THIS?
- 10. MAYBE LIKE THIS?
- 11. DRY: DON’T REPEAT YOURSELF • IF YOU FIND THAT YOU DO IT MORE THAN ONCE, PULL IT OUT INTO A SEPARATE METHOD • IF YOU FIND THAT YOU ARE COPYING AND PASTING CODE, CONSIDER HOW MUCH YOU ARE REPEATING YOURSELF
- 12. WHAT HAPPENS THE NEXT TIME WE WANT TO OPEN THAT EXCEL SPREADSHEET?
- 14. WHAT ABOUT WHEN ANOTHER USER NEEDS TO PUT THEIR OWN PATH IN?
- 16. WHAT ABOUT WHEN WE NEED TO INSERT A SHEET AS SHEET 1 IN THESE EXCEL FILES?
- 18. EVEN BETTER …
- 19. CLEAN CODE FOR TESTERS • NAME ALL VALUES WITH MEANINGFUL, RELEVANT, HUMAN-READABLE NAMES • DON’T REPEAT YOURSELF
- 20. GET STARTED WITH SELENIUM • HTTP://WWW.SELENIUMHQ.ORG/DOCS/03_WEBDRIVER.JSP
- 22. IN THIS MODEL … https://udayhere.files.wordpress.com/2012/06/testautomation1.jpg
- 23. WHAT DO WE INTEND TO MODEL?
- 24. MAYBE MORE LIKE THIS?
- 26. WHY USE PAGE OBJECTS? • CLEAN SEPARATION BETWEEN TEST CODE AND PAGE SPECIFIC CODE • REDUCE/REMOVE DUPLICATION FOR OBJECT LOCATION AND INTERACTION • TEST STEPS HAVE MORE MEANINGFUL NAMES ABOUT WHAT THE TEST IS ACTUALLY DOING
- 27. PAGE OBJECT PATTERNS • GROWING PAGE OBJECTS ORGANICALLY • SELF-VERIFICATION • BUILT-IN NAVIGATION • NO ASSERTIONS IN THE PAGE OBJECT • PRIVATE ELEMENTS IN PAGE OBJECT
- 28. WHAT GOES WRONG? • MOST OF IT IS ABOUT SCALING • FIRST: WHAT IS A “PAGE”, ANYWAY? • LARGE AND COMPLEX PAGE OBJECTS • NAVIGATION? • IT DOES REQUIRE HIGHER LEVEL OF PROGRAMMING KNOWLEDGE • PAGE OBJECT REPO IS HIGHLY APPLICATION SPECIFIC
- 29. WHAT ARE YOUR EXPERIENCES?
- 30. FOR FURTHER READING • WRITING MAINTAINABLE AUTOMATED TESTS, BY DALE EMERY • HTTPS://MARTINFOWLER.COM/BLIKI/PAGEOBJECT.HTML • HTTPS://GITHUB.COM/SELENIUMHQ/SELENIUM/WIKI/PAGEOBJECTS • HTTP://WWW.SELENIUMHQ.ORG/DOCS/06_TEST_DESIGN_CONSIDERATIONS.JSP