> Basically, these rules mean that 90% of the tests written > with JUnit are not unit tests :-) > > (I'm certainly not disagreeing with you, being the creator > of TestNG and all, but I just wanted to clarify...)
Yeah, depends on where you are, I guess. I usually convince teams to work like this rather early so the world looks better from where I sit. It's sort of like saying, "oh, grass never grows high" when you habitually mow your lawn.
I hope it's better than that, though. I mean, seriously, if every unit test talks to the database because that's the way the production code works, well, either those are big tests, there's not much layering in the system, or you're using a magical object mapping system. If the latter works speedily enough against the real store, more power to you, but in systems without that, well, it's just scary.
Flat View: This topic has 50 replies
on 51 pages
[
«
|
2345678910
|
»
]