It’s tough being a Tester! Testing Circus article

The people at Testing Circus are doing a great job and the magazine has just published their Anniversary edition. I’m really glad and lucky to be part of those passionate people.

You can read my article along with a host of many others in the August edition of testing circus.. Grab your copy now from the following link!

http://testingcircus.com/August2011.aspx

Thanks for your time!!

Your comments will be much appreciated!

Who is breaking the AC switch?

Disclaimer!! The characters in this story are fictional. Resemblance to anyone dead or alive is simply coincidental!!

“Ahh! Not again!!” Yelled the Admin team’s Manager…

and he goes on…

“Are you all little kids? Who is breaking these AC Switches daily? If you are not going to tell, then we are installing security cameras soon. Then we will see who breaks this stuff…”

We look at each other puzzled – someone from ourselves is breaking this switch… But who?

Don’t worry mates – Super Tester is here for your rescue!! He will find it and punish the offender (Grrrr!!) ;)

Puzzled?? I will explain…

Hope you all are aware of the temperature control switches for the centralized air conditioners. In our office, we had our centralized AC’s controls hanging from the wall. So people changed the temperature at will – when they felt it was too cold or too hot ;) As a result the switches began to malfunction and our Admin team had to replace them. Also they instructed the security people to operate these switches and locked them up in a small plastic box. Now, if the employees want to change the temperature, they must call the security guys to open this box and change the temperature :) In addition, they stuck these plastic boxes to the wall with an adhesive tape, to look more aesthetic…

And these small plastic boxes are causing the yelling now a days :) Everyday the Admin team finds 2 of these boxes stripped from the wall and hanging inconveniently. They will fix it again and the next day, the same thing happens… No wonder the manager becomes mad at these…

So, from the day our Admin manager started to yell, I paid close attention to what is happening with these boxes. But it is sort of an intermittent issue and I cannot always keep on looking at these switches.. I somewhat forgot about this problem, even though the yelling and complaining continued :)

We usually have our video conference with onsite colleagues weekly. I forgot about this meeting once and went for lunch. I remembered about the meeting when my friend called me on her way to the meeting room. So I finished my lunch quickly and ran for the meeting room. I remember my shoulder stuck something, but since I was running to catch up, I didn’t really care about what I broke. While returning from the meeting room, I noticed that the switch box is broken!!! Oh my god! I broke it this time, rather unknowingly, with my shoulder ;) Ah! here’s the naughty kid who is breaking the switch box!

But I was sure that this may not happen every time you pass that corridor. You can see the corridor outline in the below picture:

AC Switch near door
My first thought was like, the door when opened hits the box and it falls. But that was not the case, since they have fixed it in such a way that there is no problem in opening and closing the door. But I was also sure that the box fell off because I hit it with my shoulder. So what is the scenario which caused it?

I tried to rewind what happened earlier…

1. I was running
2. I hit the box
3. It fell off

That is not so clear – let’s try again…

1. I was running
2. I had to open the door
3. I hit the box
4. It fell off

That is also not clear – since there is no problem with opening the door as I mentioned above… Let’s try again…

1. I was running
2. I had to open the door
3. But, I didn’t open the door fully – since I had to be quick, I just opened a quarter of it and squeezed myself in
4. I hit the box
5. It fell off

Wow! That’s an “Aha” moment – I remembered the movie Source Code while writing this. Rewinding and fixing your actions to find a mystery…

But this solves only half the problem – what is happening to the other switch box?

Here’s the next corridor outline:

AC Switch near the Printer  You might have guessed it – there is a printer sitting on the way and someone is hitting the box with their shoulder while avoiding the printer. That is somewhat true. But, the corridor is big enough for a person to walk without hitting the switch box even when avoiding the printer. Here’s what happens:

1. You are walking towards the wall
2. Someone is walking towards you from the opposite direction
3. You two meet exactly at the printer
4. The person near to the switch adjusts so that you two don’t collide
5. That person hits the switch with the shoulder
6. Depending on the impact, it falls off..

:)

So, what testers find?

They find this, this and this

And they sometimes find and solve mysteries as described above..

Have they fixed it? Not yet ;)

Mobile Blog!

Hello!

As I step into the smart phone era, here comes the first post from my iPhone 3GS! I’m loving this gadget :)

And for updates, I had been to Chennai for attending Pradeep’s Exploratory testing workshop. It was a great experience listening to him – as he says, he didn’t teach us anything new! But he taught us to do those things in a better way.. Looking forward to more such workshops.

Thanks for your time for reading this short post! Will be back shortly.. Until then, happy testing :)

SBTM, Context Free Questions and Rapid Reporter.

Hello folks, hope you are all doing well and had a cracking start to the New Year. The year started very well for
me, I had a chance to take up a project in more of a consulting way than our usual projects.

