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.
Veröffentlicht unter Learning
Verschlagwortet mit effect mapping, how, paper, video, what, who, why
Andreas Schliep (@andreasschliep) talked about how to test your organization, he started by telling about his experience about playing the ballpoint exercise, which is a kind of scrum-simulation, where the team has to do an exercise, then do a retrospective, and starts to iterate (and hopefully improve).
Gojko Adzic (@gojkoadzic)talked about the five key challenges he sees for agile testers tomorrow. He has two basic statementes/ assumption which guide him to these challenges: Technology is changing fast and the field of agile testing is quite well defined today.
According to Gojko, these challenges are
- shorter delivery phases
- agile is now mainstream
- faster feedback
- large „enterprise“ projects
- validating business, not software
The initial statement of Anko Tijman (@agiletesternl) in his talks was, that agile testing is about migitating the risk, therefor a test strategy should focus on risks in
- business acceptance
Veröffentlicht unter Learning, Testing
Verschlagwortet mit agile testing, architecture, business acceptance, code, customer's acceptance, Exploratory Testing, integration test, interfaces, migitating risk, non functional test, requirements, risk, test case, Test Strategy, unit test, user story
In this talk Lisa Crispin (@lisacrispin) and Janet Gregory (@janetgregoryca) presented some major issues they learned about since they published their book Agile Testing some years ago.
These topics are:
- Feature Acceptance
- Test Automation
- Large Organisations with Multiple Teams
- Distributed Teams
- Continous Learning
From monday to wednesday I had the chance to visit the Agile Testing Days in Potsdam. It was an awesome event: I met a lot of interesting people (delegates, speakers & tutors), had many interesting conversations, met former colleagues, listened to amazing talks, and learned a lot. Far too much to wrap everything up in one blog posting. Therefor I will use this article to list up all the articles about the Agile Testing Days 2011 (#agileTD), the list will be updated as a add articles, so drop in from while to while, or subscribe to the RSS-feed:
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): Weiterlesen
Veröffentlicht unter Fun, Testing
Verschlagwortet mit bug, defect, report, tracker, tracking, useless