> How do you know your top level API tests are stable?

Because they cement the specifications of the project.

The only problem I see with my approach, is that clients tend to consider demo code as production ready.

But I may have problems to express my ideas properly here.

>Because they cement the specifications of the project.

My question is how do you know your specifications are correct/stable? You're testing all this code up until it is stable, how much of that testing remains in its original form?

Three thousand years of beautiful tradition, from Moses to Sandy Koufax, you're god damn right I'm living in the fucking past

I'm confused, unstable specifications result in an unstable project.

This can happen if communication is bad or priorities are messed up.

Starting with demos, POCs and tests for the main features should minimize that risk.

With some clients this still happens, but then it's their responsibility to pay for the extra costs.

Cheers Rolf
_{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :)
Wikisyntax for the Monastery}