Following on from Hadi's post, I found this recent blog on the same topic. It says pretty much the same thing, and acts as a good re-enforcement to the general point, which is to give your tests good names so that the next chap who looks at the code understands what the code being tested is supposed to do. It's such a valuable addition to the project documentation.
Exactly which form you choose isn't really that important, providing that it is both descriptive and consistent. What do you use for your test names?
Posts
No comments:
Post a Comment