How do I unit test error messages on the primary page?
I have a Data Page that generates a page message when it is passed invalid parameters - This page message is set on the Data Page itself (as primary).
I have written some 'happy' Pega Unit Test rules and they work fine. However, my unit test that checks for the error scenario fails. In fact, the only way I can get the test to work is to change the logic of the data page itself, and I don't want that!
I have attached a couple of screenshots showing what I have in my unit test and the result.
Does anyone know how to get the test to pass on the data page containing the error message?
Pegasystems Inc.
AU
Have you tried using a Page Name of RunRecordPrimaryPage (instead of Primary). This the actual page name that the Data Page rule-runner (in 8.4) creates to stage the Data Page.
It is possible the "Primary" is too ambiguous for the Test Case. Did it work for your other happy path test cases or were they all Property assertions?
Updated: 22 Sep 2020 19:14 EDT
Pegasystems Inc.
GB
Thanks for the reply Braam. Sadly I could not see that page in the trace, and I added it as a named page under the tracer settings to be sure.
I am not running the latest version of Pega, so perhaps that page name has changed. In the version I have (Pega 8.3.1) there is a page named 'TestRunOutput' instead. That contains the error messages from the primary page (in this case D_TaskItemsSavable) copied into a text property. Still errors on that page cause the test fail, even if the errors are expected.
Pegasystems Inc.
AU
Hey @Tom_Holt
Sorry I didn't get a notification about your update and am only now circling back over old posts I commented on.
Did you get to the bottom of this or is there more to dig into?
I can see what you're trying to do, and it's annoying that you can't, but haven't you in essence implemented a Test Case for OOTB Platform functionality? That is, a Lookup Data Page returns an error when the keys don't locate an instance?
I propose you can focus your PegaUnits on the happier paths for this Data Page and trust that a lookup Data Page will honour its contract of returning an error when the lookup fails.
Pegasystems Inc.
AU
@BraamCLSA
I have an implementation where I have a data transform Data Page, that calls a separate lookup Data Page. My source data transform copies any errors and messages (if any) from the lookup to it's primary page. And I want to write the TC that checks that's still happening.
So in the error scenario (bad lookup) it's the same issue as the OP mentioned.
Seems like the 'After rule execution' is also not run if there's a message on the test page. Tried a DT that mapped any messages to a Param property and cleared messages to work around it. Guess I'll keep this TC disabled for now.