A subset of the C3 AcceptanceTest''''''s, run before code release.  It runs a bit too long to wait for, so we go out for coffee.  We changed our process to require this when we went to production, because we wanted to be sure we didn't break the production system.  Since we push code to production only about weekly, the CoffeeTalk suite gives us an early warning, when we know what has changed to cause the problem.  We run the full suite of AcceptanceTest''''''s, in GemStone, before code push. -- RonJeffries

Someone touched this page, drawing my attention back to it. I wonder whether we need to find a better way to be sure the system works perfectly than running lots of paychecks. How could we do that, I wonder ...

''Isn't the Xp way "one wonder at a time"?'' :) :)

----

''"run before code release"'' - does that mean at task integration time?

----

Could you please explain a bit more about CoffeeTalk please. Is it like JUnit? What can/not it do? Where can I get a copy to try? Is the world round?!