aidy lewis wrote:

> True, but if we implement story or scenario driven development then
> these tests lead development. A change in the tests means a change in
> development - not the other way round! I know for sure you are not
> saying; not automate through the browser and validate user
> requirements?

Two big points:

- the first tier of tests must cover as many features as possible, and
be super-fast to run

- test cases must be as close as possible to the tested code.

Put them together, and you should only test GUI things thru the GUI. Never test
biz logic only thru the GUI.

These rules imply "acceptance tests" are _not_ "thru the GUI tests". Pro testers
must work the test rig itself to add their coverage.

--
Phlip