I have set up the following test steps for an ATF test in Madrid, and you can already see the problem :).
We cannot seem to go past submitting a RITM using the ATF test step Order a Catalog Item (SP). The Client Test Runner clicks "Order Now" (we are not using a cart layout), it reads "Submitting..." but then it fails with no more detail than "FAILURE: Validations failed. Failed to Order Item."
Validation failing cannot be true since all mandatory fields are filled in by steps prior to Order a Catalog Item (SP), as you can see. I have also tried testing another, simpler catalog item with the same result. I have tried different browsers, impersonating my admin user instead of one with the role snc_internal, but all end up in the same error.
When creating the test using backend steps (so without "SP" behind the name of the step), the RITM gets submitted successfully, so this seems to only be a problem with the test steps that target the Service Portal.
We have quite a lot of customizations in our portal and I wouldn't be surprised if it is due to this issue with "submit" not found:
We are getting this warning on inspecting a catalog item that is yet to be submitted, probably as intended by ServiceNow. We have no trouble submitting the same catalog item from the portal manually, despite the submit UI action not found warning. At the same time, in Chrome > Inspect > Console the above warning for the UI action is followed tightly by the ATF error when tested from ATF:
Or is this because our Order Now is not OotB and as such, not supported? Ref.:
Any insight is greatly appreciated, including if there is an alternative way of submitting and getting a record from it. I have also tried Submit a form (SP) but I cannot extract the submitted record from it...
We're having the same issue. So far I've tracked it down to the tests failing when the sys property 'glide.sc.sp.twostep' is set to false and succeeding when that property is set to true. In London you could have the property set to either value and succeed. I've opened a HI case to get a resolution.
The only work around I've found is to add a Record Update step to the beginning of the ATF test that modifies the value of the sys property. Doing this will only update the property for the test. It will not permanently change the property.
