Pega Selenium Automation Course Outline

Pega Selenium Automation Course Outline
Focus: Advanced UI Automation and End-to-End Regression Testing for Pega Applications using Selenium WebDriver
This course is designed for QA professionals and System Architects who need to implement robust, external UI automation for Pega applications using industry-standard Selenium WebDriver and Java/Python-based testing frameworks.
Prerequisites: Familiarity with Java or Python, basic understanding of Pega application structure (Case Life Cycle, Rules, Portals), and HTML/CSS/JavaScript concepts.
Module 1: Pega Automation Testing Foundation & Setup
1.1 Introduction to Pega Testing Strategy
The role of external automation (Selenium) alongside Pega's built-in tools (PegaUnit, Scenario Testing).
When to choose Selenium: Cross-browser compatibility, testing non-Pega external integrations, and complex regression cycles.
1.2 Setting up the Automation Environment
Installing Java Development Kit (JDK) / Python Environment.
Setting up the IDE (e.g., IntelliJ, VS Code) and configuring Maven/Gradle.
Installing Selenium WebDriver, TestNG/JUnit (or PyTest), and required browser drivers (Chrome, Firefox).
1.3 Pega Application Structure from a Tester's View
Understanding the Pega Document Object Model (DOM) and how Pega renders its UI elements.
Identifying key UI components: Harnesses, Sections, Dynamic Layouts, and Data Grids.
Module 2: Overcoming Pega's UI Challenges with Selenium
2.1 Locating Pega Elements Safely (The Dynamic Problem)
Handling dynamically generated IDs and Pega's naming conventions.
Best practices for using TestID property (Developer tool) for stable element identification.
Writing resilient XPaths and CSS selectors based on Pega attributes (e.g., data-test-id).
2.2 Mastering Wait Strategies
Why standard Selenium waits fail in Pega (due to frequent AJAX calls).
Implementing explicit waits based on Pega-specific loading indicators (e.g., checking for the pzhc-waiting-overlay disappearance).
Techniques for waiting for Pega's client-side processing to complete.
2.3 Handling Advanced UI Interactions
Switching between Pega frames (iframes) for embedded content.
Automating interactions with Pega's controls: Dynamic Selects, Calendars, and Checkbox groups.
Working with Pega Tables and Data Grids (iterating through rows, sorting, and filtering).
Module 3: Building a Robust Pega Automation Framework
3.1 Framework Architecture and Page Object Model (POM)
Designing the folder structure for Pega Test Suites.
Implementing a highly reusable POM tailored for Pega Case Types (e.g., a Page Object for each Stage or Major Section).
Creating reusable Pega Utility classes for common platform actions (e.g., logging in, navigating the portal).
3.2 Test Data Management for Pega
Strategies for generating or fetching test data from external sources (Excel, databases).
Using Pega's API to pre-populate or clean up Case data before UI testing begins (hybrid approach).
Data-driven testing using TestNG/PyTest parameterized methods for Case flows.
3.3 Custom Keywords and Utility Functions
Developing custom Selenium keywords to simplify common Pega actions (e.g., clickNextStage(), setFieldValue(label, value)).
Implementing custom listeners for automatic screenshot capture on Pega assertion failures.
Module 4: Automating Pega End-to-End Scenarios
4.1 Case Life Cycle Automation
Designing test scenarios that cover the entire life cycle of a Case Type (creation, assignments, approval, resolution).
Validating data propagation and calculation results across different stages and data transforms.
4.2 Testing Different Pega Portals and Roles
Automating user journeys for distinct Operator IDs (e.g., Customer Service Rep, Manager, Admin).
Testing different portals (e.g., App Studio, Dev Studio, Custom Portals) for role-based access.
4.3 Integration Testing via the UI
Testing Case flows that trigger external Pega Connectors (e.g., checking if external data retrieval is successful).
Validating the successful creation or update of external records as viewed through the Pega UI.
Module 5: Reporting, CI/CD, and Maintenance
5.1 Integration with TestNG/PyTest Reporting
Generating detailed HTML test reports using TestNG/Extent Reports (or equivalent for Python).
Integrating Pega log data (from the Tracer) into Selenium reports for comprehensive debugging.
5.2 Integrating Selenium into CI/CD
Running tests in Headless mode (e.g., using headless Chrome/Firefox).
Configuring Jenkins, GitLab, or Azure DevOps pipelines to automatically trigger Pega Selenium Test Suites after deployment to lower environments.
5.3 Maintenance Strategies and Best Practices
The "Self-Healing" concept: Using dynamic locators to reduce maintenance effort.
Strategies for rapid test script updates when Pega hotfixes or major version upgrades occur.
Setting up parallel execution for faster test run times (using Selenium Grid or cloud services).
Final Project: Full Regression Suite Development
The final project requires students to select a real-world Pega Case Type (or a mock application) and develop a complete, parameterized, and well-structured Selenium Automation Framework covering critical end-to-end regression paths.
INR: 20000/-