Как надо правильно строить автоматизацию тестирования с нуля, что нужно применять, а то не нужно применять при проектировании архитектуры. Какие виды фреймворков бывают, что с ними надо делать. Все и много другое вы сможете найти в этой презентации

1. Presented by: MykolaKolisnyk 1 Automation Patterns on Practice. Automation Architecture creation.

3. Framework types

4. Design patterns

6. Framework types 06.02.11 Functional decomposition Object-based Data-driven Keyword-driven Behavior-driven Model-based Hybrid

7. Functional Decomposition

8. «Data-Driven» Approach

12. «Keyword-Driven» Approach

13. Behavior-driven Text instruction WhenI log into the system as “login”/”password” Actual Code When/log into the system as “(.*)””(.*)”/do|login,password| app.login( login , password )‏ end class App def login( username , password )‏ # Some actions end end

14. Model-based framefork Action 0-1 Action 0-1 Initial state Action 5-1 State 1 State 5 Action 1-1 Action 2-2 Action 2-1 State 2 State 4 Action 0-1 State 3 Action 3-1 Final State

15. Patterns 06.02.11

16. What does pattern mean? 06.02.11 Pattern is a typical solution for typical task

18. Should be initialized only once

19. Should not be modified from outsideEngine driver Config

20. Singleton 06.02.11 Local instance Private constructor All operations are done via local instance

21. Immutable & Lazy initialization 06.02.11 Filled only during initialization Initialized at first method call

23. Units should represent actual command to executeEngine driver NOTE: applicable for Object-based, Keyword-Driven, Behavior-driven, Model-based approaches

26. Functional design 06.02.11 Independent functions

28. If engine driver is used it should be used implicitlyResources

29. Page object 06.02.11 Objects functionality is extended via external class (Decorator/Wrapper)

30. Page Factory 06.02.11 Implicit page object initialization Usage example:

31. Anti-Patterns 06.02.11

32. Big ball of mud 06.02.11

33. God object 06.02.11 Too much methods in one class

34. Hard & Soft Coding 06.02.11 Magic numbers Configuration hell

35. Dependency hell 06.02.11 Test 8 Test 1 Test 7 Test 9 Test 2 Test 6 Test 3 Test 5 Test 4

36. Summary “Framework”, “pattern”, “architecture” are not magic spells Framework identifies how we structure overall solution Each framework type uses specific set of patterns Pattern is the solution for specific task Good solution is the balance between complexity and simplicity 06.02.11

37. 06.02.11 Узнай больше на