I can't believe this page didn't exist already.
Maybe that's because the term is not in wide use.
calls this a
. It's very useful when getting ready to refactor some
that is not yet covered by tests. (Yes, that's a tautology.)
When developing with a new API, write a test that verifies your expectation of how that API will behave.
has written about his
I think the terms are distinct. I've read
book now (highly recommended, I showed it to my CEO, but I don't think he got what I was getting at!) and I tend to do
[s] to explore a problem domain - not necessarily as a precursor to refactoring. The example given about
is something that is documenting knowledge about a system as per
[s], but those would typically be put in place as a safety net when refactoring. With
, there is no intent to refactor - just document.
of this page (last edited
February 13, 2007
with title or text search