Comments on Questioning Software: Failure Usability

Very good mnemonic. Under audience you might want...

2011-09-01T10:10:18.235-06:00

Very good mnemonic. Under audience you might want to add a question such as this:

Localizable/Internationalization: Does the error display properly in other langauges, fonts, character sets, etc (when there is more text, or right-to-left text, etc)?

Another UI consideration: is the dialog consistent with the platform or operating system usability guidelines (such as for placement of ok/cancel buttons, etc?)

Another consideration: duration. I have seen error messages that disappear too quickly to read them. This might be obvious for self-timed items, but I've had situations when the message arrives while I am typing, and before I can stop, something I've typed dismisses the dialog. Hmm...

Testing Error http://www.sdtimes.com/default.aspx?...

2009-12-01T06:34:58.889-07:00

Testing Error
http://www.sdtimes.com/default.aspx?CustomError=404

F - Can not test, I dont know if the link is in their database

A - Pass, I came when I tried to access the link

I - Pass, no impact except for not reading the page

L - Can't test. This should be logged so that they can know which links people are trying to access but can't find.

U - Not so good. It looks very nasty and evil red. And it's very small. But it does draw attention to it by the annoying color.

R - Pass, It tells me to browse the page or search

E - A bit annoyed yes, and the color does not make it look any better

Summary:
All in all it's a decent error message which could be made nicer and bigger.

I agre that spellnig is importnat. I also udnerst...

2007-12-04T06:17:00.000-07:00

I agre that spellnig is importnat. I also udnerstnad that sometmies my figners mistyep tihngs. I try to fix tehm before I pubilsh but smoeitmes typos slip out – just like bgus into pordcution sotfwrae.

The example is an example error message for testing. It contains a spelling error. It contains grammatical errors. It contains confusing information. It is a bad error message. Pradeep created it an a testing exercise. It appears that you tested it for spelling. I hope you also test it for other problems.

Cheers

Ben

I got a problem with all the spelling errors on th...

2007-12-04T02:47:00.000-07:00

I got a problem with all the spelling errors on this blog. Even shown in your example error message. I think that correct spelling plays a major role in professionalism. Developers often get alot of errors, it is testers who should pick this up.

Microsoft Word should be able to assist you before you publish anything.

Cheers
DK

I haven't had a chance to use it yet, but it's *re...

2007-08-22T01:25:00.000-06:00

I haven't had a chance to use it yet, but it's *really* easy to remember. I like it!

I don't know if you've been following my blog, but I've got a couple up that I've had a lot of success with and two more on the way when I get a chance to write them up.

It's odd, I didn't like the mnemonics of guideword heuristics until recently, then all of the sudden they've become really central to how I think about, do, and teach performance testing. Maybe it's another one of those things that's like riding a bike. ;)

This blog takes longer to load than any I've ev...

2007-08-20T11:31:00.000-06:00
This blog takes longer to load than any I've ever visited.

Sorry about that. It was likely the embedded 5mb mp3 file in this post. I removed the embed and the audio is now available only as a link. Hopefully this helps. Please let me know if you encounter any other performance issues.

Thanks for the feedback.

Ben

This blog takes longer to load than any I've ever ...

2007-08-20T11:24:00.000-06:00
This blog takes longer to load than any I've ever visited.

Yep. The overlap is in the meanings -- not the le...

2007-08-20T00:14:00.000-06:00
Yep. The overlap is in the meanings -- not the letters themselves.

I think each one brings some meaning, emphasis, and/or point of view that the others do not. I have found that thinking about something from different angles is a good thing in that it helps me remember to think about things that I might otherwise miss. The overlap also helps me better think through the interaction between the parts of a system.

I see no overlap in the letters of your mnemonic. ...

2007-08-19T23:41:00.000-06:00
I see no overlap in the letters of your mnemonic. They literally do not overlap. What does overlap is the meanings of the guidewords in your heuristic that is served by your mnemonic.

A mnemonic is a memory aid. But beneath your memory aid is a problem-solving aid, the words that suggest what to think about.

There is some overlap among the meanings of the words, but you have to ask yourself if each word contributes something unique an valuable. If that is true, don't be concerned with overlap.

... and yes, there is some overlap amongst the let...

