Mind maps at STeP-IN Summit 2013. See you there.

One of the highlights of participating in Weekend Testing sessions is that you get to see others test, their test reports and thought process to an extent. When I participated in sessions conducted by Europe chapter of Weekend Testing, I noticed that few test reports were in the form of mind maps. Darren McMillan was excellent in reporting with the help of mind maps. When I asked him to help me with mind maps, he wrote this beautiful blog post which soon became the go-to post for mind maps. I myself would have referenced this over thirty times.

Over the last two years, I have practiced and used mind maps to collect all sorts of information.
Starting from test ideas to book draft to bug investigation, I have gained a lot by using mind maps. I have also conducted workshops at Hyderabad and Chennai on usage of mind maps in testing. It was well-received. So when STeP-IN agreed to my topic of mind maps, I was happy. I see this as an opportunity to help more testers realize the power of mind maps and save a lot of valuable testing time.

Do attend STeP-IN Summit 2013?

 

I am presenting on mind maps on June 18th and there are other valuable presentations and workshops too. Hope to see you there. An overview of my presentation can be found here.

Any questions, feel free to ping me.

Leia Mais…

Less time? Map the bugs.

Last night when I came back from office, I saw the email from www.99tests.com about a one day contest on Android mobile. I joined the contest and observed that the max limit of bugs per tester was 15 instead of 25 (for 3 day contests). For every duplicate bug one logs, there is a -1 point. So, one has to be careful before logging bugs. And when I joined the contest, there were already 50+ bugs logged. I like to spend the initial few minutes of any contest, trying to understand the purpose of the application, the focus areas by the other testers and the validation strategy by the contest owner.

I wanted to go through every bug logged and at the same time understand the application quickly. I started with few bugs and then an idea struck me. Why not map the bugs and categorize the features too as parent nodes?

This is what I got after 25 mins:

Mindmap of Bugs

This way, I went through every bug and still made a high level model of the entire application.

I liked it and after three hours of testing, I got the 7th position with 100% valid bugs. I logged 6 bugs.

Maybe, there is a better approach but I liked the approach of mapping out the bugs before testing. What do you think? Do you have a better way?

Leia Mais…

Flipkart Testing @ Hyderabad - Session Results

At the end of Session 1 & Session 2, we preapred two mindmaps about the product & the testing plan.
The corkboard image is also put up below.
Thanks to Anurag & Raghavendra.

Consider this for testing

What to test

Testing Notes

Leia Mais…