> 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.
Are you saying that a GUI's appearence is not part of it's
functionality? I would think that as well as displaying the right
data, that data should be readable, and it should be readable on a
variety of screen resolutions on a variety of systems. Isn't this
part of the functionality of a GUI?
------------------
One of the things that got me thinking about this was code audiences.
The audience for the model code is other programs and other
programmers. It's what Joel would have thought of as a UNIX model.
But the audience for the GUI code is very different. It needs to work
for many types of people on many types of machines with many types of
input, some of them seemingly random.
I'm very different when I write GUI code. It's a completely different
hat. And I wonder, if all I did was write GUI code or I could drop
this "one size fits all" approach to programming, would I work in a
different way?
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/
