Architecture for test frameworks

Transcript

1. Architecture For test automation frameworks
2. Sven Kroell Testing Toolsmith 5 Years in Automation Working for Novoda Mentoring new Testers Creating tailored solutions @craftingtester 2
3. End to End Integration Unit The pyramid 3
4. Why automate checks? Save time 4 Codebase grows Better risk mitigation People grow tired
5. Record and play 5
6. Tape jam 6
7. Do it yourself 7
9. Time flows by 9 Maintenance hard Duplicated code Devs change locators
10. Repairing on the fly 1 0 Checks get deactivated Hard to understand Red builds Codebase grows
11. How to do it better? 1 1
12. Building a framework 1 2
13. ➡ Separation of concerns ➡ Build a domain language ➡ Keeping the checks simple ➡ Reusable components Why a framework 1 3
14. What went wrong? 1 4 Locators Testdata Userflows Repetitions Magic code Sleeps
16. Think in layers 1 6 Checks Framework Driver Application
17. ➡ Orchestrate the checks ➡ No states ➡ KISS ➡ Using a DSL provided by the framework Checks (Testfiles) 1 7
18. Layers of the Framework 1 8 Checks Driver Repositories Workflows Page Objects Data Generators Data
 Access Objects
19. ➡ Hold the states ➡ Fetch data from api ➡ Trigger builder Repositories 1 9
20. How it could look like 2 0
21. ➡ Centralised data generation ➡ Single point of change ➡ Checks don’t need to know data rules Why repositories? 2 1
22. ➡ Simple DSL ➡ Reusable Flows ➡ Interact via page objects Workflows 2 2
23. How it could look like 2 3
24. ➡ Decouple flows from checks ➡ Checks get cleaner ➡ Using a DSL makes it easier for new joiners to get up to speed Why workflows? 2 4
25. ➡ Holds information about one component of the page ➡ Write and Read from a certain elements Page Objects 2 5
26. How it could look like 2 6
27. ➡ Hides complexity of the DOM from workflows ➡ Single point of change for identifiers Why Page Objects? 2 7
28. Lets have a small demo 2 8
29. ➡ Errors != Faults != Failures ➡ Plan your checks ➡ Work closely with your devs Remarks 2 9
30. ➡ Creating checks is software development ➡ Clean code is very important ➡ A good architecture helps while refactoring Final thoughts 3 0
31. Questions? 3 1 Thank you!