Как надо правильно строить автоматизацию тестирования с нуля, что нужно применять, а то не нужно применять при проектировании архитектуры. Какие виды фреймворков бывают, что с ними надо делать. Все и много другое вы сможете найти в этой презентации
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
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
22.
23. Units should represent actual command to executeEngine driver NOTE: applicable for Object-based, Keyword-Driven, Behavior-driven, Model-based approaches
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
![What’s it all about? ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)