Hi, I'm starting up a new project and getting my infrastructure in place, setting up teaspoon. Since I'm using chruby my gems aren't excluded by the default config.ignore, so I added a pattern (%r{/gems/}). I also customized coverage.output_path but aside from that it's just the vanilla installation -- I haven't even written any specs yet!
I found that running bundle exec teaspoon ignores the gems as expected, but running rake teaspoon includes the gems in the coverage report. rake teaspoondoes however respect coverage.output_path set in the same config block.
Any thoughts? Is this a bug or might there be there something about my environment or setup that's causing trouble?
Thanks!
TL;DR: Here's a shell session illustrating the issue. With annotation interspersed but otherwise verbatim:
versions...
$ teaspoon --version
1.1.1
$ ruby --version
ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin14]
$ sw_vers
ProductName: Mac OS X
ProductVersion: 10.11.1
BuildVersion: 15B42
$ rake teaspoon
Starting the Teaspoon server...
Puma 2.14.0 starting...
* Min threads: 0, max threads: 16
* Environment: test
* Listening on tcp://0.0.0.0:53831
Teaspoon running default suite at http://127.0.0.1:53831/teaspoon/default
Finished in 0.00200 seconds
0 examples, 0 failures
OOPS! lots of code in the summary, it's almost all from the gems...
$ bundle exec teaspoon
Starting the Teaspoon server...
Puma 2.14.0 starting...
* Min threads: 0, max threads: 16
* Environment: test
* Listening on tcp://0.0.0.0:53858
Teaspoon running default suite at http://127.0.0.1:53858/teaspoon/default
Finished in 0.00200 seconds
0 examples, 0 failures
YAY! as expected, coverage only includes the app code...
Hi, I'm starting up a new project and getting my infrastructure in place, setting up teaspoon. Since I'm using chruby my gems aren't excluded by the default
config.ignore
, so I added a pattern (%r{/gems/}
). I also customizedcoverage.output_path
but aside from that it's just the vanilla installation -- I haven't even written any specs yet!I found that running
bundle exec teaspoon
ignores the gems as expected, but runningrake teaspoon
includes the gems in the coverage report.rake teaspoon
does however respectcoverage.output_path
set in the same config block.Any thoughts? Is this a bug or might there be there something about my environment or setup that's causing trouble?
Thanks!
TL;DR: Here's a shell session illustrating the issue. With annotation interspersed but otherwise verbatim:
versions...
coverage configuration... custom output path & ignore gems:
run teaspoon using rake...
OOPS! lots of code in the summary, it's almost all from the gems...
...and the html output includes a bunch of gems (but notice the custom output path!)
now run teaspoon using bundle exec...
YAY! as expected, coverage only includes the app code...
and similarly, the html report doesn't include the gems: