TestToTester

I went online at around 1130PM Saturday hunting for some challenge to exercise my sleepless mind. Pinged Ajay and Manoj on GTalk and they had plans of testing a product. After around 45 min spent on researching what to test we finally decided upon www.tinyurl.com The mission was simple hunt for bugs, and so did we. The session was fantastic; bugs started flowing from the first minute, and all three of us had loads of fun. The test techniques varied individually and the discussions we had during the test session been great. Once we were thru with the session, Manoj and me left and Ajay did almost most of the post production. So, it would be nice to read the full report from his blog @ http://enjoytesting.blogspot.com/2009/08/trio-testing-at-distance-part-1.html So, next time if you are not feeling sleepy or feel like practicing your test skills with other testers or feel like learning some thing new or feel like sharing your test ideas, or just curious to know what this is all about...

The rainy season is here in Bangalore and so are the experience reports from BWST-1. WOW! My small attempt to faction all reports Pradeep Soundararajan's report Santhosh S Tuppad’s report Shikhar K Singh’s report Rahul Mirakhur’s report Enjoy reading these fantastic reports, and hope to see more of you in the next BWST.

Yesterday I felt very happy after reading http://www.developsense.com/2009/05/experience-report-from-india.html from Michael Bolton, so sharing with you all. Thanks Michael, appreciation on your blog means a lot to me and is very inspiring. The most wonderful thing about context driven testing community I have observed is they are just an email away from you. They love sharing their testing experiences, they love sharing their secrets, and most importantly they love to see a better test community. “My blog List” lists some of those testers who I respect a lot and have learnt from. The list is nowhere complete, and has been growing the day I started it. Thank you all.

Today when I went thru the latest post from Shrini Kulkarni , Shrini’s question is this a bug? Made me recollect James and Michael's definition of a bug, I had always liked this definition because it’s simple, catchy, crisp and makes a lot of sense “ A bug is something that bugs somebody who matters ”. Well, I have a game in my cell phone called “Krish Cricket PRO Challenge” in the game cricket greats like even Lara, Gilchrist bat right handed – is this is a bug?. Well, I am confused because though they are right handed the game is a lot of fun to play and I do not mind them batting right handed or in other words it does not bug me. So is this a bug? The game came bundled with other applications when I bought the cell phone. Initially I felt very odd to see Lara play right handed, and I cursed the team who built this game. Could the code be simple if all batsmen in the game are right handed? May be the team who built the game did not invest enough in the software since it would b...

Couple of weeks back when I met Pradeep , Manoj and Mohan at Edista Testing Institute , Pradeep handed me a project/assignment report to glance thru and asked for my observations of the report. I glanced thru the mission statement, test scenarios, bugs logged, testers own analysis/review of the assignment, the answers to the difficult questions like • What did I do well? • What did I not do well? • What wasn’t I able to do? • Why wasn’t I able to do whatever I couldn’t do? • How much time did I pit in on daily basis? • What did I learn about what I don’t know during these days? • What tools did I use in this project & what tools did I discover? I felt very happy; I looked for the author name and asked Pradeep for more information about the author and the reply by Pradeep was a “fresher” who has just completed the Finishing school from Edista. WOW! I doubt if I might have written such a good report as a fresher for my first testing assignment. Check out the report for yourselves @...

In my last assignment a mix of exploratory, session based and scripted testing helped won an award, appreciation by managers & stake holders at our organization. The quotes from our award certificate “ QA team has come up with some intelligent testing techniques to validate the product. The customer test team was not able to find even a single critical bug after delivery ” Though the award was a small one in terms of the award categories our organization have, it meant a lot to me and the team, because this was the first time the team used exploratory approach. The assignment was not pure exploratory or session based, in fact it was supposed to be scripted, but a mix of all three exploratory, session based and scripted testing helped us learn, enjoy, and meet our mission. The assignment started off with developing test cases. We wrote test cases based on the initial requirement document provided. We did come up with a large number of test cases, of which most were re-written, some ...

In a recent assignment I was asked to test an application which downloads and displays pictures off the web with minimal features support like slide show, rotate, minimize, maximize etc. (I cannot provide any more information on the product because of NDA) We knew that our internet connectivity thru LAN is slow, but had to observe and document the result on the same network. After stating the assumptions about connectivity, speed, throughput available I started testing, in 2-3 min I decided not to use our bug tracker but instead write a story in a word document. What did my story contain – every step (test) performed on the application sequentially. An extract from it would look like 1) Reboot the 2) Click on for the first time. It takes approximately 13 seconds to display all the images in the 3) Click on and login to . The takes approximately 6-7 minutes to load 15 images. 4) When initially started it displayed loading x/37 images but after loading 15 images the message disappears...