The context driven school of testing is a good representation of my personal normal state of mind when it comes to my profession. I really like to hang out with like-minded people that are outspoken about belonging to this community of testers. I also recognize many of the people within this community to be interested in and are practicing good Agile testing. When I started to write this post I also realized I gave it a shot 3 years ago, when I still hadn’t wrapped my head around context-driven. But although my knowledge and experience has changed a lot during that time I still think the post is valid in some sense.
Before continuing, read my previous posts in this series:
Agile Testing – Traditional testing perspective
Agile Testing – Agile perspective
Agile Testing – Programmer perspective
Agile Testing – Project management perspective
Context driven testers
If you haven’t read my post about bridging communities, please start there.
In many of the places and discussions I have been this year, people have been trying to define what Agile testing really is. And it is quite interesting that even 3 (almost 4) years after THE book on Agile testing came out, people are still trying to define what it is. What has interested me more is the fact that I’ve seen the area evolve in different communities, and that is what I want to share. I will talk about some extremes in communities, so forgive me if I step on toes. I am emphasizing other peoples opinions to make my point. Read more…
I love communities, hanging around smart people that have their main interests of which they are really passionate and also often very good at. Personally I prefer blending into different communities, getting some of many different things rather than to delve very deep into something in particular. I think its my curiosity and kind of systems thinking mind that wants to stay up to date with a lot of things. I also like to keep my spectrum broad with regards to the knowledge I take in, and then I can filter the good parts myself. Read more…
I was at Agile testing days in Potsdam as a speaker. The conference is quite a nice experience as a speaker. I don’t know the numbers, but I think it was about 500-600 people there and around 80 speakers I think. Small enough to be able to speak to most of the people that you want to speak to, as well as big enough to give the touch of diversity of people.
Most of the sessions I attended I tried to note down important stuff into mind maps. Although with highly varied results because of the contexts of my awareness and concentration during the session. (Here is an example through my live blogging from Pete Walens session). Its really is hard to maintain the discipline of good documentation as you go throughout a very long time. This is actually one of my pinpoints in my presentation; having people that are not used to test documentation to actually record the exploration done throughout sessions. And the fact that I am having troubles with it myself during a conference hints that it might not be so easy. Here are some highlights: Read more…
I stumbled upon another one of those mind mapping applications called Scapple.app. As I am always looking for ways to improve and change ways of working I had to try it out. I regularly use Xmind at the moment for these demands.
As it is in Beta test, I also decided to give it a real test perspective. A short session with recorded notes and a bug list was what came out of it. I hope they can make use of my results.
This is my summary:
Scapple seems to be a valid competitor to any mindmapping tools out there, and it has its niche. However it has a long way to go before being able to get me as a user for day-today work. My preferences go for Xmind and Prezi for these types of tasks. Testing was mainly done through exploration of the steps shown in the quickstart guide. It is not a very deep analysis, but even so the light coverage found some very basic and severe issues.
Starting off my stay in San Jose with Test Coach Camp, my head was already full of ideas before the conference. But that did not actually matter when I got up to speed of conferring with my fellow peers at the conference.
This was my second CAST. Last year I got to meet so many new people that I have been in contact with since online and at other conferences. The difference for this year was obvious, I must already have known or at least met and talked to one third of this years crowd before. It was a comforting thought when I was about to go to San Jose. Anyway, it turned out big parts of the other two thirds were highly interesting people as well, so if I would have to regret something from this years conference, it would be that I did not talk enough to the people I already know. That is a pity when you don’t meet very often. But I made so many new friends instead.
Another difference from last year was that this year I was a speaker. Read more…
First of all, I had a blast at text coach camp!
I am very happy I made that decision last Friday. Before coming to San Jose I had not applied to go to the Test Coach Camp. I was going to explore the town and its surroundings to adapt to the time difference before CAST. I had dinner with the TCC participants and got to know they had some last minute drop-offs. So I was encouraged to go through the application process, which I did later that night by creating this mind map for application. Read more…