Now that we've talked about our high-level approach to testing, it's time to get into the details.
The fact is, it's usually very quick and easy to bang out an automated test that will verify some unit of code does what we expect... and that will be absolutely impenetrable to the next programmer who has to sort out why a previously-passing test is now erroring out. Complicating matters is that "good style" in tests is often very different---even diametrically opposed, sometimes---to "good style" for application code.
Fortunately, there are some easy-to-learn guidelines for making your Ruby tests self-explanatory, expressive, and maintainable. We've collected a few of these guidelines in this module.
Report
There was a problem reporting this post.
Block Member?
Please confirm you want to block this member.
You will no longer be able to:
See blocked member's posts
Mention this member in posts
Please allow a few minutes for this process to complete.
Responses