Posted: 22 Jan 2020 0:51 EST Last activity: 6 Feb 2020 8:06 EST
Scenario Testing Documentation to record screens and calculations
Would you share any documentation on capturing and defining different scenarios in “Scenario Testing” (UI based testing)? How to capture/record the declarative calculations and read-only fields?
For example: DueAmount, Surcharge and TotalDue fields are on screen. TotalDue is calculated declaratively by using declare expression (TotalDue = DueAmount + Surcharge). So, it’s been calculated and displayed read-only value on screen the moment values are entered in input amount fields. How to mention this calculation formula in Scenario Test Case?
Another scenario: DueAmount and Surcharge are entered in first screen and TotalDue is calculated in post transform and displayed read-only value in second screen.
What is configuration needed on TotalDue step in Scenario Test Case?
Pega Platform version: 8.1.2
I have gone through the below links which are useful in set up and start capturing the scenarios.
You cannot test the formula / formulae that have been used to calculate the values dynamically. Scenario testing is ideally used to run your case and validate the fields that are available in the UI. Having said that, you can record the inputs that you are using for calculation and record the output dynamic value as well. While running the test case, the same values will be provided as inputs and the output should match the expected output. If it doesn't the test case fails there by letting us know that the formula for declarative property has changed.
The other way of doing this would be to use the data pages for providing the dynamic values while running the test case which is listed in the help documents that you have gone through. While running the test case, you can use dynamic values for inputs and provide the calculated value also as dynamic value (by manually calculating the output and passing it while running the test case ) and see if the output matches the dynamic value that you have provided. If it doesn't that means there has been a change in the formula.
Other than this we don't have a provision to validate the formulae used while creating declarative properties.