ATF Test Step: Send REST Request - Inbound: Fails

[Mudagallu Ragha]

Hi All,

I've one ATF Test Step "Send REST Request - Inbound" that is invoking the scripted rest api end point and the account with which it is getting authenticated has all the required privileges, but it is failing with the below response.

Response Body:
{"code":60,"reason":"Resource not found","message":"Param: sysparm_rollback_context_id, Value: cf231487972b1290d2f531d0f053af89, Reason: Invalid parameter name","details":[{"message":"Param: sysparm_rollback_context_id, Value: cf231487972b1290d2f531d0f053af89, Reason: Invalid parameter name","datapath":""}]}

But the same call works fine when we test it from the Postman Client.

Could you please provide some insights about this issue.

Thanks,

Raghu

[Ankur Bawiskar]

@Mudagallu Ragha 

share the test steps screenshots.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Mudagallu Ragha]

Hi @Ankur Bawiskar 
Thanks for looking into. PFB snapshots on the steps execution:

ATF Test Step Definition:

ATF Test Step Execution:

Same REST API Executed successfully in Postman that too with the same credential used in ATF.

Thanks,

Raghu

[Ankur Bawiskar]

@Mudagallu Ragha 

the user in whose session ATF is running has read access to that table?

Also is that the correct end-point?

Did you try running the step with admin credentials?

Is the basic auth details configured correctly in the ATF step?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Mudagallu Ragha]

@Ankur Bawiskar 

Yes, the account has all the required access, and the endpoint is same as that in Postman.

Credential record was already in the system and consumed it in the ATF Test Step. Also used the info on the Postman. And I don't see the authentication issue on the error message. Could not be able to test with the admin privilege as we have limited access in our DEV instance.

Thanks,

Raghu