If some function doesn't work according to user needs, then it is a bug. Period.
Now the gray areas.
If that same function still serves the user's needs if used in some other ways (albeit not exactly
according to user's mouse-clicking habits), it depends.
If I'm given time and resources to fix the issue, then it is a bug. If I don't have time and
resources to fix it, then it is... erm... not a bug. :P
Jonathon
BJ Freeman wrote:
Most bugs arise from mistakes and errors made by people in either a
program's source code or its design
we all accept that if the code breaks it is a bug.
For applications that have UI, it is also a failure if the person using
the application is not given the input necessary to put correct data and
then gets an error message say they should. This to me is a design bug.
So I put to you.
is it important to include how a user might use the application
inappropriately if there is not the correct information for the user
interact without getting error messages.
if so is this considered a bug.
