Creating ATF that starts on portal and ends on the backend

[Darlene York]

Hello, I am trying to build an ATF script that starts with

1. Creating Users
2. Impersonating the user that was just created
3. Open a Catalog Item on the Portal
4. Set the variable state validation
5. Set the Variable Values
6. Test the Submit Button I am getting the following error on the Submit a Form step.  FAILURE: Browser blocked submission of 'null' form to server 

The above is working except for #6, what I’m not sure about is how now go about adding the steps to complete the test on the backend.  I want to add an approval step and a fulfiller step, I want it to be all on one test.  The item that is opened in step 3 I want to work get approved and fulfilled then the req and RITM to close.

Also, I have read that best practice is to have a set of test users, example atf.user, atf.approver, atf.itil, etc. and always test with those users. Then I read that best practice is to create a user and impersonate user in the test.  Which is best?

Any suggestions would be greatly appreciated.

[Brian Lancaster · Accepted solution]

For step 6 are you using Submit a Form (SP) for the test step.

Also your don't need step 2. In step 1 there is a check box that will allow you to automatically impersonate the user that was just created.

Edit: Sorry missed where you said that you were using Submit a Form (SP). I'm not sure if it is the same thing but after upgrading to Rome I has a similar error with Submit a Record Producer (SP). I viewed the test results and clicked on related link call Add all client error to warning list. I then was able to get thought the test and verify the incident was created on the back end. Seems like a bug in Rome.

[Darlene York]

Hi Brian,

Thank you for your response.  I didnt realize that I didnt need the impersonate step, thank you.  I will try to add the errors to the warning list.  I appreciate your help.

[Brian Lancaster]

If my response fixed your issue please mark a correct.