Automation patterns on practice
- 1. Presented by: MykolaKolisnyk1Automation Patterns on Practice. Automation Architecture creation.
- 2. What’s it all about?Framework structure
- 5. Behavioral patterns in automationFramework is the core06.02.11LibrariesTestsEngineConfigsReportingResourcesCore components
- 11. Run()List ofActionClassRun()for each Test in this.Testsfor each Action in Test.ActionsAction.Run()
- 13. Behavior-drivenText instructionWhenI log into the system as “login”/”password”Actual CodeWhen/log into the system as “(.*)”\/”(.*)”/do|login,password|app.login( login , password )endclass Appdef login( username , password )# Some actionsendend
- 14. Model-based frameforkAction 0-1Action 0-1Initial stateAction 5-1State 1State 5Action 1-1Action 2-2Action 2-1State 2State 4Action 0-1State 3Action 3-1Final State
- 15. Patterns06.02.11
- 16. What does pattern mean?06.02.11Pattern is a typical solution for typical task
- 17. Global Objects06.02.11Should be only one in the system
- 18. Should be initialized only once
- 19. Should not be modified from outsideEngine driverConfig
- 20. Singleton06.02.11Local instancePrivate constructorAll operations are done via local instance
- 21. Immutable & Lazy initialization06.02.11Filled only during initializationInitialized at first method call
- 22. Engine-specific patterns06.02.11Each unit implementation should be abstracted from interface
- 23. Units should represent actual command to executeEngine driverNOTE: applicable for Object-based, Keyword-Driven, Behavior-driven, Model-based approaches
- 24. Command & Interface & Delegate06.02.11Common interface for each class (Interface)Object represents the action (Command)ActionClassARun()TestClassActions
- 25. Run()List ofActionClassRun()ActionClassBRun()ActionClassCRun()Actual execution is delegated to aligned class objects (Delegate)
- 27. Resource-specific patterns06.02.11Resource should represent logical structure rather than physical
- 28. If engine driver is used it should be used implicitlyResources
- 29. Page object06.02.11Objects functionality is extended via external class (Decorator/Wrapper)
- 30. Page Factory06.02.11Implicit page object initializationUsage example:
- 32. Big ball of mud06.02.11
- 33. God object06.02.11Too much methods in one class
- 34. Hard & Soft Coding06.02.11Magic numbersConfiguration hell
- 35. Dependency hell06.02.11Test 8Test 1Test 7Test 9Test 2Test 6Test 3Test 5Test 4
- 36. Summary“Framework”, “pattern”, “architecture” are not magic spellsFramework identifies how we structure overall solutionEach framework type uses specific set of patternsPattern is the solution for specific task Good solution is the balance between complexity and simplicity06.02.11