Pega Automation approach using UFT

Hey folks,

I try here to give you reference for taking automation approach for PEGA automation projects. I have used UFT 12.02 for PEGA 7.2.2 version automation in one of my project. Following are checklist, which can help.

1. As PEGA application is rule based and flow based application, there were always few set of pages will be used in application. Before deciding framework, dry run the whole application flow for the pages behavior.
2. As pages, might be limited, we can use object repository approach for the application as size will not grow. For few PEGAcontrols, we need to write descriptive programming as well. Mostly frame related problems occurs for few control identification.
3. As it is rule based application, may be require to run different set of test with combination of test data to test the rules, but pages remains same. So try use data driven approach while using framework. Keep all the functions generic so with any combination of test data, we can use same functions.
4. As its having flow based application too, driver script should having provision to calling different functions in sequences to drive the flow. Write module based functions for easy flow driven. 
5. Most of the flow driven by some actions like approve, reject etc., so write function in generic with switch cases to handle the different flow along with data passing approach.
6. Few scenarios may be having multiple data at same flow, then there should be some provision to handle multiple entry of test data by passing argument in split way.
7. Few controls are dynamic based on the conditions, so we can handle it using regular expression. for ex., few property values like , \strname1 can handle in as $\strname1, like that. 
8. Controls are similar to rest web applications for PEGA. UFT can identify it properly, there is no additional add ins require.
9. For error handling, we can used on error resume next statement at function level.
10. Facing sync issue for application, which hurdle in night run execution. so increase wait time much to avoid such things.
11. Try to keep all function libary at module levels.
12. Use environment variables for sharing constant value across test suite
13. keep configuration files for easy project path references.
14. keep files references at top level with public variable to access across the test suite for implementing rules.
15. keep generic functions to connect external files, fetching values or rules to implement, export test results etc.
16. while executing UFT , we need to enable add on in internet explore for PEGA.

Regards,

Trupti