QA should design different data pattern, try to exploit your program. If the QA can't reproduce the error, fire them.
What I am trying to do is:
1, Read the program to find out the problem. That's very hard, you have little chance to find that out by reading the source code.
2, Give different data set, find out in what condition you see the error message again. Usually this is the job of QA.
Once I read a novel, saying that in the design of DEC, the development team submit the product to QA team, and if the QA team find bugs, they send it back without any report. The development team must find out bugs themselves and improve the program before resubmitting.
What I am trying to do is:
1, Read the program to find out the problem. That's very hard, you have little chance to find that out by reading the source code.
2, Give different data set, find out in what condition you see the error message again. Usually this is the job of QA.
Once I read a novel, saying that in the design of DEC, the development team submit the product to QA team, and if the QA team find bugs, they send it back without any report. The development team must find out bugs themselves and improve the program before resubmitting.