Solano CI vs. Test Kitchen
Related Comparisons
|
|
|||||
Favorites12
|
Favorites5
|
|||||
Hacker News, Reddit, Stack Overflow Stats |
||||||
GitHub Stats |
No public GitHub repository stats available
|
|||||
Description |
What is Solano CI?Faster Continuous Integration and Deployment with patented auto-parallelization. See results 10 to 80x faster. 14-day free trial. No credit card required.
|
What is Test Kitchen?Test Kitchen has a static, declarative configuration in a .kitchen.yml file at the root of your project. It is designed to execute isolated code run in pristine environments ensuring that no prior state exists. A plugin architecture gives you the freedom to run your code on any cloud, virtualization, or bare metal resources and allows you to write acceptance criteria in whatever framework you desire.
|
||||
Pros |
|
|
||||
Cons |
|
|
||||
Pricing |
How much does Solano CI cost?
|
How much does Test Kitchen cost?
|
||||
Companies |
What companies use Solano CI?
12 companies on StackShare use Solano CI
|
What companies use Test Kitchen?
6 companies on StackShare use Test Kitchen
|
||||
Integrations |
What tools integrate with Solano CI?
15 tools on StackShare integrate with Solano CI
|
No integrations listed yet
|
||||
What are some alternatives to Solano CI and Test Kitchen?
|
||||||
Latest News |
Deprecating Older Solano CLI Versions
October 06, 2017
Announcing Custom Worker Volumes
August 10, 2017
Migrating from Snap CI to Solano CI
April 05, 2017
|
|||||
Reviews of Solano CI and Test Kitchen
-
keightyGreat team to work with
June 22, 2015 16:36
Solano is a great CI tool, and it has become an essential part of our build process. The suite builds in parallel, which makes test runs fast. The support team is super responsive and helpful.
Ease of Use Documentation Reliability Support -
sdhullBetter than the rest, since forever
February 17, 2016 19:30
Some of the stuff I've enjoyed the most about Solano:
- turnkey parallelism out of the box, with very little setup required (ie, it's fasstttt with almost no work)
- in all, when I set it up 2 years ago, I found it much easier to set up than the competitor service we were using at the time (and I've set up a couple competing services since then -- this is is still the easiest)
- sane defaults, project auto-detection, extensive configuration available (versions of everything)
- useful parsed results that are sortable & filterable (ie, you can filter just to show failed specs)
- github integration (commit hooks + badges on PRs)
- cached dependencies (for ruby, it's the bundle by default but you can add custom stuff like assets)
- infinitely customizable (I set up a project to run specs for a mobile app I'm building. maybe not impressive to some of you but as a rails developer, I thought it was cool)
Ease of Use Documentation Reliability Support
How developers use Solano CI vs Test Kitchen
-
Airbnb uses Solano CI
"There are a ton of excellent strategies for speeding up Rails test suites—aggressive use of stubbing/test doubles, decoupling logic from models, avoiding loading Rails entirely—but given the size of our codebase and the velocity with which we’re moving, most of these weren’t immediately feasible. We needed a build system that would allow us to parallelize our test suite so that the real time taken to run the suite was manageable.
Our SRE team went through several different continuous integration solutions in the last year before settling on Solano.
Each of the previous systems had some issue: instability, memory consumption, poor DB management, poor parallelization, painful web UI, you name it. What Solano gives us is an on-premise solution with excellent native support for fanning out tests to multiple threads, running them in parallel, and then assembling the results. It has a great web UI, CLI support, and impressive performance. Since we started using it, our deploy workflow has grown noticeably faster, and the number of wails and anguished GIFs from frustrated engineers is at an all-time low."
-