The projects I worked on last year are in a support phase now, so I could manage some free time almost every day.
It’s pretty boring sitting idle, right? So I’ve gone through some lessons on Performance Testing, read a lot of
James Bach’s and Michael Bolton’s blog posts. SBTM and Context free questions fascinated me a lot, but there were limitations of actually trying them out in our projects (that old test case running syndrome ;) ). And, out of the
blue I get a chance to test one of our internal projects.

This project has been going on for a while and one of my fellow testers had the test cases prepared for it. He had
tested it as well. So here is my chance to go back to Exploratory testing and do what I like!

The first thing I did was to go through Michael Bolton’s Context free questions to help testing.  I had a thorough look at those questions and comments for the post and identified that all of them need not be asked in my scenario. So I trimmed them down to about 20 questions. This decision was made completely on a personal instinct. Here goes my trimmed list:

  1. Who is the customer/stake holder of the project?
  2. Do you know any problems that would threaten the value of this product?
  3. How much time do I have?
  4. When is the next release?
  5. When do you want the reports/information?
  6. How do you want the reports?
  7. When are you planning to launch this?
  8. Is there another application like this?
  9. What are the issues with the old application?
  10. What are the improvements in this application over the old one?
  11. Could you describe the functionality flow with a diagram?
  12. Has any one tested this?
  13. What all information are available to me?
  14. Is there some specific type of data processed by the application?
  15. What are your thoughts on this?
  16. Have you shown this to end users?
    1. What are their thoughts on this?
    2. What is their overall perception of the application?
    3. Is there any thing specific they wanted to be included?
  17. Is there any thing that I should avoid?
  18. Have you seen any error patterns?
  19. What usually is the common problem you face with these types of systems?
  20. Is there anything else I should have asked/I must be aware of?

I had a meet with the Product’s user champion and got the answers for all these questions. I was granted a week to
provide my exploratory testing report. My fellow tester had done a good job in testing this, and his bug reports and test cases were very handy to start my mission.

Exploratory testing is accountable - and I wanted to practice SBTM for this project. Since I’m sort of consulting for
this project on my free time, I was sure that the Debriefing part will be a problem as it was nearly impossible for me
to find some one to get this done. So I had to avoid the Debriefing part. But still, I worked on chartered sessions
and taking logs.

For taking logs, I used Rapid Reporter developed by Shmuel Gershon. I had used the Session Tester previously
for my exploratory testing missions. But having read a lot about Rapid Reporter through various blogs, I wanted to
give it a try. And I was really impressed with this nifty little tool (Thanks Shmuel!). I performed 6 chartered
sessions using Rapid Reporter and it was a great help in my mission. I really liked the automatic creation of that
CSV document, that was virtually hassle free :) How I wish to publish one of those documents here, but I’m bound by NDAs!

So, all in all a great experience and I’m happy that I provided a worthy report to my user champion on the product.
I couldn’t continue my work on that product even thought they wanted me to :( A couple of other projects came up
which needed my attention. There is an offer to train a junior tester for the above product, which I’ve gladly
agreed. Hoping to pass on some good lessons. Will blog about it once I complete it.

Off Topic: It’s been a year since I started Blogging! Whoa!! :) I want to thank all my readers/followers for your
encouragement, your support has been invaluable to this blog and my career as a Software Tester.

Until next time, Happy testing :)

2010 in review

WordPress thinks I was on fire last year :) Hey, thanks for that wonderful stats dear people at WordPress! Love you :)

Now if you are interested – please read the report :)

The stats helper monkeys at WordPress.com mulled over how this blog did in 2010, and here’s a high level summary of its overall blog health:

Healthy blog!

The Blog-Health-o-Meter™ reads This blog is on fire!.

Crunchy numbers

Featured image

A Boeing 747-400 passenger jet can hold 416 passengers. This blog was viewed about 2,100 times in 2010. That’s about 5 full 747s.

 

In 2010, there were 11 new posts, not bad for the first year! There were 8 pictures uploaded, taking up a total of 520kb.

The busiest day of the year was August 4th with 65 views. The most popular post that day was To my beloved… bug!.

Where did they come from?

The top referring sites in 2010 were satisfice.com, digg.com, twitter.com, forums.utest.com, and Google Reader.

Some visitors came searching, mostly for defect triage james bach, elementary my dear watson, ujala techno bright, how to show passion for software testing, and deduction my dear watson.

Attractions in 2010

These are the posts and pages that got the most views in 2010.

1

To my beloved… bug! August 2010
2 comments

2

Elementary, my dear Watson.. June 2010
8 comments and 1 Like on WordPress.com,

3

The Man Leaves home puzzle.. Are you limiting your thoughts? May 2010
2 comments

4

About Me November 2009

5

A question, answers and a session with James Bach.. March 2010
9 comments

Follow

Get every new post delivered to your Inbox.