Overview
Test your Appian application within minutes with methods created specifically to operate within Appian applications and Tempo!
Common test case scenarios can be created for reusability throughout test suites. A CheatSheet.feature file that lists out all the supported methods and how to invoke them using the @Given, @When, @Then, @But, @And, and other Cucumber-supported annotation.
Note: Java 11 required for plugin version 23.4
Key Features & Functionality
With Cucumber for Appian:
Post 23.1 upgrade, old locators for dropdown class is not working for us. Does any one else facing the issue with older locators? is there any way that we can make older one compatible too?
Examples on how we are using it previously -
Locator: (//*[contains(text(),'Valuation Report Type')])[1]/ancestor::*[contains(@class,'FieldLayout---field_layout FieldLayout---margin_below_none FieldLayout---margin_above_none FieldLayout---inSideBySideItem')]/descendant::*[@role='listbox']
Locator: //div[contains(@class,'Dropdown')][@role='listbox']
yes, Chrome driver 111 we need to add additional argument or else we need downgrade he chrome version in our local
Thanks
Satheesh Kannan
Hi Team,
I am facing "org.openqa.selenium.remote.http.ConnectionFailedException" error when invoking command "Given I setup with "CHROME" browser" in cucumber-for-appian versions 22.4 and 23.1 and and chrome version "111.0.5563.65 (64-bit)". I also checked using ChromeDriver 111.0.5563.64, but got the same error. I'm using AWS windows 10 machine.
Error message: org.openqa.selenium.remote.http.ConnectionFailedException: Unable to establish websocket connection to <my-local-host-details>
Is there anyway I can get rid of the DEBUG statements, it takes lot of digging to find the actual issue. Any help of this will be appreciated.
15:06:22.699 [AsyncHttpClient-1-6] DEBUG org.asynchttpclient.netty.channel.ChannelManager - Closing Channel [id: 0x352261bf, L:/127.0.0.1:65045 - R:localhost/127.0.0.1:55909] 15:06:22.699 [AsyncHttpClient-1-6] DEBUG org.asynchttpclient.netty.handler.HttpHandler - Channel Closed: [id: 0x352261bf, L:/127.0.0.1:65045 ! R:localhost/127.0.0.1:55909] with attribute DISCARD15:06:22.704 [AsyncHttpClient-1-7] DEBUG org.asynchttpclient.netty.channel.NettyConnectListener - Using new Channel '[id: 0xb5d60450, L:/127.0.0.1:65046 - R:localhost/127.0.0.1:55909]' for 'POST' to '/session/38b062eefaf139bb0d755dcb873de4f4/element'15:06:23.097 [AsyncHttpClient-1-7] DEBUG org.asynchttpclient.netty.handler.HttpHandler -
Thanks,
Chandrakant Raju C
the latest version v22.4 seems to have a bug;
The object identification fails for drop-down.
On New version 22.4 the element definition for dropdown is as below;
<span id="9d114c989f45ddbdab069168cd461dae_value_span">Value</span>
.Whereas for older version of appian the definition was as below;
<span id="4c85c14d61e4e58a2a354fc2a6e88f8d_selectedChoice" class="DropdownWidget---accessibilityhidden">Corporate</span>
the newest version (v22.4) of cucumber tries to find the object with the following Xpath;
//span[contains(@class, 'DropdownWidget---accessibilityhidden')]"
This works on older version on newer version it fails
Appian Chrome Driver's latest version is 109, so Fitness/Cucumber does not support the newest Chrome Driver.
You don't want locator identification , In cucumber Appian most of the locator designed in Stepdef file
if you want you can navigate using Ctrl +click on your Gherkin statement