CustomerAcceptanceTest

In the beginning, there was the FunctionalTest, and that was good enough for ExtremeProgrammingExplainedEmbraceChange.

Then (like the name-shift from UnitTest to ProgrammerTest), eXtremos learned they needed to distinguist FTs written by programmers and those specified in conjunction with UserStories. So they changed the name to AcceptanceTest, and thence to CustomerTest.

Befuddled teams in the trenches hence started calling them CustomerAcceptanceTests.

The best are the kind non-programmers can author on the fly. See http://fitnesse.org