Process documentation needed: automated test suite

[denise]

crschmidt pointed out in his bug walkthrough that the process of running the automated test suite is not very well documented! And I agree; I know I don't run the tests when I'm patching things since I don't really know much about it, and I don't contribute tests along with my code because I actually don't know how to write them or what they should do. I am probably not the only one! (The only thing I know about the test suite is that you shouldn't run it in production because it does weird and wonky things to the database.)

I do know that our test suite coverage is not extensive at all, and we've talked before about moving to a more test-driven devlopment mindset. If anybody wanted to write up some documentation on the Wiki about both how to run the tests (and what you should look for) and how to write new tests (and when you should), that would be awesome and I would love you forever. (Well, I mean, I love you all forever already. But I'd love you more forever.)

Comments

[exor674]

I think we really need to fix our tests to not corrupt the database before we start using them more. Because I will not be running the tests ( or only running select tests ) until they can be run safely -- especially after the next time I reset my database.

( forex: momji did NOT post this post on my dev env: http://momijizukamori.dwdev.andreanall.com/ )

[denise]

I maded a bug for that: http://bugs.dwscoalition.org/show_bug.cgi?id=4439