Hi, I have been tasked with writing automated tests that need to use

Hi,

I have been tasked with writing automated tests that need to use (browse, enter texts, click buttons etc) objects on Appian pages. I’ve been looking at the DOM for a few of the early-release pages and have having difficulty identifying ways of performing object identification.

As an example, an Appian page I’m looking at has a number of inputs (text, dates, dropdows etc….). Picking two different textboxes at random I see:-

<input type="text" class="aui-TextInput" id="gwt-uid-245" aria-required="true" aria-invalid="false" style="text-align: left;">
and
<input type="text" class="aui-TextInput" id="gwt-uid-271" aria-required="true" aria-invalid="false" style="text-align: left;">

The wrapping/parent elements do not have anything that can be used and the id attributes change between page renderings. Is anyone else using Test Automation with Appian and if so, how are they doing robust object identification? Is there a way I can get the design...

OriginalPostID-163127

OriginalPostID-163127

  Discussion posts and replies are publicly visible

Parents
  • Does this Id change after each build deployed? During the Automation testing implementation for Appian Applications, we faced an issue where the Id's changed after each build; However there was still a field where the Prefix remained the same for all the builds and only the value after the postfix kept changing. We were able to use this field as the object identifier.
Reply
  • Does this Id change after each build deployed? During the Automation testing implementation for Appian Applications, we faced an issue where the Id's changed after each build; However there was still a field where the Prefix remained the same for all the builds and only the value after the postfix kept changing. We were able to use this field as the object identifier.
Children
No Data