We love you that argue for us, seriously. I've had (very careful) tantrums about rushing through emergency fixes that only do a partial fix with workaround, or we weren't given time to explore more scenarios, or the fix explanation wasn't comprehensive (or comprehensible) enough.
Someone with my responsibility sat in a meeting and argued for just another day of testing, and described the process for dealing with this kind of thing, but it still comes down to someone making a call about how much is needed and how much heat the company can take.
Yes. I've honestly wished at least the test supervisors could go to some of the meetings to explain why release is a bad idea until we can check a few more things. I've had to use a single test run for three or four separate variables and I absolutely hate having to do that. It will always come up two or three builds later when a user finds out it affected something entirely unexpected that might have been caught if we'd a.) had more information or b.) had more time.
no subject
Someone with my responsibility sat in a meeting and argued for just another day of testing, and described the process for dealing with this kind of thing, but it still comes down to someone making a call about how much is needed and how much heat the company can take.
Yes. I've honestly wished at least the test supervisors could go to some of the meetings to explain why release is a bad idea until we can check a few more things. I've had to use a single test run for three or four separate variables and I absolutely hate having to do that. It will always come up two or three builds later when a user finds out it affected something entirely unexpected that might have been caught if we'd a.) had more information or b.) had more time.