Run the right tests for a change and nothing more!
On each change, the Launchable AI ranks tests by importance to code changes and allows you to create a unique subset (based on this ranking) in real-time. Run a fraction of your test suite while still maintaining high confidence that if a failure exists one will be found.
Reduce a 30 min pre-merge suite to 6 min
Reduce a 5-hour nightly suite to 1 hour on each pull request
Shorten test feedback delay by running tests that are likely to fail, first.
Subset long-running suites and shift-left. Run a subset on every PR or at the top of each hour.
Move a subset of your long-running UI suite earlier in your development cycle.
Be more agile without sacrificingquality
This graph a customer that is able to run 20% of the tests with Launchable to get 90% confidence that a failure will be found if one exists for a change. The practical outcome is that quality increases because you can test more often.
In addition to getting 100% confidence once a day, you can get 90% confidence every hour
Remove bottlenecks & double or triple hardware capacity
Hardware utilization drops when you run a smaller percentage of tests, effectively doubling or tripling resources. This allows you to reduce queue times and handle the same load with a third of the machines, or run 3 times the current load with the same hardware.
Mobile software: run tests with fewer mobile devices (Android and iOS)
Server-based software: run on fewer VMs and machines