Questions regarding manual testing

Question

Q1. If tester have no requirement, how he will test?

Q2. Please give the example of "Not a bug".?

Answer 1

1. Try test good, predict all cases of input data, try do this most better you can.
2. Feature is not provided in documentation but result of this is good, this is not a bug.

Answer 2

1. Write down assumptions about requirements, then make a test plan off of them. Is there product documentation? If so, that can be a good source of requirements.

2. A good bug report states:

   • What I did, step-by-step
   • What I saw when I did it
   • What I expected to see

"Not a bug" is a response if (c) isn't a correct expectation, and (b) was.

Answer 3

Test against the functional spec and the design specs and the proposal documents. Then demand requirements :).

Answer 4

In all honesty, it sounds like you need training from your QA manager, or whomever you report to.

Answer 5

Q1. If tester have no requirement, how he will test?

When we are testing, essentially what we want to know is 'Is there a problem here?' A requirements document can be a very good source for answering that question, but you should not limit your self to the requirements document.

If the software crashes constantly, and you look at the requirements document and can't find the requirement that says 'the software shall not crash', are you going to report the problem or not? This is a very extreme example, but there are many things that the software will do that may be undesirable, and there is no specific requirement in the document.

In the absence of requirements (or complete requirements), you could try using Heuristic Oracles. Take a look at these article:

http://www.informit.com/articles/article.aspx?p=463947