2007-08-19T15:14:00.000-06:00
... and yes, there is some overlap amongst the letters of the mnemonic.

:)

Shrini,

The F in FAILURE is intended to be ...

2007-08-19T15:11:00.000-06:00
Shrini,

The F in FAILURE is intended to be "Functional", as in functional testing of the condition that causes the error and functional testing of the error reporting. It goes beyond the event that causes the message to be reported and includes the functionality of the reporting mechanism: whether it be a dialog, a log entry, a change in flow, or something else.

The rest of the letters in FAILURE are more focused on usability questions.

Here's a very short version.

F Does the error detecting, reporting, and handling function as expected?

A Is the error reported at the appropriate time in an appropriate manner?

I Is the impact to the user communicated?

LIs the error appropriately logged? ... or not logged if that is desired?

U Is the error appropriately reported in the user interface in terms that the user understands?

R Is the user told how to recover from the error condition?

E Does the error reporting evoke the desired emotions? Could changes in the error reporting and handling improve the users emotional response?

Thanks for your comments. The input -- both good and bad -- of other testers helps me better communicate what I think about when I use the mnemonic.

Thanks,

Ben

Nice work Ben ---

I would attempt analysing...

2007-08-19T13:00:00.000-06:00
Nice work Ben ---

I would attempt analysing future error messages with this ...

Few suggestions for your pnemonic ...

The letter F in FAILURE is not quite "functionality". I would have something like "E" - Event.
When application throws up message in response to change in some of its own or related systems change -it could be an error message or just some infomration or acknowldegement. When such a messge is displayed - first thing I would ask is - "What happened", "what you (application) are trying to tell me? Did I commit any mistake? Do you need anything from me? and so on ..."

Second part of dialog - that happens between application and user is - "what should I do now"
that is recovery part.

So an error message at the least should explain what happened and then explain what steps the user needs to take following the message notification...

Shrini

Thanks James. I have been using these heuristics ...

2007-08-18T14:18:00.000-06:00
Thanks James. I have been using these heuristics for some time but just assembled them into a mnemonic. I will now try accessing the heuristics via the mnemonic.

I am very interested in whether or not it helps other people.

I applied the mnemonic to Pradeep's error message. I have written down most of my observations from my discussion about it with Pradeep. I will post my application of the mnemonic once more people have an opportunity to try it like you did.

Anyone else? Please try the mnemonic on the sample error and on real situations as you test.

Does the mnemonic help? Is it lacking?

The next step after creating a heuristic is to try...

2007-08-18T12:59:00.000-06:00
The next step after creating a heuristic is to try using it on a project. Until you've tested it under live fire, you don't know much about whether it will help.

I'll try using it on that error message as you suggested:

F - I can't tell if the error message functions properly, just from seeing the message. For instance, you may have been doing something completely unlike adding a contact when the message came up. Or perhaps the user already is a premium customer. However, it appears that the URL may be misspelled.

A - The message could be timed right, assuming that it came up when the user tried to add a contact.

I - The impact appears to be reasonably communicated. I like how it lists the other features that are disabled (is that list correct, though?)

L - I don't know if anything about this is logged. It may not be important for an error like this to be logged.

U - It's written in reasonable English. It explains the problem (assuming that problem really exists). The UI is a little crude. That may not be a big deal, unless this is a major product.

R - The error message appears to show how to solve the problem (but is the URL correct?)

E - It doesn't seem to trigger negative emotions in me-- unless of course I actually paid to use this thing.

Comments on Questioning Software: Failure Usability

Very good mnemonic. Under audience you might want...

Testing Error http://www.sdtimes.com/default.aspx?...

I agre that spellnig is importnat. I also udnerst...

I got a problem with all the spelling errors on th...

I haven't had a chance to use it yet, but it's *re...

This blog takes longer to load than any I've ev...

This blog takes longer to load than any I've ever ...

Yep. The overlap is in the meanings -- not the le...

I see no overlap in the letters of your mnemonic. ...

... and yes, there is some overlap amongst the let...

Shrini,The F in FAILURE is intended to be ...

Nice work Ben ---I would attempt analysing...

Thanks James. I have been using these heuristics ...

The next step after creating a heuristic is to try...

Shrini,

The F in FAILURE is intended to be ...

Nice work Ben ---

I would attempt analysing...