Quality is delighting customers
After the bug closed do we change the status as "Pass" in the testcase? My PM is telling that in testcase we should not change the status as "Pass" in case of closed bug. Please guide me in this. Thanks in advance.
Hi..I think.you should make a column based on every Milestone and mark the status as Pass for that release..
See.. test cases are executed in cycles.
Suppose you got bug followed by reporting and resolving from developers, it means that test case had a bug in cycle one. So make it clearly fail in column of cycle one.
suppose when next cycle on modified build will be executed then, absolutely you can tag PASS in cycle 2 column for same test case.
again, if you are using term BUG, then ofcourse it's approved from developer team to ensure defect is still in system.
So if your are using Defect then it's ok to aggree with Samrat's notes, and If BUG then it must be resolved ot make them pass in next cycle.
What do you mean to say by term Bug or Defect ...? are they different ..? if yes make me understand the difference ...............
Defect is just synonyms of problems found by Tester (at any stage*) and yet not verified and accepted by developer(at any stage*)
where as Bug is fully reviewed and accepted as it is defect, by developers(at any stage*).
*I write any stage, it means developer could be any one either Business Analyst or designer or coder.
And also, it is not compulsory as if product was released then all found defects had been resolved. As delivery or release could be depended whether product is stage as per customer usage level, or all major issues have been resolved or defect was found for extreme level exceptional cases.
I Completely disagree ... ! What I could get from your reply : A defect is a defect until it is approved by developers .. after approval it becomes Bug.. at least your reply is indicating that .....
But We find around 50% of the defects/bugs in system and our development team is still to write first line of code...!