in reply to Re^4: When Test Suites Attack
in thread When Test Suites Attack
Since we tend to write CPAN distros, our test suites are "unit-tests", but also are API tests. We use TDD wherever possible, so we immediately use and write document for our APIs. This is very much akin to the "integration-tests" you speak of. I can't tell you how often I have added features and/or changed APIs (and rewritten tests) because I can't test a specific scenario or the test "just feels wrong."
We are also starting to write each other's tests. For one, it means that the API has to pass someone else's eyes. stvn will think of usages that I just don't conceive of, and vice versa. Plus, it's so much easier to write code to pass tests than it is to write the tests in the first place. We did this for Perl6::Roles and we liked it a lot.
Our UAT tends to comes about because many of our modules are heavily used (Excel::Template, Tree::Simple, DBD::Mock, etc). If it doesn't pass muster, we hear about it.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?