Comments on: Belly Wants to Eat Your Tests

By: Arti

Arti — Tue, 07 Sep 2010 09:31:30 +0000

Thanks, Matt. That worked.

By: Matt

Matt — Mon, 06 Sep 2010 18:25:33 +0000

Hi Arti,

Thanks for trying Belly. I'd love to hear any feedback you have.

The belly init command installs a file inside your project in order to hook into belly and send your results during test runs. You've uninstalled the gem but that file is still there (and still looking for the gem).

Try deleting the file features/support/belly.rb - that should be all you need to clean things up.

By: Arti

Arti — Mon, 06 Sep 2010 10:46:14 +0000

Hi Matt,

How does one uninstall belly? I removed the gem but when I try to run my features, I get the following error:

Using the default profile...
no such file to load -- belly/for/cucumber (MissingSourceFile)
C:/Test/Ruby/lib/ruby/siteruby/1.8/rubygems/customrequire.rb:31:in `gem_origin
al_require'

Thanks!

By: Callum Anderson

Callum Anderson — Tue, 24 Aug 2010 10:53:14 +0000

I tried to get round this problem by using manual tagging to run my tests in two batches. I would ensure my 30 minute build ran tests against all key features and recently fixed bugs - and each night my six hour suite would run so that I could see results in the morning.

However, the effort required to keep updating and fixing the two test suites is almost becoming too much.

I think tools like Belly and CukeMax are really going to help Cucumber turn the corner and start to alleviate the maintenance burden large test suites often entail.

By: Lenary

Lenary — Mon, 23 Aug 2010 17:22:45 +0000

This is rather cool in concept, though I am yet to try it out.