Question
Lloyds Banking Group PLC
GB
Last activity: 11 Apr 2019 6:17 EDT
Unit testing a decision table
v7.3.1
Created a unit test case for a decision table and added multiple inputs to test against all possible combinations of input and return.
Updated this decision table in a later version to include a new column, however when I open/save as the original test case to update it with scenarios, the new column is not reflected in the test case rule.
So I had to end up again manually copying the different scenarios across to a new test case. Is this the expected behaviour with this version or is this a bug?
Another question I have is - what is the best practice in terms of the rule set created for unit tests. Should they be locked at the end of each sprint and a new version created or can they be left open?
***Edited by Moderator: Pallavi to update platform capability tags***
Accepted Solution
Pegasystems Inc.
US
That post is relevant unto the latest versions of Pega that is available. At this time there is no option to update a decision table with new changes, you will have to recreate it. This will be addressed in a future release.
Regarding ruleset versioning best practices. The test ruleset versioning should follow the same as the other versioning practices for the other ruleset version. If you lock and roll to a new ruleset version at the beginning of each sprint, then follow that for test ruleset too.
Pegasystems Inc.
IN
Hi Leela,
I think it is an expected behavior as per the discussion in the below post.
https://collaborate.pega.com/question/decision-table-test-case
Thanks!
Lloyds Banking Group PLC
GB
Thank you for your response. Unfortunately, that post doesn't mention which version of PEGA that was reported for and speculates that saving as the old test case rule to a newer version might bring up the new changes, which doesn't work.
Also would appreciate any suggestions on my other query?
Another question I have is - what is the best practice in terms of the rule set created for unit tests. Should they be locked at the end of each sprint and a new version created or can they be left open?
Accepted Solution
Pegasystems Inc.
US
That post is relevant unto the latest versions of Pega that is available. At this time there is no option to update a decision table with new changes, you will have to recreate it. This will be addressed in a future release.
Regarding ruleset versioning best practices. The test ruleset versioning should follow the same as the other versioning practices for the other ruleset version. If you lock and roll to a new ruleset version at the beginning of each sprint, then follow that for test ruleset too.