GitHub Actions now has a ready-made action for running FT tests, giving release owners a supported way to place functional execution inside GitHub workflows.
That addition matters because functional test execution is often managed outside the delivery pipeline, leaving unclear ownership for failures, results, and release gates. FT 26.3 also brings supported Python authoring, AI-assisted verification, broader application coverage, and operational improvements across Jenkins and Azure DevOps.
Put functional tests in the delivery workflow
The new GitHub Action allows teams to invoke FT tests from GitHub workflows. This enables a more consistent pattern for associating a build, test execution, result, and deployment decision in one delivery record.
For release governance, teams should define:
- Which workflows require functional-test gates
- Which repositories and branches may invoke shared test assets
- How credentials and test-environment access are controlled
- Where run evidence is retained for audit and incident review
- Who owns failures caused by environments versus application changes
Azure DevOps users gain the ability to run tests as a specific Windows user. This can matter where desktop applications, profile-specific settings, certificates, or access policies affect test behavior. The extension can also specify a workspace when connecting to a Functional Testing Lab server with multiple workspaces. Its resource task can retrieve workspace information alongside device and application information.
Jenkins teams can now order ALM test sets by name or ID and send run-result summary emails to specified recipients. Ordering by ID can reduce ambiguity when names are duplicated or naming standards have changed over time. Configurable notifications provide a direct route for putting execution outcomes in the hands of release stakeholders.
