Cucumber would only be for the Acceptance/Feature level testing. We could use rspec or minitest for unit testing. The industry seems to be moving in the direction of Cucumber for Acceptance, Steak + Capybara for interface/integration testing, and rspec or one of the other suites like mini-test for more unit level testing. If there are other combinations/applications you are seening, please share! Since this is an educational project for all of us, it might be fun to test some pieces with one framework and others with another. Each groups who used different suites could then do presentations comparing and contrasting.
The main thing from a quality standpoint is that the code is tested.
regarding the pivotal tracker project, yes, that is probably a good idea.
On Fri, Jan 27, 2012 at 12:32 PM, arlen <[address removed]>
So it's a given we're going to use Cucumber? (Not a complaint, just a question. I usually stick with minitest/spec myself.)
On Jan 27, 2012, at 11:58 AM, Alexander Lemanski wrote:
> I think those are good next steps. So lets:
> 1. Start prioritizing features
> 2. Start Working on Cucumber
> Sorry, I didn't think about this before, but would it make sense to setup an open group on pivotal tracker?
In God we trust, all others must supply data
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by arlen ([address removed]) from RubyMKE.
To learn more about arlen, visit his/her member profile: http://www.meetup.com/RubyMKE/members/7503910/
To unsubscribe or to update your mailing list settings, click here: http://www.meetup.com/RubyMKE/settings/
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]