Testing is vital to ensure that only high-quality projects are produced. Throughout the application's lifecycle, testing strategies can be categorized into the following stages: Before development During development Leading up to go-live During…

Requirements Appian 22.2 and above Java Runtime Environment 11 Chrome or Firefox browsers If using Chrome, we recommend using Chrome For Testing for a more consistent testing experience. An IDE, such as IntelliJ IDEA or Eclipse Setup…

Introduction This play includes tips for organizing, writing, and running tests in FitNesse for Appian, as well as designing Appian applications for testing with FitNesse. This is intended to complement the existing documentation that comes with FitNesse…

Apache JMeter is an open source Java performance testing tool which can be used to simulate user load on a web application. This guide explains how to use JMeter to implement and run test scripts for Appian applications as part of the Appian Performance…

Cucumber For Appian is a client-side tool that builds on top of what FitNesse For Appian has implemented and allows users to write automated UI tests against Appian with Gherkin syntax . Cucumber For Appian will support all of the same fixture methods…

Automated testing reduces the amount of manual testing necessary in an Appian application and reduces risk at each stage of the application development lifecycle. Automated testing can be used throughout the Appian application development lifecycle to…

A hardening sprint is a period of a project where the team stops delivering new features and instead focuses on fixing bugs, preparing deployment activities, performing various types of testing, and cleaning up tech debt. What is the Value of Hardening…

This article provides guidance to application delivery teams regarding the planning and execution of User Acceptance Testing , commonly known as UAT. Although UAT is typically carried out by customer resources, it is important that all team members understand…

Introduction When deploying process model changes to a higher environment, in-flight (active) process instances continue to use the pre-deployment process model version. Additionally, the pre-deployment CDT version is used within these in-flight process…

What is System Integration Testing System Integration Testing (SIT) is the execution of tests to ensure that the different components of an application (Appian application, legacy systems, third party applications, data sources) are integrated and functioning…

Exploratory Testing Overview Exploratory Testing (ET) is a risk-focused testing method in which testers explore systems to identify areas of risk, in addition to checking expected functionality. As testing reveals risks, the tester uses what they have…

Methodology Overview This methodology is intended to provide an entry point for projects of all sizes and types, while identifying opportunities to extend and customize the performance testing effort based on specific project goals and constraints.…

FitNesse for Appian is a client side tool, built on top of FitNesse , that makes it easy to create automated tests on the Appian platform. This tool allows you to create test scripts in a easy to read wiki language that will be run by the system to interact…

Introduction Functional testing is required to verify that a software application performs correctly according to design specifications. It provides you with the opportunity to identify any defects which would prevent the application from being unfit…

Expression rule test cases enable unit testing with minimal overhead by reducing the time required to test while increasing code quality. Because expression rules have a wide variety of uses, creating meaningful test cases will speed up unit, regression…