At 01:44 PM 6/7/2005 -0700, Heikki Toivonen wrote:
Phillip J. Eby wrote:
> Okay, I totally give up. I can see that there is no way I'm going to
> convince everybody to stop calling all developer-written automated tests
> "unit" tests. (All unit tests are developer-written automated tests,
Maybe it's because we are using the Python unit tests framework, even if
we are not exactly running unit tests only.
Sure, I'll buy that. :) Unfortunately, I've been in the habit of thinking
when people talk about "unit tests", that they mean the more strict
definition, which then leads to confusion like me trying to write a
TestReactor to help you with something that then turns out to be an
integration test, for which it won't help at all. :( Not blaming you, or
anybody, just explaining my frustration.
At this point it's clear to me that it's not cost effective for me to keep
trying to convince people to change the terms they're already using,
although I don't plan to start using the term myself.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev