We’re using a chef-repo and testing every cookbook from our Jenkins build server on every commit, but it takes upwards of 14-15 minutes to run all of our spec tests (for ~450 examples).
Are there any good ways to speed up our tests for quicker feedback?
Or, are there bad testing practices to watch for that could be slowing down our spec tests?
Thanks,
Curtis
On Feb 12, 2014, at 8:54 AM, "Stewart, Curtis" cstewart@momentumsi.com wrote:
We’re using a chef-repo and testing every cookbook from our Jenkins build server on every commit, but it takes upwards of 14-15 minutes to run all of our spec tests (for ~450 examples).
Is that with parallel rspec or without?
--
Brad Knowles brad@shub-internet.org
LinkedIn Profile: http://tinyurl.com/y8kpxu
That’s without running/using parallel_tests.
Curtis
On Feb 12, 2014, at 9:32 AM, Brad Knowles <brad@shub-internet.orgmailto:brad@shub-internet.org> wrote:
On Feb 12, 2014, at 8:54 AM, “Stewart, Curtis” <cstewart@momentumsi.commailto:cstewart@momentumsi.com> wrote:
We’re using a chef-repo and testing every cookbook from our Jenkins build server on every commit, but it takes upwards of 14-15 minutes to run all of our spec tests (for ~450 examples).
Is that with parallel rspec or without?
–
Brad Knowles <brad@shub-internet.orgmailto:brad@shub-internet.org>
LinkedIn Profile: http://tinyurl.com/y8kpxu
There's literally a section of the README entitled "Faster Specs": GitHub - chefspec/chefspec: Write RSpec examples and generate coverage reports for Chef recipes!
Thanks,
Seth Vargo
Release Engineer, Chef
@sethvargo
On Feb 12, 2014, at 11:22 AM, Stewart, Curtis cstewart@momentumsi.com wrote:
That’s without running/using parallel_tests.
Curtis
On Feb 12, 2014, at 9:32 AM, Brad Knowles brad@shub-internet.org wrote:
On Feb 12, 2014, at 8:54 AM, "Stewart, Curtis" cstewart@momentumsi.com wrote:
We’re using a chef-repo and testing every cookbook from our Jenkins build server on every commit, but it takes upwards of 14-15 minutes to run all of our spec tests (for ~450 examples).
Is that with parallel rspec or without?
--
Brad Knowles brad@shub-internet.org
LinkedIn Profile: http://tinyurl.com/y8kpxu
Awesome, thanks for the heads up.
Just doing some google searches on 'faster specs’ didn’t turn that up. Not sure why I hadn’t checked there to begin with!
I’ll check out the cacher functionality to see if that helps speed things up.
Thanks again,
Curtis
On Feb 12, 2014, at 11:06 AM, Seth Vargo <sethvargo@getchef.commailto:sethvargo@getchef.com> wrote:
There’s literally a section of the README entitled “Faster Specs”: https://github.com/sethvargo/chefspec#faster-specs
Thanks,
Seth Vargo
Release Engineer, Chef
@sethvargohttps://twitter.com/sethvargo
On Feb 12, 2014, at 11:22 AM, Stewart, Curtis <cstewart@momentumsi.commailto:cstewart@momentumsi.com> wrote:
That’s without running/using parallel_tests.
Curtis
On Feb 12, 2014, at 9:32 AM, Brad Knowles <brad@shub-internet.orgmailto:brad@shub-internet.org> wrote:
On Feb 12, 2014, at 8:54 AM, “Stewart, Curtis” <cstewart@momentumsi.commailto:cstewart@momentumsi.com> wrote:
We’re using a chef-repo and testing every cookbook from our Jenkins build server on every commit, but it takes upwards of 14-15 minutes to run all of our spec tests (for ~450 examples).
Is that with parallel rspec or without?
–
Brad Knowles <brad@shub-internet.orgmailto:brad@shub-internet.org>
LinkedIn Profile: http://tinyurl.com/y8kpxu