--- Thomas Eyde <[EMAIL PROTECTED]> wrote: > > Testing is about functionality. Think of it: You do > refactoring, right? > The functionality is still the same, but the > appearence of the code is > different. The same should apply for GUIs. Test the > functionality, not > the appearence. I have not got that far, because I > can't figure out how > to easily set up a page in a certain state and then > test it. > > So for now the Humble Dialog Box is my way to do > GUIs.
There are two decouplings at work here - between the GUI Toolkit and GUI Layer, then between that and the Representation Layer (the Humble Dialog Box thing). GUI Toolkits exist to make changing GUI appearances easy. If you move a button, you don't need to move the code that reacts to the button. Agile development relies on making changes easy. But usability is sensitive to changes that programmers like. You can't guess that users will be as delighted as you about GUI changes. They prefer to take delivery of steadily growing features under GUIs that are as similar as possible. So, because GUIs are too easy to refactor, tests should be just a little sensitive to their changes. ===== Phlip http://industrialxp.org/community/bin/view/Main/TestFirstUserInterfaces _______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com To Post a message, send it to: [EMAIL PROTECTED] To Unsubscribe, send a blank message to: [EMAIL PROTECTED] ad-free courtesy of objectmentor.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/extremeprogramming/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
