Check Your Subroutines - We are delivering our latest release to internal test today. Had a code review yesterday. Many issues were found. We are fixing the highest priority probl...
Marked as Passed
Recently the customers reported a very strange behavior in some of our new software. A tester got assigned the task to replicate the problem. This tester could not even get the applicaiton launched. She reached out to a developer for help. The developer produced a recent build for the tester to use. Then tester then was able to launch the app.
This tester proceeded to then try the steps documented by the customer trouble ticket. There was no trouble for the tester when she tried following the steps. She made the conclusion that they developer must have fixed the customer problem. The tester reported that the problem was fixed and verified. Management took this diagnosis as gospel. Promises were made.
Disaster ensued from this mix up. The customer thought they were getting a fix. They received no such correction. Imagine development's surprise when this thing came back to us. Development was sure they never resolved the problem that the customer raised. This was tracked down and the conclusion was that the tester was never able to recreate the problem voiced by the customer. This is much different than testing and passing a fix.