[LRUG] Testing standards

[J. Pablo Fernández]

At the company I'm working right now there are no standards, except that you
are expected to write tests.

One policy I like is: no commits while the build is red (except to fix the
build of course). Obviously, you should run the tests before committing, but
hey! sometimes we forget, and sometimes the tests take half an hour to run
and almost nobody ever runs them completely.

About libraries... we have several projects with different libraries. The
big policy here is: don't add libraries just because. If the project uses
Test::Unit, don't use RSpec.

Then there are a lot of preferences. I prefer factories to fixtures,
test-unit to rspec but I like shoulda (both matchers and context). I'm
playing around with capybara. We'll see how that goes. Oh. please, no
cucumbers for me.

If you are setting the rules, goes for what works, which obviously mean,
what you like. If you are not, I think the golden rule is to adapt... write
rspec when everybody around is doing so, write test-unit when everybody
around is doing so, run away when everybody around is not writing test.

On Thu, Aug 25, 2011 at 16:46, Neil Middleton <neil.middleton at gmail.com>wrote:

> Hi All,
>
> Just a quick question really, and one that I'm sure could kick off a fight,
> but do you guys who work in teams have any testing standards that you stick
> to?  For instance, which libraries you use, what sort of tests & coverage
> you expect etc?  Do you have any requirements from devs before they commit
> or are you all fairly free and easy ;) ?
>
> Thoughts more than welcome.
>
> --
> Neil
>
>
> _______________________________________________
> Chat mailing list
> Chat at lists.lrug.org
> http://lists.lrug.org/listinfo.cgi/chat-lrug.org
>
>


-- 
J. Pablo Fernández <pupeno at pupeno.com> (http://pupeno.com)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20110825/de28e03a/attachment.html>