ATF for Service Catalog Issue?

[Brian Lancaster]

I'm setting up ATF for Service Catalog. In my 2nd test I using the UI 16 interface to open a request using the service catalog test steps. Up to step five seems to work fine when watching the client test running.

My Steps Are:

1. Create a user.
2. Create a user and assign step one user as the manager (this is for approval in the workflow)
3. Open a Catalog Item
4. Set Variable Values
5. Order Catalog Item
6. Record Query - This is done on the sc_req_item table with request = document id from step 5.

My test keeps failing at step 6 "FAILURE: No records matching query: Request = (empty)". In the first test I built I used the same record query as the only difference was the step was Order a Catalog Item (SP) and it worked fine. Any idea why it is not working when using UI 16 to order the item? It’s almost like step 5 is not working even though I get a success message from it, and it looks fine when watching the client test runner. 

I have tried deleting and re-adding step 6.

[Ankur Bawiskar]

@Brian Lancaster 

Hope you are doing good.

Did my reply answer your question?

If my response helped please close the thread by marking appropriate response as correct so that it benefits future readers.

Regards
Ankur

[Brian Lancaster]

No its still not working for me. I set the record query to something else and did some other stuff so I could watch the request item table. Nothing ever appears so it seems to be an issue with the Order Catalog item.

[Brian Lancaster]

I just tested in a Rome PDI. It worked for me there a well. Then I noticed that 2 step checkout was not turned on. As soon as I turned it on it started to fail. So it seems that the Order a Catalog Item (SP) works with two step checkout but Order a Catalog Item does not.

[Brian Lancaster · Accepted solution]

As a work around after submit I used a click custom component. So I could click the checkout button on the shopping cart page. Then for my record query since I don't get a document id from the custom component I did created on today and request.requested_for is step 2 user.