To set up automated testing with Jenkins, you must expose Appian's testing services to the external CI system via Web APIs. The process follows a logical dependency chain:

1. Container: First, create a dedicated application (e.g., "Continuous_Integration") to house the CI/CD artifacts.
2. Initiation: Create the Web API that triggers the test run using a!startRuleTestsApplications(), which returns a testRunId.
3. Monitoring: Create the Web API to poll the status of the run using a!testRunStatusForId() (requires the ID from the previous step).
4. Retrieval: Create the Web API to fetch the final results using a!testRunResultForId() once the status is complete.
5. Validation: Finally, verify the entire sequence by testing the end-to-end functionality before configuring the Jenkins pipeline.

Appian Documentation - Running Automated Tests on Expression Rules with Jenkins

Section: "Integrating with an external system" and "Overview".

Ref: Describes the requirement to create three specific Web APIs in sequence: one to start execution, one to query status, and one to fetch results.

URL: https://docs.appian.com/suite/help/25.3/Running_Automated_Tests_on_Expression_Rules_with_Jenkins.html

Appian Documentation - Expression Rule Testing Functions

Section: "Integrating with an external system".

Ref: "Running expression rule tests from an external system can be accomplished by creating web APIs... The first web API should start the test execution... The second web API should query the status... Finally, the third web API should fetch the results."

URL: https://docs.appian.com/suite/help/25.3/Expression_Rule_Testing_Functions.html

Appian Documentation - Start Rule Tests (Applications) Smart Service

Section: "Overview".

Ref: Explains that this function initiates the test and provides the testRunId used by the subsequent status and result functions.

URL: https://docs.appian.com/suite/help/25.3/Start_Rule_Tests_Applications_Smart_Service.html