开云体育

It's ALL jargon! In the first meaning (in most dictionaries I checked) of "language peculiar to a particular trade profession or group,"

rather than in the sense of something negative or not understood.

The "micro-test" movement has grown rather large, so I think you should critique it (if you want to) by using the definitions that

already exist, not just what the word "sounds like."

Now I'll whine too. :-)

Our TDD, XP and Agile movements have been plagued by the search for terms, which everyone will automatically understand

(in the same way we understand them) upon first encountering them. There really are no terms like that. In the rather basic

dictionary I have by my desk, there are 14 definitions of "test" and 13 for "unit." ("Behavior" has only four, which will make some

proponents happy, but they are mostly pretty non-specific and don't include "Category for which Charlie used to get a low

grade on his report card!")

Generally, to understand the "jargon" of a group, you need at least a definition. Sometimes you may need to read an article,

have a conversation or even digest a book or two. While that may sound like a problem, I've never seen it arise within the

actual teams that do the work. Of course, when we get on the internet with people following different usage, we may not

immediately understand one another. I think that's just a fact of life. We should mitigate it by not calling "hot" things "cold"

or "fast" stuff "slow" or "small" tests "big". But non-self-explanatory terms are easily bested by people who work at understanding.