Question

3
Replies
270
Views
Close popover
LEELABIRAM SRIRAMULU (LEELABIRAMS6337)
Lloyds Banking Group PLC

Lloyds Banking Group PLC
GB
LEELABIRAMS6337 Member since 2017 22 posts
Lloyds Banking Group PLC
Posted: March 5, 2019
Last activity: April 11, 2019
Closed
Solved

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***

Pega Platform DevOps Testing Applications
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.