RE: [agile-usability] Re: just one bug's enough to make a program useless
- Maybe PhotoShop defended the "feature" where Undo-Undo redoes the undid
That's actually useful in some situations, because you can do "blink
comparator" from one keystroke.
Interesting point. Do you think this is something that you would be
likely to find out through upfront design and paper prototyping?
My guess is that this is exactly the kind of thing that does not become
apparent until (even to the end user) until you look at real users
laying their hands on the real thing and trying to carry out a real
- --- In email@example.com, Brian Marick <marick@t...>
> P.S. Making changes to improve the usability for testers does haveIn the situation I was thinking about, making changes to the delivered
> business value, unless their time costs nothing. I have some faith,
> but no evidence, that it would also improve the code, much like
> catering to JUnit or Fit does.
product to better support testers would have broken business rules in
the application. Basically it would have made it easier/faster for the
tester to set up and tear down test data by forgoing some of the rules
around creating and deleting - and also installing quick navigation to
jump from creation directly to transaction entry, again, inapropriate
for our app, but workflow the testers did often.
Alain is right that lots of these tedious bits of testing should be
You're right that spending a little money to help testers complete
their work faster - or not go crazy doing it - is a good idea. We just
need to know why we're doing it. If it was a feature strictly for
testing, I'd want some way to hide or disable it from a production
But, your point is well taken. Also Michael's point you referred to as
- Alain wrote:
> By their nature, bugs cannot be caught by design. They can only beMany bugs (both code bugs and usability defects) can be avoided by effective
> caught after the buggy implementation has been implemented. This is one
> of the great advantage of early delivery and TDD. They allow you to get
> actual running software in the hands of users early, and catch bugs
> early on in the process.
design practices and found prior to having running software through
inspections and walkthroughs. Multiple research studies and extensive
practice have shown inspections to be more cost effective than is testing
for finding and eliminating bugs (both kinds).
--Larry Constantine, IDSA [mailto:lconstantine@...]
Chief Scientist | Constantine & Lockwood, Ltd.
> -----Original Message-----[mailto:firstname.lastname@example.org] On Behalf
> From: email@example.com
> Of Desilets, Alainuseless
> Sent: Tuesday, 03 January 2006 11:40 AM
> To: firstname.lastname@example.org
> Subject: RE: [agile-usability] just one bug's enough to make a program
> How can we usabilitists catch these blind spots in design, before they
> lose us customers?
> -- Alain:
> Sorry for late response... Catching up on pre-Xmas break email.
> Yahoo! Groups Links