I think neither, but perhaps focus on problem forms (?) first.

Actually, I would focus on new stories first, then problem forms second.

I would work new stories "presenter-first" and get my TDD working from the
start.
For problem forms, I would get my unit tests in order including refactoring
to MVP if required.

Lastly, I would get my acceptance/story tests running in the same area...
plugging in at the presenter.

.rob.

On Mon, May 26, 2008 at 11:37 PM, Stephan Meyn <smeyn@...> wrote:

> Just a question to the group - if you are looking to start automating
> testing, you may not have the opportunity to invest in automating all
> you would like to test. So you look what kind of tests you'd want to
> invest in to optimize the benefits vs effort.
>
> So would you rather automate
> 1) simple tests, such as testing all the navigation works, or
> 2) complex test cases, such as processing a withdrawal of a payment
> from a superannuation account
>
> 1) would give you the ability to create a large number of small test
> cases, which could then be run after a build as a smoke test. Catches
> errors before the test team gets involved
>
> 2) automates stuff that are error prone to do manually. But it
> requires more effort to build and so you would create less tests with
> the same budget.
>
> given the two choices, which way would you go?
>
> Stephan
>
>
>


[Non-text portions of this message have been removed]