Posted: 25 Mar 2018 22:19 EDT Last activity: 29 May 2018 14:15 EDT
PegaUnit related question - What all trigger points are available to trigger a PegaUnit TestSuite
Based on ALEXL's comment here, it is clear that test suites can be triggered/run through a CI tool (jenkins) OR by an agent in Pega environment. I've my question underlined below.
If the product is imported via import wizard or manually via prpcUtils utility, to a higher environment, ---> In this case, is there a way to trigger the PegaUnit test suite as part of the import process??
I could think of customizing the pyPostImportCollection rule to add an activity that calls the "Execute Tests" REST service. But how do I dynamically pass the accessgroup name or the TestSuiteID?? -- May be this approach is not feasible at all. It was just a thought.
If upgrade happens after logging into the application then we have operator context already , so you can directly configure to run the activity pzGetTestsAndExecuteInner with the TestSuiteID param. This is one of the inner activities gets called from the REST service pzExecuteTests as well. TestSuiteID is the pxInsName of the TestSuite which you want to execute that you need to explicitly pass otherwise all test cases available in the context application will get executed.
For other things like modification of pyPostImportCollection and availability of operator context during upgrade process can be shared by System Management team.
What is the right place to call the TestSuite, Is it the pre-import process API or the post-import process API?
Thanks for the reply John.
As said in my original question, I could think of customizing the pyPostImportCollection rule to add an activity that calls the "Execute Tests" REST service. But how do I dynamically pass the accessgroup name or the TestSuiteID?? That doesn't accept those parameters. -- May be this approach is not feasible at all. It was just a thought. How do I call the TestSuite as part of Post-import process then?