| Issue 58: | Documentation: what should go in your tests? | |
| 1 person starred this issue and may be notified of changes. | Back to list |
|
we need more documentation on what should go in your tests. testing patterns, what assertions to use, etc. there's good stuff to draw from in Test Driven. i can add that. rankin made a good point about not wanting to dig through the framework to find what to use in the tests". i think even just getting a simple easy no fluff page up there with the 3 or 4 main assertions you use would be good for now. you know... assertTrue, assertEquals, assertFalse, and fail(). they're the ones i use in like 90% of my tests. anyone feel like jamming this one out or at least getting it started?
Feb 11, 2008
Project Member
#1
virtix
Feb 11, 2008
I'll give it a wack ...
Owner:
virtix
Cc: -virtix marc.esher
Feb 11, 2008
...and I'm only using assertTrue and assertFalse. My components actually have an isEqual method in them as well as a sort of mock builder. I guess I'm doing a lot of things that really could go into the unit testing process. I think Marc has things worked out so he gets most if not all of his testing while working done in the framework. I'm not quite there yet.
Feb 11, 2008
and for what it's worth, with cf, I usually know if I have two handles on the same object, so my isEqual() actually compares properties instead of object ids or something like that. I think that must be more important in java.
Jan 22, 2009
getting there and wiki should help!
Status:
Fixed
|
||||||||||