ATF Tests failing after the version upgrade.

[Srikanth Menava]

Hello Community,

 My ATF Tests ran successfully in UTAH version, So I moved them to other instances. 

Now in Xanadu I came back an revisited and notice that many of them are failing at different steps.

1) Failing at : UI Action Visibility

error : FAILURE: UI action 'Create SDR' is not visible.

 So I changed the ATF property to gimme a screenshot of the error.

I saw the UI action on the form in the screenshot, WEIRD ( I veried that there is only 1 button on the table )

just so you all know, I tried to de-activate it and the next step is to click the UI action so it is failing there now.

Another test is failing too(this is a test inanother step) 

2) Failing at :Click a UI Action

error : FAILURE: Failed to find UI action '***** - Create Outage' on 'incident' form.

'***** - Create Outage' is a button on the form context(meaning it is an button you will get on clicking 3 bars on the left of the screen).

This defeats the whole purpose of having ATF's if it changes for every release.

Can somebody help me  @Ankur Bawiskar (has provided some valuable feedback on my previous posts)

[Josh Pirozzi]

Hey @Srikanth Menava,

The first thing that comes to mind / question I have is, when going through the ATF Test, are you impersonating a User Account that has access(es) to view the UI Action?

[Srikanth Menava]

Thanks for the response @Josh Pirozzi 

The UI action has condition that it should be visible to itil role, my ATF user has ITIL role so this question is ruled out as per config of UI action, moreover in the screenshot I attached in the question the UI action is clearly visible(Please find my screenshot from. the question)

[Josh Pirozzi]

Thank you @Srikanth Menava,

The next thoughts I have are:

• Confirming each record is in its correct State for the UI Action to display.
• Extend the Timeout on the Test Step to 20-30 seconds.
  • I've experiences where the Cloud Runner may miss searching for the Form Field or UI Action by running too quickly. 

[Dr Atul G- LNG]

It looks like a configuration issue that was created during the upgrade. Please check the skip record / conflicts during upgrade.