Run 1-hour tests in 2 min on your current CI server with optimal parallelisation Starting at ~$0/hour.
Run faster CI builds on your current CI server by doing the optimal split of your tests across parallel CI nodes (parallel jobs).
Knapsack Pro Queue Mode ensures each of your parallel CI nodes completes test execution at a similar time so there is no bottleneck in your CI pipeline.
Before Knapsack Pro
After Knapsack Pro - saved 7 minutes per each CI build
See the difference between Regular Mode and Queue Mode for running parallel tests.
Knapsack Pro is a wrapper that allows running tests in the optimal time across parallel CI servers with popular test runners.
Ruby & Ruby on Rails supported test runners:
Custom integration with Knapsack Pro API:
See the installation guide for your test runner.
You can run tests at full speed and in the shortest time with your current CI provider thanks to built-in integration for:
No matter if you are testing your app with databases like Redis, Postgres (PostgreSQL), MySQL, MongoDB, etc. Most likely, you can run tests in parallel on your CI, and you can log (logging) tests data into the Knapsack Pro user dashboard about executed tests. When your CI allows you to schedule tests (with a cron scheduler-like tool), you can also run your tests periodically in the shortest time with parallelisation.
Network issues? Not a problem, run tests anyway! Auto switch to the Fallback Mode to not depend on Knapsack Pro API.
Fallback Mode guarantees each test file is run at least once across parallel CI nodes. Thanks to that you know if the whole test suite is green or not.
Knapsack Pro is fault-tolerant and can withstand possible CI instance preemptions (shut down) when you use highly affordable CI nodes like Google Cloud Preemptible VMs or Amazon EC2 Spot Instances.
Thanks to that when you retry a parallel job that was shut down you can run on it exactly the same set of tests.
Knapsack Pro collects test timing data for each parallel CI build. You can see CI builds for each commit and branch name.
See CI build metrics in the user dashboard to detect bottlenecks and find slow test files that can be split into smaller files to better distribute them across parallel jobs.
If your CI provider allows retrying only one of the failed parallel jobs then you can retry failed CI node with the same subset of tests instead of running the whole CI build again thanks to Knapsack Pro remembering what was executed on that parallel job.
You can export test suite timing data from Knapsack Pro API for your historical CI builds if you like.
The Knapsack Pro add-on can be attached to multiple Heroku apps so your developers can use it with multiple projects. You need to generate a new API token for each project’s test suite in the Knapsack Pro user dashboard.
The available application locations for this add-on are shown below, and depend on whether the application is deployed to a Common Runtime region or Private Space. Learn More
|Region||Available||Installable in Space|
Need a larger plan? Let our customer success team help! Learn more.
To provision, copy the snippet into your CLI or use the install button above.