Why I hate QA
-
I recently moved some code into our live production system that I know the testers didn't really test. One of them even admitted it to me. But they all signed off on it. I guess my point is...there is another extreme. Where is the happy medium?
-
:laugh: :laugh: :laugh: :laugh: :laugh: Hey, did you hear about the short fortune teller that escaped from prison? It's a small medium at large!
All of the books in the world contain no more information than is broadcast as video in a single large American city in a single year. Not all bits have equal value. Carl Sagan
-
-
The form has a user configurable button Requirements: Click on Button1 (real name changed to protect the innocent) QA: Test fails because button text does not say Button1 Me: You understand the text can be changed at any time by the user? You also understand you are testing functionality, not text, and the text of the button does not change the functionality of it? QA: Test fails because button text does not say Button1 Now the entire application, almost six months of requirements and development are on hold because of this one, single "defect". :mad:
Failure is not an option; it's the default selection.
The QA document should be changed to read: "Click on button identifier idx12345 which can be identified visually by looking up the user configurable option defined in the user configuration buttons use case" Of course, I hate QA I am just having fun at your expense.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
-
The QA document should be changed to read: "Click on button identifier idx12345 which can be identified visually by looking up the user configurable option defined in the user configuration buttons use case" Of course, I hate QA I am just having fun at your expense.
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
Ennis Ray Lynch, Jr. wrote:
at your expense.
Expenses are billable. Where do I send the invoice?
Failure is not an option; it's the default selection.
-
Ennis Ray Lynch, Jr. wrote:
at your expense.
Expenses are billable. Where do I send the invoice?
Failure is not an option; it's the default selection.
At your expense not mine : )
Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. I also do Android Programming as I find it a refreshing break from the MS. "And they, since they Were not the one dead, turned to their affairs" -- Robert Frost
-
The form has a user configurable button Requirements: Click on Button1 (real name changed to protect the innocent) QA: Test fails because button text does not say Button1 Me: You understand the text can be changed at any time by the user? You also understand you are testing functionality, not text, and the text of the button does not change the functionality of it? QA: Test fails because button text does not say Button1 Now the entire application, almost six months of requirements and development are on hold because of this one, single "defect". :mad:
Failure is not an option; it's the default selection.
I once wrote a check issuing utility for a mortgage company that was rejected by QA, because the amount line would wrap on some checks that were over one billion dollars...that's quite a mortgage!
-
The form has a user configurable button Requirements: Click on Button1 (real name changed to protect the innocent) QA: Test fails because button text does not say Button1 Me: You understand the text can be changed at any time by the user? You also understand you are testing functionality, not text, and the text of the button does not change the functionality of it? QA: Test fails because button text does not say Button1 Now the entire application, almost six months of requirements and development are on hold because of this one, single "defect". :mad:
Failure is not an option; it's the default selection.
Mark Nischalke wrote:
development are on hold because of this one, single "defect".
Get a copy of the "defect" resume and send it to a headhunter.
Will Rogers never met me.
-
The form has a user configurable button Requirements: Click on Button1 (real name changed to protect the innocent) QA: Test fails because button text does not say Button1 Me: You understand the text can be changed at any time by the user? You also understand you are testing functionality, not text, and the text of the button does not change the functionality of it? QA: Test fails because button text does not say Button1 Now the entire application, almost six months of requirements and development are on hold because of this one, single "defect". :mad:
Failure is not an option; it's the default selection.
Could be worse... we had a requirement here written like this...(names removed to protect the guilty) The Thumbnail shall provide the user the capability to [shall] page and/or [shall] Thumbnail by Thumbnail scroll, [shall] selected mechanism(s) as configured for the Product, [shall] left to right, if Thumbnails are available to the left and/or [shall] right to left, if Thumbnails are available to the right. All of the [shall] markings were with square brackets and also with a dark blue background with a black font. It looked like the entire document was redacted by the US government. (The System Engineer that wrote it also wrote and self published hi-tech romance novels) Of course we also had a QA that wrote up a bug saying that she could not use the touch screen on the primary monitor to drag and drop an icon to the secondary monitor. She expected that she could start the dragging, then lift her finger and move over to the other monitor and it would still be there. We told her that we could not change the laws of physics (in our best Scotty impression). We could have done some things around using a gesture or something to get the icon over to the other screen but decided to just keep the bug open for a while to show management the quality of our QA department.
Steve Maier
-
Could be worse... we had a requirement here written like this...(names removed to protect the guilty) The Thumbnail shall provide the user the capability to [shall] page and/or [shall] Thumbnail by Thumbnail scroll, [shall] selected mechanism(s) as configured for the Product, [shall] left to right, if Thumbnails are available to the left and/or [shall] right to left, if Thumbnails are available to the right. All of the [shall] markings were with square brackets and also with a dark blue background with a black font. It looked like the entire document was redacted by the US government. (The System Engineer that wrote it also wrote and self published hi-tech romance novels) Of course we also had a QA that wrote up a bug saying that she could not use the touch screen on the primary monitor to drag and drop an icon to the secondary monitor. She expected that she could start the dragging, then lift her finger and move over to the other monitor and it would still be there. We told her that we could not change the laws of physics (in our best Scotty impression). We could have done some things around using a gesture or something to get the icon over to the other screen but decided to just keep the bug open for a while to show management the quality of our QA department.
Steve Maier
I worked on an app at my last company that had a dialog with Ok and Cancel buttons. A "Senior QA Analist" rejected the app and wrote in TFS saying "When I click Cancel it crashes". So I spent the next 4 hours trying to reproduce the "crash". Finally I went over to her desk and asked her to show it to me. She opened the dialog, clicked Cancel, the dialog dissappeared - and she said "See, it crashed!". I said "what crash?? Where is the 'crash'". She said, "When I click Cancel the dialog closes. Cancel should clear out the fields on the dialog. Instead it crashed". We then proceeded to have a very heated 20 minute debate over what happens in a Windows app when Cancel is clicked, which ended in her yelling "Ya know I didn't just fall off the turnip truck!!!". She insisted that Cancel should "clear out the fields". The next day I brought this[^] in and threw it on her desk.
Everything makes sense in someone's mind
