PEGA Application Testing

Hi folks,

After long time, publish another article on Pega Application testing.

Pega application testing needs to take different approach of testing then normal STLC. Pega applications are rule based application having more than 10 k rules. I was worked with pega version 7.2.2.

Pegasystems is a leading BPM / Case Management platform provider. As leaders they are at the forefront in offering automated testing capabilities in the BPM space. Testing Pega BPM based applications from the UI is still a challenge however. Pega testing is followed in agile model. Pega is fast growing tool which makes millions of users happy. It is a business process management (BPM) tool which was founded by Alen Trefler. Pega PRPC is an Application Development Product from Pega Systems. To Test Pega Applications one need to know the Testing Management Framework (TMF) from Pega as well as Required knowledge in Manual Testing and Regressive Testing. Using Pega Unit Testing Feature one can test the Flow Rules, Decision Rules, Integrations and Automated Regression Testing. With the help of pega testing we test the pega applications very wisely and deliver as a defect free.It uses concept called PRPC which is a pega rules and process commander. It uses Rules set to design the pega applications.

As it is rule based application with large set of rules, automation tester needs to create their own framework for rule implementation. use unit testing or functional approach is more better to reusability purpose. Rules can be implemented as functional validations and we can add modules or component base approach as well for the flow of application.

As per research, selenium is best tool for pega testing, but I have used UFT 12.02 for the pega automation. Later on, project move in selenium, but I didn't find much difference in both apart from licence cost of UFT. all technical problem still resides in selenium too, which was happen with UFT.

(Reference taken from quora for below content)

Pega has different Debugging Tool inbuilt to test the Application .we have different types of testing in pega .

Types of Testing :

• Flow based Testing – Concentrates on Business flows (E2E), involving multiple roles and interfaces
• Role based Testing – Testing based on workgroups – Skills, UI etc
• Rule based Testing –

1. Business Rules - Formulae, delegated rules etc
2. Technical Rules - integration rules etc

Pega Debugging Tools:

• Clipboard
• Tracer
• Rule Inspector/UI Inspector
• PLA (PegaRULES Log Analyzer)
• PAL (Performance Analyzer)
• AUT (Automated Unit Testing)

(Reference over)

For automation perspective- we should go with hybrid -data driven framework with modular approach, which work best for rule implementation with different set of data to all modules.

Few challenges in Pega projects like-
1. control identification for web edits not work proper- down key or keystroke approach needs to write for most of controls
2.Nightly run not work- application sync issues occurs much
3. modules approach required and for that application knowledge must be with you to take the decision for create modules-passing parameters, use parameters etc.
4. due to rule based implementation execution time takes more for end to end flows.
5. keep provision for normal end to end flow execution, rule base validation for module execution, role base validation etc in script itself.

Regards,
Trupti