Comments on Test This Blog - Eric Jacobson's Software Testing Blog: Test This #3 – Change Your Mind

Kish252, There are so many flavors of dropdown me...

2009-04-17T16:40:00.000-04:00

Kish252,

There are so many flavors of dropdown menus it's hard to understand your statement.

Selecting a value from a dropdown may be optional, allowing the user to type items not in the dropdown. In that case, they may be able to delete their values without having to select a value like "empty".

Update, but yeah, it's a pretty standard way of lo...

2009-04-17T12:17:00.000-04:00

Update, but yeah, it's a pretty standard way of looking at data in applications. If you don't want to include one of those operations, then you better have a good reason that everyone agrees with.
Undo is a special case and generally avoided, I think, because of complexities (how many levels? some operations and not others? when are changes committed? etc.).

And "Too bad!" cuts both ways as you're realizing! It's fine if ideas and warnings about user interaction are overruled, but if those ideas and warnings constantly come back to haunt, then something needs to change to incorporate future warnings and ideas.

CRUD: Create Read Update Delete Stuff a basic web...

2009-04-17T12:05:00.000-04:00

CRUD:
Create
Read
Update
Delete

Stuff a basic web app does. If you've ever played with Rails, this is the functionality it automatically creates.

Yep. Nice post. This is something I test for ever...

2009-04-17T04:09:00.000-04:00

Yep. Nice post.

This is something I test for every time I see anything like this. There's a common assumption also that the customer knows what they are doing. The happy path often does work. The unhappy/forgotten/got something wrong path often doesn't.

Rob..

Thats why...i suggested my Dev's that use "Select ...

2009-04-17T02:49:00.000-04:00

Thats why...i suggested my Dev's that use "Select from List" for all drop-downs( Mandatory and Optional).

Problem simply solved.......

Is it right eric??

Good point, Alex. Testers should be asking the wh...

2009-04-16T20:45:00.000-04:00

Good point, Alex. Testers should be asking the what-if-user-makes-mistake questions in the requirement walkthroughs. It's possible someone may even listen. Or you may get the usual answer..."Too bad!".

CRUD? Create, Read, Undo, Delete?

I completely agree. This is indeed a role for tes...

2009-04-16T13:48:00.000-04:00

I completely agree. This is indeed a role for testers, and it's something that should be brought up when the feature is first devised, not after the feature finds its way into production code.

Standard CRUD!