Replies are closed for this discussion.
Here is one I just heard:
"As a tester role, you are only responsible for the testing based on requirement spec which has been created by developer. You are not allow to do any type of analysis of impact on system."
I told the same statement to respective person yesterday... :)
I'm a test leader.
I've seen a guy from my team having some difficulties to get documentation from a developer to explain a database migration process.
But this QA guy need to test this migration.
So he has create a ticket in the Defect Management Tool to ask for more information.
The answear of the developper (written in the ticket) was : if I have to write the doc, then it is like if I'm doing the test myself. So I don't need the help of the QA for this project !
As with my reply to ElizaF, we had a developer who would deliberately add defects to the code in order to point them out when we 'missed' them.
It was used as a tool to try & belittle the test team - luckily for us, the Dev manager was supportive of the test team. The developer didn't last long...
Well...I have heard the folllowing couple of times from the developer,
" Testers systems are not upto date and they are not maintained properly by them and it always have a problem", but the truth is
The issue is nothing to do with the tester's systems, its either the config issue or developer might have forget to check in some of his development stuff to the staging environment.