Question
Incessant Technologies PVT Ltd
IN
Last activity: 7 Jun 2019 15:48 EDT
Pega REST API for Automated Unit Testing using Jenkins
Hi,
As part of the integration of Pega 8 with Jenkins, I have found the article, https://community.pega.com/knowledgebase/articles/running-all-pega-unit-test-cases-execute-tests-service-pega-722.
Can someone please let me know if this REST Service : PegaUnit Rule-Test-Unit-Case pzExecuteTests, is being used in Pega 8 as well ?
Thanks!
Pegasystems Inc.
US
The service is still there in Pega 8, it should still work. Have you tried and found any issues?
Incessant Technologies PVT Ltd
IN
I tried searching for the service in Pega 8, but wasn't able to find the same. Please find the screenshot attached.
Could you please let us know how can we proceed further with the integration.
Pegasystems Inc.
US
Hi Divya,
I was able to find the pzExecuteTests REST service from Records > Integration-Services > Service REST instances by filtering Service package name field with PegaUnit keyword as shown below,
If you still cannot find it from records explorer then you can have a look into the Pega-AutoTest:08 ruleset list of rules. Hope this might help you.
Regards,
Mahesh M
Incessant Technologies PVT Ltd
IN
Hi Mahesh,
Thanks for the info.
I tried following the same exact approach to find the Service from the Records Explorer. But wasn't able to find it. So I then checked from the Pega-Auto Test ruleset for the Service and I was able to find it. But then on opening the Service REST rule, I was getting a warning message saying " This is an old rule that was created prior to Pega 7.3.1. It conflicts with another rule. Delete and recreate the rule to avoid ambiguity."
Please find the screenshot attached. So is it suggested that I use the existing rule or create a new rule with the same functionality?
Also, I have found one more Service REST rule, with a similar name, could you please suggest, if I could use that for the Integration. Please find the screenshot attached.
Pegasystems Inc.
US
Hi Divya,
After looking into both the rules, it looks like at a glance there was a change in the service rule naming convention that caused this rule to be skipped in our skimming process that would normally clean up duplicates like this one. I'd recommend you to use the second service rule without the warning message which seems to be the latest one.
Will inform our Product Specialists regarding this duplicate rule.
Thanks,
Mahesh M
Incessant Technologies PVT Ltd
IN
Sure, will try using the second service rule.
Thanks for the info Mahesh!
Pegasystems Inc.
US
Today i had received an update from the SME stating that "Looking into the system does support having legacy rules living alongside newer iterations. However we created a bug to address the duplicate warning i.e. BUG-489048".