It's taken some time to collect myself into writing down my notes from the latest EAST meeting. This time we met at Verisure in Linköping. After some nice greek food we started out to draw the outlines of an ideal testing project. Focusing really on the word "ideal". We had a lot of fun. Things from "clear requirements"* to "resulting in peace in the universe" were added on the whiteboard. At this moment of writing I don't have the time to elaborate on the topic and the result, but I will post the photos from the whiteboard and promise to come back to explain it a bit more later.
We started out with defining the four different phases: Project idea, Planning/strategy, Test execution, Finish. Then we just added whatever came to mind that we wanted to have in place for an ideal test project. Note that perfect and bugfree code is not included in an ideal testing project.
* = actually, looking at the pictures after writing the above text I notice that "requirements" weren't mentioned at all... that's funny! In my memory they were. Apparently we don't really care about requirements in an ideal testing project... that idea probably calls for a separate blog post to figure out!
Here goes:
We started out with defining the four different phases: Project idea, Planning/strategy, Test execution, Finish. Then we just added whatever came to mind that we wanted to have in place for an ideal test project. Note that perfect and bugfree code is not included in an ideal testing project.
* = actually, looking at the pictures after writing the above text I notice that "requirements" weren't mentioned at all... that's funny! In my memory they were. Apparently we don't really care about requirements in an ideal testing project... that idea probably calls for a separate blog post to figure out!
Here goes: