Posted: 26 Jan 2018 11:51 EST Last activity: 14 Feb 2019 12:10 EST
Test Case guardrail warnings
Hi, In 7.3.1 we are having guardrail warnings for setup data transforms for Automated Unit Test Cases. Our test cases require data transforms to set up the test data, but Pega give a guardrail for needing a test case on all data transforms which leads into an endless circle. This ends up lowering the compliance score.
Does anybody have any fix/workaround for this?
***Edited by Moderator Marissa to update categories***
I understand that all test case related items are kept in a single rule set and that is not part of the guardrail generation. However let us say that we have imported a XSD / WSDL and it has created a lot of DT at my main application. They all have this warning that Unit test case needs to be generated. Is there any way to remove the warning , else we will have to create UTC for each of these generated DT ( which is a lot of effort without a value add) or the guardrail will go for a toss.
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write Post button here. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.
Hey Fayaz, it's indeed a good practice to justify guardrail warnings. It means that you've given the warning any thought. Although I would understand that developers won't justify every (informational) guardrail warning that pops up.
I hope that in the future Pega will add a feature to disable the test case guardrail warning for rules stored in a ruleset with the 'Use this ruleset to store test cases' checkbox enabled.
I would like clarify a few things here for others who come to this page
A adding unit test is a strong recommendation since it helps improve the overall testing practices for the application and reduces the burden on regression testing.
To that end we added an informational warning, which does not impact the guardrail score.
In Pega Platform 8.1, there was an enhancement that was introduced to ignore the test ruleset when computing the guardrail score as a way to reduce the noise with these non-production rules
As was suggested by @liy01, a good practice is to separate the test cases and its associated test rulesets into a separate test app layer, this way any guardrail warnings associated with test assets (or really anything that is not part of the production app) will not impact the main application score. I would recommend following the team application concept called out in the article - Development workflow in a DevOps pipeline