Rapise 8.5 Released - Cross-Platform Test Execution, Containerization, Large Framework Support and More

4-Sep-2025 by Adam Sandman Product News

We are excited to announce the release of the Rapise 8.5, the latest version of our award-winning, AI-driven, codeless test automation platform. This new version includes support for cross-platform running of tests, with a new RapiseLauncher agent that can be deployed on Linux, Mac, Linux, Docker, and CI/CD Pipelines such as GitLab, GitHub, AWS CodeBuild, and Azure DevOps Pipelines. In addition, this new version handles support for larger test frameworks and parallel test execution using Spira with new agent pools.

Cross-Platform Test Execution

Rapise 8.5 takes a major step forward in cross-platform test execution. You can now run Web and API tests in any environment that supports Node.js. This version introduces the new Node.js-based RapiseLauncher, which performs test execution on Linux, macOS, and Docker, and reports the results directly to Spira. These enhancements lead to more cost-effective testing and provide greater flexibility for CI/CD integration with platforms like:

  • AWS CodeBuild
  • Azure DevOps Pipelines
  • GitHub Actions
  • GitLab Pipelines
  • Jenkins

You can download the new cross-platform NodeJS execution agent directly from the Inflectra Customer Area:

For details on executing the tests using one of these platforms, please refer to the online documentation. It includes sample YAML files for the various DevOps platforms mentioned.

Rapise 8.5 introduces this new NPM package that contains both the Rapise execution engine and RapiseLauncher. The package is distributed as a .tgz file that can be installed from a URL or a local file. Future releases of Rapise will include new versions of both the core Windows Rapise IDE and this new NPM package for playback.

Parallel Test Execution using Spira

Rapise 8.5 introduces a powerful way to run your automated tests faster than ever - agent pools. If you manage multiple test sets and execution hosts, you can now group your hosts into a dynamic pool to run tests in parallel, significantly reducing the total execution time.

How It Works

Instead of assigning each test set to a specific machine, you can now create a host pool. Simply configure multiple execution hosts (with RapiseLauncher installed) to share the same Automation Host Token.

When you schedule your tests, you assign them all to this single, shared Host Token. Rapise then treats the entire pool as one powerful, logical host.

For example, let's say you have 12 test sets and 3 hosts in a pool. When the tests are scheduled to run, the system automatically distributes the work. The 3 hosts will immediately begin executing the first 3 test sets in parallel. As soon as a host finishes its test, it instantly picks up the next available one from the queue.

The Benefits

  • Maximum Speed: This dynamic distribution ensures your hosts are never idle, completing your entire test suite in a fraction of the time.
  • Ultimate Simplicity: You no longer need to manually balance the workload by assigning specific tests to specific machines. Just point all your tests to the host pool and let Rapise handle the rest.

This feature is perfect for teams looking to optimize their CI/CD pipelines and get test results faster.

Load Balancing Mode

For advanced users only

While agent pools are great for running many separate test sets, what if your challenge is a single, massive test set with hundreds of test cases? Rapise 8.5 also introduces Load Balancing Mode to solve this exact problem.

This powerful feature allows a pool of execution hosts to work together to complete a single test set much faster. Instead of one machine working through every test case sequentially, the load is distributed across the entire pool.

Support For Large Frameworks (30k Test Cases)

To better support large testing frameworks, we have optimized Rapise to ensure a smooth user experience. These performance enhancements are designed for enterprise level testing frameworks that have grown significantly, providing reliable operation for projects containing up to 30,000 test cases.

Other Improvements and Bug Fixes

In addition to these marquee features, this new version has many other customer-driven improvements, enhancements and bug fixes:

Improvements

  • Custom icon for Page Object JS file [IN:8096]
  • Optimize Add All Files [IN:9320]
  • Show XPath should work for objects from external .js files [IN:10335]
  • Enable Cancel functionality in the File Modified prompt [IN:10874]
  • Optimize Stop Debugging speed if the Report folder contains >1k report files [IN:10885]
  • Add node_modules to the Git Sync ignore list [IN:10888]
  • Optimize Save Test As for 10k+ test case frameworks [IN:10901]
  • Import Page Object should show some progress [IN:10902]
  • Spira Dashboard should be disabled when importing or cloning test cases using a script [IN:10903]
  • Add Reveal in Explorer context menu for folders in the Test Files Tree [IN:10922]
  • Do not put the output log into the RunnerMessage field of a Test Run; create an attachment instead [IN:10933]
  • AiRobot: Enable upscaling of smaller apps [IN:10936]
  • Add ResetCookies method for REST and SOAP clients [IN:10972]
  • Optimize Chrome for Testing download to reduce memory usage [IN:11066]
  • Add the path of a spawned (chrome|edge|gecko)driver.exe process to the log file [IN:11096]
  • Show JS call stack for failed JS assertions [IN:11097]
  • When creating a Floating License Session, append the username to the IP address [IN:11196]
  • In the Spira Dashboard, add tooltips for multiline report items [IN:11229]
  • Allow removing test cases when the Included filter is used on the Framework tab in the Spira Dashboard [IN:11242]
  • Allow excluding test cases when Included filter is selected on the Framework tab [IN:11243]
  • If RapiseLauncher fails to clone a Git repository or clean a folder, this information should appear in the first Blocked test case run [IN:11245]
  • In the Spira Dashboard, enable editing mode for a property even if the user clicks on a property name [IN:11247]
  • When cloning an object, change its name along with its ID [IN:11302]
  • Flash in mobile should display a dialog confirming an element was found successfully [IN:11314]
  • In the RapiseLauncher title, display Machine ID and Automation Host ID [IN:11325]
  • Allow fine-tuning of Auto-Wait logic [IN:11338]

Bug Fixes

  • The Report tab jumps to the beginning when selected [IN:10875]
  • Out-of-memory error when switching to a project with 20+ open documents [IN:10876]
  • In the code editor, tooltips for const variables are not working [IN:10911]
  • Main and User toolbar buttons prioritize the selected tree TC over the currently open document [IN:10921]
  • Close icon missing for matching test cases [IN:10925]
  • \\ Gets replaced with \ in the profile arguments editor [IN:10928]
  • When loading a Test Set in the Choose Test Case dialog, preserve Test Case order [IN:10953]
  • Dynamic test set filters are not saved if a framework is unlinked and moved to another project [IN:11004]
  • RVL Editor: Switching back and forth between RVL tabs removes the selection [IN:11024]
  • Add a 1-second sleep to Spira.RunTestSet to avoid swaps [IN:11027]
  • RapiseLauncher fails on a Test Set that contains automated test cases, but is marked as Manual [IN:11152]
  • Navigator.GetTabTitleAt and similar methods may connect to incorrect tabs [IN:11156]
  • Grid in Salesforce has changed, cannot click on a button in a cell [IN:11182]
  • Incorrect ordering of nested folders in Spira Dashboard [IN:11202]
  • Clicking on an error link in the report scrolls RVL to the beginning [IN:11203]
  • chromedriver.exe locks a folder in Rapise\Temp, and the next execution of a test set fails to clean its folder [IN:11244]
  • DoSetText in LibSelenium may fail to enter text [IN:11291]
  • Add protection from orphaned test cases in Spira.json [IN:11294]
  • Navigator.DoDomFindBy... goes into an infinite loop when searching for all elements on a page with 3-level nested frames [IN:11342]

How Do I Get the New Version?

 

If you have any questions about the new version, please contact support@inflectra.com.