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
  • If you are wanting to skip the SAML login for autmated testing users, you can try using the native Appian login by setting the login URL to <ENV_URL>/suite?signin=native. If you need to use SAML I think it's likely you'd need to write a plugin but could also try setting the IDs of the username and password login fields on the SAML page to the same IDs used by Appian on their login page

  • HI, there is a way to use Fitnesse also in enviroment that is under vpn and is saml authentication based.
    How I should set the configuration ?
    Thanks in advance.

  • Has anyone else experienced an issue where the File Upload command fails for a File Upload component?

  • I am trying FitNesse for the first time. Have installed it and have executed a test script. it triggers Appian URL and logs in with the credentials, however when trying to execute the script "click on menu | Reprots" it failing with error  Bad table! DecisionTables should have at least three rows. in the execution logs I see the below warnings. 

    My Appian version is 24.2 and Fitnesse us 24.3.

    I see the below error in the execution log. can you please help to resolve this error?

    WARNING: A terminally deprecated method in java.lang.System has been called
    WARNING: System::setSecurityManager has been called by fitnesse.slim.instructions.SystemExitSecurityManager (file:/C:/fitnesse-for-appian/lib/fitnesse-20230503-standalone.jar)
    WARNING: Please consider reporting this to the maintainers of fitnesse.slim.instructions.SystemExitSecurityManager
    WARNING: System::setSecurityManager will be removed in a future release

    Script:
    |click on menu|REPORTS|
    |click on menu|ADMIN TASKS|
  • Per http://localhost:<port#>/FitNesseForAppian.Documentation.Administration.Upgrading 

    Full Upgrade

    1. Rename existing FitNesse for Appian installation, which will be referred to as TESTING_HOME_OLD.
    2. Download the newest version of FitNesse for Appian from Appian Forum.
    3. Unzip FitNesse for Appian into TESTING_HOME.
    4. Copy the following files from the previous installation of FitNesse for Appian:
      • TESTING_HOME_OLD/fitnesse.properties
      • TESTING_HOME_OLD/log4j.properties
      • TESTING_HOME_OLD/configs/custom.properties
      • TESTING_HOME_OLD/configs/metrics.properties
      • TESTING_HOME_OLD/configs/users.properties
      • Any other custom files within the installation directory
    5. If not using default FitNesseRoot folder, for example using version control, copy the following directories from the new installation into your existing FitNesseRoot directory:
      • FitNesseForAppian - contains Appian specific documentation and examples
      • FrontPage - contains links to Appian specific documentation on the home page, make sure to merge in any changes made to the out of the box FrontPage
      • PageFooter - contains link to Appian specific documentaiton in the footer


    Partial Upgrade

    Be aware this may not always work as new methods may require additional libraries which will only be included in the full installation pacakge

    If you simply want access to new methods without the new documentation, examples, scenarios, etc. do the following:

    1. Download the newest version of FitNesse for Appian from Appian Forum.
    2. Extract the zip into a temporary directory.
    3. Replace fitnesse-for-appian-x.x.jar in TESTING_HOME/lib/appian with version from extracted zip. Make sure to only leave one fitnesse-for-appian jar.
  • Hello, good day. To update to the latest version, what is the process to follow?

  • The issue was resolved after the browser driver .exe files placed in lib/drivers folder.

  • v24.3.0 Release Notes
    • Enhancements
    • Added built-in retry to click operation in case of element not interactable exception
    • Updated the milestone locator