FitNesse for Appian

Overview

FitNesse for Appian is a client-side tool that makes it easy to create automated tests on the Appian platform. Create test scripts that will run Appian as if a user was clicking through the application and filling out data. FitNesse for Appian includes easy instructions to get you started.

Note: Java 11 required for plugin version 23.4

Key Features & Functionality

With FitNesse for Appian, you can:

  • Write easy-to-read wiki language tests for Appian applications
  • Speed up testing times
  • Set up reusable regression tests

Reusable scripts can be written to:

  • Create new packages
  • Move them to different stages in the workflow
  • Check that forms are being populated correctly
Anonymous
  • Hello,

    I'm having issues getting it to run on Ubuntu 20.04

    When using REMOTE_FIREFOX

    __EXCEPTION__:org.openqa.selenium.remote.UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure. Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'

    When using FIFEFOX (I've installed Firefox via apt-get)

    __EXCEPTION__:org.openqa.selenium.WebDriverException: invalid argument: can't kill an exited process Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:17:03'

    ### INSTALLATION PROPERTIES ###
    # Populate with location of this project's Home Directory. Home Directory is the unzipped directory.
    automated.testing.home=/opt/fitnesse-for-appian-21.2
    
    download.directory=/opt/fitnesse-for-appian-21.2/Downloads
    download.mime.types=application/xml,text/plain,text/xml,image/jpeg,image/png
    
    # When set to true, login will login to Tempo News, ignoring any path in the URL after /suite
    login.to.base.url=false
    
    ### CHROME ###
    # Leave blank if installed in default location of: C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe
    # For MacOS or Linux/Unix, update with location of Chrome binary
    chrome.browser.home=
    # Leave blank if using the Windows driver included in TESTING_HOME\\lib\\drivers\\chromedriver.exe
    # For MacOs or Linux/Unix, update with correct driver in TESTING_HOME/lib/drivers, e.g. /TESTING_HOME/lib/drivers/chromedriver-mac
    # Download new or additional drivers at https://sites.google.com/a/chromium.org/chromedriver/downloads
    chrome.driver.home=/opt/fitnesse-for-appian-21.2/lib/drivers/chromedriver-linux
    
    ### FIREFOX ###
    # Leave blank if installed in default location of: C:\\Program Files (x86)\\Mozilla Firefox\\firefox.exe
    # For MacOS or Linux/Unix, update with location of Firefox binary
    firefox.browser.home=/usr/bin/firefox
    # Leave blank if using the Windows driver included in TESTING_HOME\\lib\\drivers\\geckodriver.exe
    # For MacOS or Linux/Unix, update with correct driver in TESTING_HOME/lib/drivers, e.g. /TESTINGHOME/lib/drivers/geckodriver-mac
    # Download new or additional drivers at https://github.com/mozilla/geckodriver/releases
    firefox.driver.home=/opt/fitnesse-for-appian-21.2/lib/drivers/geckodriver-linux64
    
    ### REMOTE FIREFOX ###
    #Name the browser REMOTE_FIREFOX
    # Leave empty if connecting to localhost. http or https
    firefox.host.protocol=
    # Leave empty if connecting to localhost
    firefox.host.ip=
    # Leave empty if connecting to port 4444
    firefox.host.port=
    
    ### REMOTE CHROME ###
    # Leave empty if connecting to localhost. http or https
    # Name te browser REMOTE_CHROME
    chrome.host.protocol=
    # Leave empty if connecting to localhost (i.e. ondemand.us-west-1.saucelabs.com)
    chrome.host.ip=
    # Leave empty if connecting to port 4444
    chrome.host.port=
    #Use comma separated values ex: username=appian,accessKey=,browserName=Safari,platform=mySecretAccessKeycOS 10.13,version=11.1,name=My Safari Test
    #These two chromeOptions capabilities profile.default_content_settings.popups=0) and safebrowsing.enabled=true are hard coded capabilities.
    #You'll need to set chromeOptions to blank to override those capabilities.
    chrome.capabilities=
    ~                                                          

    I'm able to do a curl/wget of the URL I'm trying to reach from the machine.

    Here are the different versions of the tools I am running:

    openjdk version "1.8.0_282"
    OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_282-b08)
    OpenJDK 64-Bit Server VM (AdoptOpenJDK)(build 25.282-b08, mixed mode)
    
    Mozilla Firefox 89.0.2
    
    geckodriver 0.24.0 ( 2019-01-28)
    
    selenium-firefox-driver-3.141.59.jar
    
    
    

    I followed all the other instructions - anything else I may be missing?

  • log4j.properties is missing from the currently available download (July 7 2021). Is there a way to just get this file someplace else? Or else, can anyone share the file?

    Many thanks!

  • Hello Team,

    Please find the issue on the latest fitnesse we run on appian version 21.1 :

    1. On windows10, the "a!pickerFieldCustom" , "a!pickerFieldUsers" and any other picker fields are not recognized on both chrome and fiexfox, and unable to type and select by fitnesses.

    2. And Fitnesse unable to recognize and click on "a!cardLayout"  (on any OS platform, both chrome , firefox).

    Please help to fix this issue asap.

    Thanks

    Vasantha

  • Hi Stephan,

    It's the appian-selenium-api-xx.x.jar. We released a new Appian Selenium API last quarter, which is built on top of this jar, and this jar is used for the other two products FitNesse for Appian and Cucumber for Appian. 

  • Naming conventions changed? We used to extract fitnesse-for-appian-<version>.jar. But I cannot find it in the plugin package. What is the new jar to use?

  • 04 June 2021 Release Notes
    • Enhancements
    • Support new SectionLayout
    • Upgrade Selenium Server to 3.141.59
    • Bug Fixes
    • Fix bug for radio button card
    • Fix bug for icon link alt text
  • It's is working now with the latest version. 

  • HI Vincent , when will be this one is getting fixed? any ETA for the same