So I thought I would share with you something that I found incredibly amusing from a lead developer who is assigned to our next version of software/hardware product. He wrote this presentation for a meeting later that was called by his boss because of email chains going back and forth between SQA and him. I am the lead SQA Engineer on this project.
Here's the text from his "and in conclusion" slide:
QA Unit Testing Requirements
Unit Test Interfaces
Unit Test Tools
Utilize Database Technology
Predefined Test Databases
Message Transaction Log QA only requires a sub-set of the SRS
I just can't help but [img]/images/graemlins/grin.gif[/img] [img]/images/graemlins/grin.gif[/img] [img]/images/graemlins/grin.gif[/img] at this last line. This meeting will be fun.
Geez I would have fun with that person. [img]/images/graemlins/cool.gif[/img]
What a Tool!
Reminds me of a someone I knew years ago. He moved from Tech. Support to Development and said he would write 'perfect code'. He also made some other comments that caused myself and a fellow test staffer to decide to 'get' him when we could.
We waited about 3-4 weeks while he wrote his 'perfect code', pulled it down and tested it to death. We walked into his cube with a big stack of defect reports and let them "plop" onto his desk and said "Here's your perfect code Ed!" and walked out. He became a bit more humble after that one.