What exists that will prove the existence of the error?
Have you provided both the expected results and the actual
results? Is there documentation that supports your expected results?Since you are writing a problem report it is obvious that you believe there is a problem. Provide anything you can that will
convince others also that this is indeed a valid problem.
Evidence may take the form of documentation from user guides, specifications,
requirements, and designs. It may be past comments from customers,
de-facto standards from competing products, or results from previous
versions of the product. Don’t assume everyone sees things the same
way you do. Don’t expect people to read between the lines anddraw
the same conclusions as you. Don’t assume that 3 weeks from now
you will remember why you thought this was a bug. Think about what it
is that convinced you that this is a bug and include that in the
report. You will have to provide even more evidence if you think
there is a chance that this situation may not be readily accepted
by all as a valid bug.
