[Wtr-general] Best practices for structuring GUI models?

[Bret Pettichord]

philip reed wrote:
> When I sit down to implement this my perfectionism gets all caught up
> in questions like, "Do I need a separate class for my client's
> specific site and another for the Sendcard
> UI in general?" (so that other sendcard sites can easily reuse the
> same code) or stuff like that.
>   
I used to have the exact same problem.

Now i test-drive all my "gui models" and testing frameworks with simple 
tests. These help me clarify the syntax i want to use and then once they 
work i can tweak them and the libraries until i get something that not 
only works, but is also elegant. The stuff i use a lot gets refactored a 
lot until i am happy with the design. The stuff that i don't use much 
retains a certain cruftyness.

To specifically address your dilemma, You should hard-code my tests to 
work with your client's site and then only generalize the code when you 
also need to get it to work with the Sendcard UI. One thing at a time.

In other words, I agree with everything Chris said. The only problem I 
have with Kevin's article is that it is written somewhat from the 
perspective of developer-testing. I would love to see a similar article 
directed more on testers. Perhaps Chris can write it.

Bret