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
Parents

  • 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)

Comment

  • 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)

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