Download to read offline
Uploaded byAbhijeet Patil
Test automation Screen Play Design Pattern
This document discusses test automation using the Screen Play design pattern. It introduces test automation and its purposes like reducing manual effort and enabling continuous integration. It then covers the Single Responsibility Principle (SRP), how to define responsibilities at the right level of abstraction, and applying the Open Closed Principle (OCP). The document demonstrates setting up a Screen Play project in Maven and running a test. It provides references for further reading on SRP, OCP, and the Screen Play pattern.
Test automation Screen Play Design Pattern
- 1. Test Automation Using ScreenPlay Design Pattern
- 2. Test Automation ● Why‘Test Automation’ ? ○ To reduce manual efforts ○ Continuous integration ● Purpose ○ Is it making you slow ? ○ End to end test ■ Minimal journey
- 3. Page object pattern Isthere any pattern ? Assertions Features / Jobs / functions Locators
- 4. SOLID S : SingleResponsibility O : Open Close Principle L : Liskov substitution I : Interface segregation D: Dependency inversion
- 5.
- 6. Responsibility ● 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 ■ Interaction can change.
- 7.
- 8. Apply SOLID principleTo POM 1. Single responsibility 2. Open close principle Assertions Features Locators AT High level Questions Task UI
- 9.
- 10. 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
- 11.
- 12.
- 13.