Tester that doesn't test
- by George
What should I do about a tester that does not test?
We have a complicated dry run scenario, that takes a lot of time to execute. Mostly this tester will execute it's tests in very slow way...checking emails, internet, etc. He reports just a few bugs, but!
Whenever the official dry-run begins (these are logged with testlink) the tester starts to open new bugs that where not discovered before.
Is he not doing his job correctly? Or am I just overlooking how tests work?
I'm not his supervisor, but he is testing code that I wrote.