Download to read offline
![● How to strike right balance
○ Too many fragments [Test becomes too noisy]
○ Too big component [Loose flexibility]
● How to define a task and how to make sure we build a building blocks ?
○ Dont define action
○ Define behaviour / Goal
■ Frequency of Behaviour to change is very less and is business driven.
Some Learnings till date](https://image.slidesharecdn.com/testautomation-playdesignpattern-170914142231-190123212344/85/Serenity-s-Screen-Play-Design-Pattern-13-320.jpg)
Uploaded byAbhijeet Patil
Serenity's Screen Play Design Pattern
This document discusses test automation using the Screen Play design pattern. It introduces screen play and explains why end-to-end test automation is important. The document then discusses common design patterns for test automation like the page object model and how to apply SOLID principles to page objects. It provides an overview of the screen play pattern and tips for defining tasks and building reusable components. Finally, it provides steps for setting up a screen play project and references for further reading.
Serenity's Screen Play Design Pattern
- 1. Test Automation Using Serenity’s ScreenPlay Design Pattern
- 2.
- 3. What do Imean by test automation ? End to End
- 4. Test Automation ● Why‘End to EndTest Automation’ ? ○ To reduce manual efforts ??? Really ■ Is it making you slow ? ■ Minimal journey ○ Continuous integration pipeline ● Pattern in Test automation ? ○ https://abhigets.blogspot.in/2017/08/pattern-in-test-automation.html ● Most popular design patter ○ Page object pattern
- 5.
- 6. If page istoo complex ??
- 7. SOLID S : SingleResponsibility O : Open Close Principle L : Liskov substitution I : Interface segregation D: Dependency inversion
- 8.
- 9.
- 10. Page object pattern Isthere any pattern ? Assertions Behaviours/Actions Locators
- 11. Apply SOLID principleTo POM 1. Single responsibility 2. Open close principle Assertions Behaviours /Actions Locators AT High level Questions Task UI
- 12.
- 13. ● How tostrike right balance ○ Too many fragments [Test becomes too noisy] ○ Too big component [Loose flexibility] ● How to define a task and how to make sure we build a building blocks ? ○ Dont define action ○ Define behaviour / Goal ■ Frequency of Behaviour to change is very less and is business driven. Some Learnings till date
- 14. Some Tips ○Look atapplication design ○UI components the way they are coupled
- 15. Setup Screenplay 1. GenerateProject a. $ mvn archetype:generate -Dfilter=screenplay i. Enter 1 and select a version ii. 'groupId': : net.serenitybdd.tutorials iii. 'artifactId': : todomvctests iv. 'package': net.serenitybdd.tutorials 2. Run Test a. mvn clean verify
- 16.
- 17.