automation, best practices, cuucumber, framework, java records, reflection, selenium, web automation

2. 2
2

3.  Problem Statement
 Solutions
• Traditional Solution
• Developed Solution
 Challenges
 Demo
 Effort Analysis

5. Problem Statement
To develop generic, model-based
solution in which page automation is
driven by BDD (Cucumber) scripts.

6. SOLUTIONS : TRADITIONAL APPROACH
(A)

7. SOLUTIONS : TRADITIONAL APPROACH
(B)

8.  Re-writing of following for every page
 Page Objects
 Step Definitions
 Static Data
 Increased Development Efforts
 Scalability
 Increased Maintenance
Challenges : Traditional Approach

9. L E T ’ S D I V E I N
Developed Solution

10.  Ease of use
 Decreased development efforts
 Randomized / Static Data
 Increased Scalability
 Minimal Maintenance
Advantages : Developed Solution

13. Anatomy of the
Solution

14. Feature File(s)
Object Repository
Step Definition(s)
Page Object(s)

15. What is Java Reflection APIs?
 Java Reflection is a process of
examining or modifying the run time
behavior of a classes, methods &
interfaces at run time.
 Through reflection, we can invoke
methods at a runtime.
Source : GeeksForGeeks

16. Default Behavior
i.e. Java Faker
DiUS/java-faker: Brings the popular ruby faker gem to Java (github.com)

17. #BTS Of the Solution

18.  Exact Name as seen on UI
 Locator
 Type of Field
 Faker Data Model that defines the randomness
 Field Name
 Field Type
 Value

19. Efforts
Analysis
Traditional v/s Developed

21. HITESH PRAJAPATI
hiteshprajapati1992@gmail.com
/in/hiteshprajapati007
/prajapati-hitesh