AboutAt the blunt end of the leading edge. Generalist just trying to keep the lights on and flashing
SkillsC# MS SQL web and desktop with the odd Windows Service too
Joined devRant on 1/12/2018
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
So I'm testing a co-workers code and doing regression scenarios when suddenly it "loses" data in two fields after I save the data and go out/come back into the form. That's weird says I, lets have a look....
And I find the following conditional::
if (field empty) then failValidation("hey stoopid user")
else blank field value
Happy Friyay everyone....
How many times do I have to tell my co-workers that testing isn’t just about proving your shit works in nice ways. It’s also about proving it works with sparse or inadequate data. Also, regression testing is a thing so do it!2
Me: hey guys there seems to be an integration problem?
Vendor: hacky workaround
Me: no that’s a hacky workaround, please check the integration
Vendor (sometime later): yeah so we made an engineering change like, a while back, which fundamentally alters stuff.
Me: so shit is fucked because you don’t think customers should be informed ahead of release? Dude do you not want our money?
Email all staff. Important! We are having problems with the firewall.
Sure as shit we still get the help desk emails that start "is there a problems with email"
Hmm most incompetent co-worker? That would be the guy with a degree in IT who couldn't create a stored procedure without needing a team leader to tell him which keys to press. We were not his first employer and allegedly he had experience...
Perhaps this would be fine, learning curve and all that, for the first few weeks but when a simple select statement was still causing problems alarm bells rang loud. He got attached to the test team for a week before being sat down with the boss....