Jul. 11th, 2006

jameydee: (Default)
They're MAD! MAD, I tell you! Q/A has gone abso-f*cking-lutely insane.

Test against the requirements, not against your expectations. I see a error report filed because the tester "thought they should see..." No, no, no, that's not what you're there for! That's not what the requirements say!

What makes me insane is that the testing and function departments actually got together and rewrote the requirements as we were testing--requirements are a moving target at best, so it's bad enough to have to code against ever-changing requirements, but now to get swipes due to tester expectations? No, ain't gonna change it. Won't do it. Can't make me. It ain't in the requirements. Go tell someone to rewrite the requirements to meet your expectations and then I'll change the code.

I'm actually upset because the requirement writer added a little phrase that breaks one of my carefully crafted validations and will take a major rewrite of an entire segment of the web app. What pisses me off is that I *KNOW* the customer will hate the change. But, no, it's in the requirements now. I must make the change. Until the customer sees the change in action and wants it gone again.

April 2017

9 101112131415
16 171819202122

Most Popular Tags

Page Summary

Style Credit

Expand Cut Tags

No cut tags
Page generated Oct. 22nd, 2017 09:46 am
Powered by Dreamwidth Studios