Question
IT CO GROUP OF COMPANIES
RU
Last activity: 22 Dec 2015 6:14 EST
How to work with Pega Auto Testing of Flow in Pega 7.1.8 version? Is there any document available for this?
I have tried to create Auto Test for Flow in pega 7.1.8 version but it is not working as expected. I think because in Pega 7 version starting flow is case stage based so there might be some different way to create auto test for it. Please help me regarding this.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
IT CO GROUP OF COMPANIES
RU
SR is resolved related to this post by Pega GCS team members Vaibhav Sharma and Suruchi Gupta. pzIndexedOwnerKey is the property used for Pega internal purpose and so we can ignore that in the first screen.
Recorded Test Case is working as expected. In pega 7 all state of the assignment is recorded, so the blank assignment UI form screen that appears first is initial stage of assignment and on clicking next we will see the data that we have filled in the assignment UI form.
Pegasystems Inc.
US
Hello Anupam,
On my 7.1.8 box, I was able to successfully create testcases coupled to a flow given the instructions mentioned in the following pdn article coupled to the 6.1 version.
What issues are you encountering? Maybe some screenshots of the behavior would help clarify the issue.
Updated: 1 Dec 2015 4:05 EST
IT CO GROUP OF COMPANIES
RU
Hi Rowland,
I am recording the test case by running the flow pystartcase.
After recording the test case, I am running the recorded test case by selecting the option "Run until difference found". It shows a list of difference found on the screen, which is normal but what bothers me are the difference that is marked in the below screen shot. It indicates that recorded work object is not identified as per my understanding. And all the entered field values from the forms are missing in the run.
I followed the same steps as mentioned in pdn article about test case creations.
Pegasystems Inc.
US
Hello Anupam,
I see the same behavior in the fields identified. I wouldn't think you would write the test workobject to the index table so the behavior seems to me like this would make sense to me. Did this perform differently in the pasted?
Pegasystems Inc.
IN
Hi Rowland,
This is to inform you that I am handling this SR.
As discussed , Anupam told me that he is not able to understand "I wouldn't think you would write the test workobject to the index table"
He further told that he is not creating any indexing for the Work Object.It is just getting saved in a separate table but after recording the test case I am getting the messages that mentioned above.
Could you please help me to clarify more to Anupam?
Regards
Suruchi Gupta
Pegasystems Inc.
US
If you are working an SR that pertains to this discussion thread, do you mind sharing the SR number so that we may track it?
Thanks in advance!
Pegasystems Inc.
IN
Pegasystems Inc.
US
Thanks! I've updated the thread!
Accepted Solution
IT CO GROUP OF COMPANIES
RU
SR is resolved related to this post by Pega GCS team members Vaibhav Sharma and Suruchi Gupta. pzIndexedOwnerKey is the property used for Pega internal purpose and so we can ignore that in the first screen.
Recorded Test Case is working as expected. In pega 7 all state of the assignment is recorded, so the blank assignment UI form screen that appears first is initial stage of assignment and on clicking next we will see the data that we have filled in the assignment UI form.