- Why do you need 2 days to write test cases? You already have the SRS/BRS/FRS. You just copy and paste the text from it.
- You don't have the latest requirements? I made sure to communicate the latest changes to all developers.
- Remember that we are using the Agile methodology. Time is critical. Do not waste it by creating any test cases or bug reports. Just test and discuss the bugs directly with the concerned developer.
- Note that the build you are testing can change any time. Even if you notice that the build has changed, just continue your testing as if nothing has happened.
- There is no need to test the <this> module. I have already had a [senior] developer test it and he said it is working fine.
- You are new to the project. We will have a senior tester repeat your tests and compare both your results.
- I want to be aware of each bug as it is found. In addition to logging the bug report, inform me(PM) as soon as you find a bug.
- You have found a bug? Are you sure that you have tested the latest build [talking about the recently developed build not yet passed on for testing]?
- What bug did you say you have found? Please confirm each bug with the developer before raising/ logging it.
- Why doesn't your bug report have a test case ID? Note that no bug will be accepted without an existing test case ID.
- Your bug is a duplicate of bug ID <number>. Note that NO [implying not even the first] duplicate bugs will be entertained by the developers.
- Finally, It is 8 p.m. The developers have worked very hard to create this release. Now, they have all gone home. You can do all your testing. Just remember that the release has to be delivered to the client first thing tomorrow morning.
- Why did you submit only the defect summary report? Where is the incident summary report?
Date: 04 May 2014