| |
I hate it.
Unit test this. Unit test that.
Let's put "unit" in our testing framework so we can test "units" cuz that's all ANYBODY is EVER going to test.
Testing outside of the "unit" is forsaken. Thou shalt never test more than a unit. Test more than a unit and ye shall be pelted with stones and crucified.
Let's see... What do we have here for unit test frameworks:
brentUnit (even Brent Strange can have a unit testing framework)
JUnit (notice the word unit)
nUnit (look at me, I test units)
mbUnit (I'm a follower, I can't think outside of the box. Uhm...let's test units.)
csUnit (CHEESE & RICE, this is INSANE)
...
OH HELL...Just go here for the gi-hugey list:
http://en.wikipedia.org/wiki/List_of_unit_testing_frameworks
You back? See what I mean? There's like one-cajillion testing frameworks that are for "Unit Testing".
Unit, unit, unit. It's freakin' beyond dumb.
Tell me...What happens once this developer phase of "Oh, I gotta go write some unit tests, with my unit test framework so my code is better" evolves to tests beyond "unit"? You know, like writing some tests that are "integration" or "functional? It'll happen people.
IT'S HAPPENING PEOPLE.
I, and others have been using "unit testing" frameworks as an automation test harness for years now. All kinds of tests.. Tests that aren't "unit".
Yeah, insane. Unheard of I know. What? You going to crucify me now?
Drop the unit. Get over it. These are "Testing frameworks".
P.S.
Microsoft, nice namespace: Microsoft.VisualStudio.TestTools.UnitTesting
P.P.S
Don't give me any crap about how "unit testing frameworks" are for developers. Good one rocket scientist...Let's create separate frameworks to basically do the same thing. One for Dev, one for QA. Brilliant... |
|