On 19/04/2010 22:13, Pat Maddox wrote:
Put the interesting bits in a basic Ruby class and test that, then make the
Rake tasks a very thin layer over the class.
On Apr 19, 2010, at 8:46 AM, Rick DeNatale wrote:
I released a new gem this past weekend which adds a new rake task for
Jeweler to generate a release announcement.
I was lazy and didn't write any specs, mostly because I couldn't
quickly come up with a reasonably way to write a spec for a rake task.
I was wondering if anyone had done some kind of testing harness for
Rake tasks with RSpec. I tried googling but kept coming up with stuff
about using the rake tasks provided by RSpec.
I tend to do what Pat suggested with Rspec. In Cucumber I've had cases
where I really wanted to run a rake task directly. This was pretty easy:
http://gist.github.com/373000
--
Joseph Wilk
http://blog.josephwilk.net
http://www.songkick.com
+44 (0)7812 816431
--
Rick DeNatale
Blog: http://talklikeaduck.denhaven2.com/
Github: http://github.com/rubyredrick
Twitter: @RickDeNatale
WWR: http://www.workingwithrails.com/person/9021-rick-denatale
LinkedIn: http://www.linkedin.com/in/rickdenatale
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
--
Joseph Wilk
http://blog.josephwilk.net
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
