SOFTWARE TESTING
TEST PLAN AND TEST CASE DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
|
|
Action + Function + Operating Condition
|
|
|
Symptom + Action + Operating Condition
|
|
|
Action + Symptom + Operating Condition
|
|
|
Function + Action + Operating Condition
|
Detailed explanation-1: -A bug report template should contain the following fields: title, severity/priority, description, environment, steps to reproduce, expected result, actual result, attachments (screenshots, videos, text).
Detailed explanation-2: -#2) Bug Title This should explain all about what comes with the bug. The Bug title should be suggestive enough that the reader can understand it. A clear bug title makes it easy to understand and the reader can know if the bug has been reported earlier or has been fixed.
Detailed explanation-3: -Title. The bug report title should summarize the problem so that the reader gets a general idea of the bug just by reading the bug title. They should not have to read the whole report to understand what the problem is. Your bug report title should be precise and not too long at the same time.