Run Rapise tests in the cloud, in parallel, without managing infrastructure
Keep authoring in Rapise. Run your suite at scale on Testery, the cloud execution platform for teams that already use Rapise. No execution machines, browsers, or CI plumbing to stand up and maintain.
> testery run --framework rapise
→ discovered 48 Rapise test projects
⏻ Running on 12 cloud runners, browser managed
✓ 46 passed ↻ 2 retried· 5m 18s
⏻ Screenshots and logs collected.
Your team writes great Rapise tests. Scaling them is the bottleneck.
Building the tests is the fun part. The slog is running them at scale: execution machines to provision and patch, browsers and drivers to keep current, CI integrations to build, and suites that crawl when run one at a time. Testery is the cloud execution platform that takes that off your plate. As an Inflectra partner, Testery runs your Rapise tests at cloud scale, with no test lab to maintain.
From your Rapise project to a parallel cloud run
Four steps, no execution agents to install.
- 1
Author your tests in Rapise
Keep building tests in Rapise exactly as you do today, codeless with RVL or scripted in JavaScript. Nothing about authoring changes.
- 2
Put your Rapise project in a repo
Commit your Rapise test project to your Git repository. If your test cases are documented in Spira, connect Spira instead and Testery pulls them.
- 3
Connect it to Testery
Point Testery at your repository and select the Rapise framework. There is no execution agent to install and no machines to register.
- 4
Run in the cloud, in parallel
Testery provisions managed runners, executes your suite concurrently, handles the browser, and collects screenshots, logs, and pass or fail results.
Parallel execution, zero infrastructure
Cut hours to minutes
Shard your Rapise suite across many cloud runners. A multi-hour sequential run finishes in minutes when it runs in parallel.
No machines or browsers to manage
Testery provisions and manages the execution environment and browser, so there are no runners, drivers, or grids for you to keep online.
Trigger from anywhere
Run from the CLI or REST API, on every pull request, on a schedule, or on deploy. Wire it into CI/CD without building or maintaining the integration.
Screenshots, logs, and trends
Every run collects screenshots and logs, with pass and fail history and trends in one dashboard for fast triage.
Flaky tests handled
Intelligent retries and flaky-test detection keep large suites trustworthy as you scale.
Works with Spira
Automate the test cases documented in Spira, then run them on Testery, with results flowing back to Spira.
Run Rapise and open-source tests side by side
Mix codeless Rapise tests with engineer-written suites and run them all on Testery.
Trusted on large, complex suites
Testery is the best way to run our large, complex test suites.
Making the case to your team? See the cost and velocity impact of moving Rapise execution to the cloud.
See the business caseRunning Rapise in the cloud, answered
Can I run my existing Rapise tests on Testery without rewriting them?
Yes. You keep authoring in Rapise, codeless with RVL or scripted in JavaScript, and Testery executes your existing Rapise project as-is. Point Testery at your repository, and it provisions the environment, runs the suite in parallel in the cloud, and streams results back. You can run open-source frameworks like Playwright and Cypress on the same platform too.
How does Testery run Rapise tests in parallel?
Instead of configuring a fleet of execution hosts and max-parallel limits yourself, Testery shards your suite across cloud runners and runs them concurrently. You set the parallelism you want and Testery scales the runners up and down for that run, so a suite that took hours sequentially can finish in minutes.
Do I have to maintain Windows machines and browsers to run Rapise at scale?
You author in Rapise on your workstation as usual. For running at scale you do not stand up or maintain a fleet of execution machines, browser versions, or drivers; Testery provisions and manages the execution environment on demand, so you get capacity without owning the infrastructure.
How does Testery fit into my CI/CD pipeline?
Testery integrates with any pipeline that can make an API or CLI call, so you trigger a run on every pull request or as a build or deploy step and it reports pass or fail back to the pipeline as a status check. There is no execution agent to install on your CI workers and no orchestration scripts to maintain yourself.
Can I trigger Testery runs from the command line or an API?
Yes. Testery offers a CLI and REST API so you can kick off Rapise test runs from scripts, pipelines, or deploy hooks. You can also trigger a run on every pull request, schedule runs on a cron, run on deploy, or chain a run to follow another.
Does cloud execution collect screenshots and logs?
Yes. Testery captures screenshots and logs from each Rapise run and surfaces pass or fail results, with history and trends in the dashboard so you can triage failures quickly.
We document manual test cases in Spira. Does that still work?
Yes. Keep documenting your test cases in Spira and automate them in Rapise, then run them on Testery for scalable cloud execution, with results reported back to Spira.
Run your Rapise suite in the cloud.
Create a free Testery account, connect your repo, and run your first parallel Rapise suite in minutes.