A while ago I started looking for agile testing games, unfortunately I didn´t find much, but since a couple of people asked me for that, I´m gonna now publish what I have.
Hopefully, this (small) list grows a bit over time, so please let me know, if you know about other (Agile) Testing Games!
Kategorien
How to fix the build – not!
Via @dvdstelt
In most retrospectives, we´re using the plain „What went good? What went wrong?“ – technique via a roundtable, noting down the outcome of this, then start discussing possible solutions for the „wrong“ things, coming up with action items to solve them, decide to take the actions, and ask participants for their ROTI (Return of Time Invested).
Kategorien
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
As already last year, Lind Rising’s talk was really amazing and just awesome! I already know that writing a blog post about it can only be a bad copy, but I will give it a try.
This was the opening keynote of the conference, done by Johanna Rothman (@johannarothman). Johanna was so nice to publish her slides on slideshare, find them embedded at te end of this article.
Kategorien
Group testing
The idea -as well as a draft- for this blog posting are around for quite a while now, what finally forced me to finish and publish it, was a talk with Lasse Koskela (@lassekoskela) at the Agile Testing Days 2011, where I told him about the approach of „group testing“ sessions within our team, and he insisted that I had to write about it. So thanks Lasse, for forcing me to finish and finally posting this article.
This talk of David Evans (@DavidEvans66) was one of my favorites at the Agile Testing Days 2011.
I will only list some things not to find on the slides in this article, and then provide a link to the slides at the end of the article, as they are really self-explaining (imho).
This talk was held by Gojko Adzic (@gojkoadzic) as a replacement for Markus Gärtner (@mgaertne), who unfortunately has been sick.
I found it was a quite challenging topic, therefor I didn’t take much notes, and my article might be quite fraqmentary. If you feel so, please scroll down to the very end, there I will link to some stuff on Gojko’s homepage, which gives more & additional insight on the topic.
In this talk, Rob Lambert (@Rob_Lambert) presented different ways to increase your awareness and tries to give an answer to the headlining question.