You know testing is going well...



  • You know testing is going well when tickets are verified before they are ever released. A copy of an email I recently sent:


    It's not possible that it was okay as that feature has not been released to test.
    

    From: Jefferson, Thomas
    Sent: Tuesday, February 10, 2009 12:18 PM
    To: Washington, George
    Subject: CR 18262 VERIFIED COMPLETE

    I tested this yesterday and it was ok.

    Thomas Jefferson, PMP
    Program Manager
    ABC inc
    Office: 414-555-1212
    Email: tjefferson@abcinc.com



  • @GazingIntoTheAbyss said:

    You know testing is going well when tickets are verified before they are ever released. A copy of an email I recently sent:


    It's not possible that it was okay as that feature has not been released to test.
    

    From: Jefferson, Thomas
    Sent: Tuesday, February 10, 2009 12:18 PM
    To: Washington, George
    Subject: CR 18262 VERIFIED COMPLETE

    I tested this yesterday and it was ok.

    BTDTGTT

    Once upon a time, I was the administrator for an in-house programming group's dev and qa environment.  I found a bug in their product.  I checked a test script into their version control system which reproduced the bug.  I then promptly filed a bug, and included a URL to the test script.

    About a week later, I got an email from the head developer, indicating the problem was fixed, as he just verified it was no longer a problem on the production system.

    I had not seen any change control messages about it.  I checked, he had not been on the production systems to deploy a change.  He had not been on the QA systems to deploy a change.  My test script had not been accessed since I checked it in.  None of the files in that subdirectory of his development environment's home directory had been accessed since I submitted the bug.  I checked out my test script (as I had not retained a copy in my home directory) and ran it against all three environments.  It failed on every one of them.

    I emailed him and Cced his supervisor, with the results of my testing and a copy of the test script, and asked him what he tested.

    He insisted he tested the same thing.

    This went back and forth a couple of times, and then I went over to his work area, to witness his test.  I made sure to get his supervisor for the show.

    He then proceeded to demonstrate that some functionality which was logically near but completely different from the buggy code worked flawlessly.

    I then walked away while his supervisor chewed him out for a bit.

    The issue turned out to not only be something he didn't understand, but actually something he apparently *couldn't* understand.  Even after someone demonstrated the issue to him.

    The bright side of it was that his supervisor was sufficiently clued that he did not remain the head developer for very long after that.  (Note that this wasn't the only issue.  His supervisor had put him on probation a couple of weeks before this incident.)



  • @tgape said:

    BTDTGTT
    Be The Developer That Garotte-wires The Tester?



  • @TwelveBaud said:

    @tgape said:
    BTDTGTT
    Be The Developer That Garotte-wires The Tester?

    Actually, that's a recursive acronym, standing for BTDTGTT isn't defined yet.





  • @derula said:

    @TwelveBaud said:
    @tgape said:
    BTDTGTT
    Be The Developer That Garotte-wires The Tester?

    Actually, that's a recursive acronym, standing for BTDTGTT isn't defined yet.

    How can it not be defined yet?  That's older than Old.  It was in common usage1 back when I first got on to the net - back before September2.

    1 Well, at least on a.s.r.

    2 Not last September, you ninny. *This* September we're still in.

    3 Footnotes were sort of an a.s.r. thing4.

    4 This isn't a lot of footnotes.  26 footnotes is a lot.  I never wrote any messages with a lot of footnotes.



  • where is footnote 3 referenced from?



  • @tgape said:

    *This* September we're still in.
    The sad part is that even though this is the first time I've heard of this, I completely understand it. There is no end in sight...



  • @DOA said:

    @tgape said:

    *This* September we're still in.
    The sad part is that even though this is the first time I've heard of this, I completely understand it. There is no end in sight...

    ME TOO!


  • @lanzz said:

    where is footnote 3 referenced from?
    Here.3


Log in to reply