Via @jokegijsbrechts
Kategorie: Fun
How to fix the build – not!
Via @dvdstelt
Return to Sender – Software Test Version
Return to Sender – Software Test Version
I had to submit a new defect,
looked like a major bug.
But as development received it,
they reassigned right back.
They wrote upon it:
Return to sender, runs with our mock,
must be environment, ain’t no bug.
They send their package, once it compiled,
and all no matter how many bug reports I filed.
Then i attached a bunch of log files,
and screen shots, two or three.
But just a minute at the coders‘
and it came back to me.
They wrote upon it:
Return to sender, can’t reproduce,
No such requirement, your test is screwed.
Next package we get for deployment,
I’m going to inspect,
And with a bit of schadenfreude,
I’m going to send it back.
I’ll write upon it:
Return to sender, does not install
when strictly clinging, to your manual.
Da-dab-dee-da-da
Return to sender
Return to sender
Return to sender
The idea of writing a blog post like this was in my mind for quite a while already, but as too often, I was just procrastinating. Today I have been busy retesting (and closing) a lot of items from our defect tracking system (DTS) and started writing down the following items, as I stumbled upon them (and as they came to my mind as I remembered them from previous projects).
Of course I´m exaggerating a bit on some of the listed items, but all of them are real examples of what I´ve experienced in the past. 😉
So here it is, my (not-yet-complete) list of things to do, to make your bug report most useless for your team mates (none ordered):
Have a look at what @AgileBorat is writing on Twitter: https://twitter.com/#!/AgileBorat
My favorites so far:
My friend Azamat is very good developer, he is always have all unit test green. If unit test is fail, it is remove. Is best practice.
Azamat and Vlad has write new Defilation of Done. They say better something Done than nothing Done. CEO is hope for _anything_ Done.
Via @YvesHanoulle