Test as long as you need it! Days count only when you use API. We want to make your developer life smooth with no unneeded interruptions like expired trial :)
Monthly you can save hours
and up to $
on faster development cycle.
I'd like to share with you my experience to optimise your CI pipeline. Please sign up and:
Founder of Knapsack Pro
We sum up the length of each of the CI node. So, if your test suite runs on 3 nodes and each takes 10 minutes, then the length is 30 minutes.
The soft limits are applied to the total usage across your suites. Test suites length means the total time run of each parallel node in all suites. The number of nodes means the total of all nodes used in all test suites.
Let's say your project has RSpec tests and you run CI build on a single machine for 40 minutes.
If you run the 40 minutes RSpec test suite CI build with Knapsack Pro on 2 parallel nodes (node 0 takes 20 minutes and node 1 takes 20 minutes) then your project fits 1 hour test suite plan because the total time of running RSpec test suite is 20 minutes + 20 minutes = 40 minutes per CI build.
If you have additional tests like Cucumber and they took 50 minutes then your both test suites take 90 minutes in total (RSpec 40 minutes + Cucumber 50 minutes). Then your project fits up to 2 hours test suites plan.
In other words, Knapsack Pro records total execution time from all your test suites (API tokens) executed across all parallel CI nodes. The total recorded time per CI build should fit up to the plan limit.
If you have one test suite for instance in RSpec and you run tests on 50 parallel CI nodes then you fit up to 50 parallel CI nodes limit.
You can run many concurrent CI builds for the RSpec test suite.
If you have 2 test suites, for instance in RSpec you run 30 parallel CI nodes and in Cucumber you run 20 parallel CI nodes then you fit up to 50 parallel CI nodes limit.
You can run many concurrent CI builds for the RSpec and the Cucumber test suite.
It's one of the parallel jobs (isolated server machine or Docker container) being part of the CI build. Knapsack Pro command is executed inside of each parallel job to run part of your whole test suite and thanks to that split all your tests across parallel machines. The configuration of parallel CI nodes depends on your current CI provider.
Knapsack Pro is CI provider agnostic. As long as you can define bash command per parallel job (parallel CI node) on your CI server then you can run Knapsack Pro with it. Knapsack Pro has built-in support for many popular CI providers.
There is no hard limit on the Knapsack Pro API side to cut you off if you exceed the parallel CI nodes limit or time usage limit. Thanks to that you can test various configurations for your project. If you happen to exceed limits or API usage would be much higher than for average customer then we will get in touch with you about plan upgrade.
The price is based on total time execution of all test suites across all your projects.
Feel free to try Knapsack Pro and I will contact you to better understand your project context and ensure the pricing is right for the value you get.
To qualify, your project needs just three things: