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:
We are experiencing some problems with the dependencies after upgrading to Appian 23.3 jar. This is affecting our application performance and functionality. We have tried to resolve the issue by following the documentation and troubleshooting steps, but we have not been successful. We would appreciate your assistance in resolving this issue as soon as possible. Please find the snippet below:
Thank you for you cooperation and support Sainath Singirala
Can anyone suggest where to look for this kind of release notes which can actually convey to us about the locators change.
Hi, I am using new version 23.2.1 and can not access related actions.
Previously I was able to access it via clickMenu() but not it doesn't work in new version. So I tried different approaches - clickActions, clickRecord and clickLInk, clickRelatedActions and other- no luck.
I click on site page "SITE_PAGE" isn't applicable here
Any suggestions how it can be solved?
the problem seems to be on the new feature that changes the number of items in the menu from 5 to 10. now, there is a hidden div, and the original one. so the selector returns 2 elements instead of one.
the solution appian gave is to change the statement
from :
"Click on menu"
to:
I click on site page "SITE_PAGE"
Hi,
If your Cucumber script does not specify that the Appian version is 23.2, you will receive this error upon login due to changes in the XPATH and HTML structure in 23.2.
If you continue to experience this issue after specifying the Appian version as 23.2 in your testing script, please open a support case with an example test script that reproduces the issue so that we can review further.
Hi there,
We are being affected by this issue as well.
Has anyone implemented a resolution or workaround?
Thanks!