did my best to scan all responses, not wanting to be redundant...
i had trouble with understanding unit v. functional in years past (perhaps still do, but it feels better nowadays).
a wacky coworker put this reminder to us, "if your unit test 'poops in the sandbox' it is not a unit test". meaning, if the unit test altered info in a db, then it is a functional test.
i was initially incredulous/confused, "but, but, but, i've <b>got</b> to see if it works or not!"
in order to keep the sandbox clean, and keep the unit tests true to intent, i've had a good time using mockrunner (http://mockrunner.sourceforge.net/).
Flat View: This topic has 50 replies
on 51 pages
[
«
|
383940414243444546
|
»
]
Previous Topic
