developers that rely too much on QA

[stringbeans]

so i got bitched out by one of our clients today

he says i dont add enough details into my bug reports. THEY DONT NEED ANY MORE DETAILS BECAUSE YOU ALREADY KNOW THEM. then hes like "you never mentioned whether or not you had enough disk space to proceed in the installation." .... ok well the bug that i logged occurs on the screen AFTER where the installation checks for enough disk space, so OBVIOUSLY i had enough.

fucking moron.

and hes like "i especially dont get enough details from you and its very frustrating. we ship tomorrow"

well maybe if they were smart about the process they'd do the smoke tests on THEIR end first, and then release it to qa, instead of letting us perform the smoke tests. letting us do them requires us to first download the new build from their ftp (about 60 mins), then distribute it onto our network (30 mins), whereas if they do it on their end first it can be done in probably under 10 minutes. and plus, if there is something wrong they can immediately do a rebuild instead of waiting for a response from us.

ugghhhhhhhhh

[Kraig]

Originally Posted by stringbeans

so i got bitched out by one of our clients today

he says i dont add enough details into my bug reports. THEY DONT NEED ANY MORE DETAILS BECAUSE YOU ALREADY KNOW THEM. then hes like "you never mentioned whether or not you had enough disk space to proceed in the installation." .... ok well the bug that i logged occurs on the screen AFTER where the installation checks for enough disk space, so OBVIOUSLY i had enough.

fucking moron.

and hes like "i especially dont get enough details from you and its very frustrating. we ship tomorrow"

well maybe if they were smart about the process they'd do the smoke tests on THEIR end first, and then release it to qa, instead of letting us perform the smoke tests. letting us do them requires us to first download the new build from their ftp (about 60 mins), then distribute it onto our network (30 mins), whereas if they do it on their end first it can be done in probably under 10 minutes. and plus, if there is something wrong they can immediately do a rebuild instead of waiting for a response from us.

ugghhhhhhhhh

Given that the product is shipping tomorrow, obviously he is under stress. I'm not saying its right to say what he is saying or how he is saying it, but I guess if you put yourself in his shoes you could understand.

[stringbeans]

yeah i'd be stressed too. but their whole process was backwards to begin with, so the fact hes strapped for time shouldnt be blamed on me. there would be days where i'd come in and i'd find a critical bug which'll need to be addressed before continuing, and i wouldnt get a new build that fixed it till the next day. stuff like that eventually adds up...

and its just weird that they dont test it on their machines before releasing it. i mean, how many developers do you know code without even testing their final product.

[dj_soo]

i mean, how many developers do you know code without even testing their final product.

Acutally lots of developers don't do it. I actually had to send one of my testers to the developers on-site of my project (in the states) because they didn't want to, or couldn't... smoke test our product.

And yea, when developers start getting stressed, QA tends to be a big scapegoat - that's why we always make sure all of our problems are and issues are always documented to cover our ass...