Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Cut rake out of rspec/cucumber for CI builds.
When something environmental fails (i.e. not in an individual spec, but when the spec files are being loaded), the rake tasks craps out but does not include the backtrace of what failed. It's really annoying and hard to troubleshoot. This should work better.
- Loading branch information
1 parent
1bdaa8c
commit 2ac7a03
Showing
2 changed files
with
15 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
# Kill the whole script on error | ||
set -e | ||
|
||
# Setup vendored rspec-1 | ||
git submodule init | ||
git submodule update | ||
|
||
bundle exec ruby -w -I./spec -r./spec/capture_warnings -rspec_helper -S rspec spec --format progress --backtrace | ||
|
||
bundle exec cucumber | ||
|
||
bundle exec rake yard_coverage | ||
|
||
bundle exec rake check_code_coverage |