Hello Friends, I want to share you one scenario. Suppose Testing team is performing Ad Hoc Testing and they find some issues. As we know that these new issues should not be part of our Test Case and Test Scenarios. Because we do random Testing from Users perspective. These issues may be Critical, Major, Minor. As I know If we face critical issues then we write Test Case for it. But we do not write for Major/Minor.
So Please tell me if we do not write Test Case for these Major/Minor issues/errors, then there should not be Test Case Name(TC-001) and Test Case ID(something like 12). So how should I send these defects to Development Team without having Test Case for it? Will it now look informal way? If you have understood the scenario, then try to share your ideas.
Thanks & Regards,
I am not sure if I understand your query clearly. Assuming that you are asking if tester finds an issue for which there was not any test case then how should we communicate about this issue specifically if the issue is minor/major and not critical.
In my opinion, severity of issue should not be a deciding factor whether to write test case for it or now. We write test cases for an application's features/functionality for the diff possible scenarios where there is a possibility for issue to occur irrespective of its severity as we can't predict every time severity of an issue.
Now coming to the point still even if we have considered all possible scenarios in our test cases, still we find an issue for which no scenario was covered in our test cases then itís always better to report it and add the corresponding test case for it so that it is not missed out in subsequent cycles/phases. Always remember as a QA our role is to improve quality of the application, a QA/tested should act like a 'Gate Keeper'.
Someone told me once as QA/tester our responsibility is to report the bad news as early as possible without delaying [img]/images/graemlins/smile.gif[/img]
Please revert if I have misunderstood your question.
Thanks mbalajiwale_InfoCepts, You have understood the scenario exactly for the reason which I have posted it.As you said yourself
"if we have considered all possible scenarios in our test cases, still we find an issue for which no scenario was covered in our test cases then itís always better to report it and add the corresponding test case for it so that it is not missed out in subsequent cycles/phases."
So my doubt is clear and I would like to say thanks for your suggestion and same way I want to repeat your last line as you said.
"Always remember as a QA our role is to improve quality of the application"