Information
  • Author: Appian Corporation
  • Type: Utility
  • Support: This plug-in or utility is supported by Appian. Questions, issues, and enhancement requests related to its use should be directed to Appian Technical Support.
  • Industry: All Industries
  • Compatible Version(s): 22.3+, 24.2
  • First Released:
  • Last Updated:
  • Cost: Free - Appian Supported
Share
Home » AppMarket » Cucumber For Appian

Cucumber For Appian

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:

  • Test scripts don't need to be updated for upgrades to supported Appian versions
  • Appian design knowledge is not required to create test scripts
  • Test scripts are easily updated for new UI changes to a form or interface
  • All of the same methods that FitNesse For Appian currently supports are supported
  • Multiple browsers are supported (Chrome v. 64-66 and Firefox v. 53-62)
Anonymous
  • v21.1 Release Notes
    • Supports Appian version 21.1
  • in reply to ginao0001

    Hi Gina,

    You can reuse your existing installation and replace the src and lib folders from the new zip you downloaded. This will update you to the latest version in the current spot you are using Cucumber. When you do this, you could rename the existing folder to lib_old and src_old for example to make a backup of your current setup in case you need to revert.

  • Hello, is there a way to get just the glue code and use that in our code? I downloaded the zip file and am hesitant to set it up the way the Playbook describes because I already have Cucumber set up on my computer and also the basic code that clicks through most of our Appian website, and I don't want any of the prior set up to get messed up because of that. However, I am interested in using the steps that are in the CheatSheet.feature such as "Given I click on card "CARD_LINK_NAME or CARD_LINK_NAME[INDEX]" to be able to add more tests on top of what we have, but am unsure of how to go about getting the code for it. 

  • in reply to ricardop

    Hi Richard,

    I changed my pom.xml file as suggested by you but getting build failure. Could you please assist on this.

  • in reply to Venu

    Hi Venu,I had the same issue, try adding this lines to your pom.xml

  • Hi,

    I downloaded this application today and followed the instructions mentioned in Appian playbook. I am getting build error while running the "mvn clean test" command in command prompt. I have verified the mvn - Version, it is returning Maven information. Can you please help me to set up cucumber for appian.

    Thanks,

    Venu.

  • v20.2.1 Release Notes
    • Bug fixes
    • Fixed a bug regarding clicking on card layouts
  • v20.2 Release Notes
    * Fixed bug with milestone click
    * Fixed toggle box visibility on related action pop up

  • Hi,

    I was trying to execute the cucumber tests through the Azure Devops Pipeline as a build step.

    I was constantly getting the below error. Eventhough the driver was available in the correct path

    java.lang.IllegalStateException: The driver executable does not exist: D:\a\1\s\GBPA\lib\drivers\chromedriver.exe
    at com.google.common.base.Preconditions.checkState(Preconditions.java:518)
    at org.openqa.selenium.remote.service.DriverService.checkExecutable(DriverService.java:136)
    at org.openqa.selenium.remote.service.DriverService.findExecutable(DriverService.java:131)
    at org.openqa.selenium.chrome.ChromeDriverService.access$000(ChromeDriverService.java:32)
    at org.openqa.selenium.chrome.ChromeDriverService$Builder.findDefaultExecutable(ChromeDriverService.java:137)
    at org.openqa.selenium.remote.service.DriverService$Builder.build(DriverService.java:330)
    at org.openqa.selenium.chrome.ChromeDriverService.createDefaultService(ChromeDriverService.java:88)
    at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:158)
    at com.appiancorp.ps.automatedtest.fixture.BaseFixture.setupWithBrowser(BaseFixture.java:172)
    at com.appiancorp.ps.cucumber.fixtures.CucumberBaseFixture.setupWithBrowser(CucumberBaseFixture.java:19)

  • in reply to Bhuvan

    You can use JUnit for Appian (https://community.appian.com/b/appmarket/posts/junit-for-appian). That has all of our Appian Fitnesse Fixtures. You can include those methods inside of your step definition

© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.