Story of how a hang becomes a crash (because testers love reporting crashes)

I am doing my first exploratory testing workshop for 2011 and first from Moolya Software Testing Pvt Ltd. and I am excited about it. You can find the details by clicking on this link . If you are in India and plan to attend it, please do it quickly. I usually don't take a lot of participants although I know I'd gain more money out of more participants. Ever since I announced it yesterday, there are 4 seats that got filled within 5 hours.


Now, I am going to tell you a story that I had been hiding for quite a while. Not intentionally hiding but was planning to blog about it and the time is right now :)


I provide many applications to test in my workshop. At the end of a testing session, I check with the participants if they found any crashes with the application. Not to be surprised, a room full of testers, they do report crashes.


I ask them to reproduce it with me watching what they do and here is a shocking information; most of what they report as crash weren't crashes at all. What you are about to read is also a great example of confirmation bias that I have witnessed.


Here is what they are doing: They are performing an input constraint attack or providing a large set of characters as an input to a field and hits the "Submit" button. They wait for 10 seconds to see what the application does and on seeing the application in not responding state, kill the application and report that as a crash. 


Awesome! Isn't it?


Now, I got conscious of the fact that testers seem to be reporting a hang as a crash and was keen in looking at live projects during my consulting assignments. I get access to the bug tracking system during my consulting (wow) and I see patterns of such reports. 


I go filter out some of the crash reports from the bug tracking system and try to attempt what the tester did to report that type of a crash and bang, that's a hang.


I have made this point to testers who attend my workshop in order to help them be more conscious of what they are seeing versus what they are reporting versus what they are eager to report versus what they should be reporting. 


It seems to me that testers have an anxiety to report crashes. There's nothing wrong in it but it goes horribly wrong when you report a crash by fooling yourselves and the people around you. I recently blogged about the Obsessive Checking if being mentioned disorder that I was suffering from and here is a relevant excerpt from it, "Months later, I started replacing every word by my name till I saw my name on others post. So, I may have read a few posts without actually learning anything from it because all I saw is "Pradeep" & "Tester Tested" on those posts."


Now, why is that relevant to this post? I see that the testers I have witnessed who report hangs as crashes also appear to have a similar problem of obsession towards reporting crashes that they appear to not see a hang but see a crash. I would love if you ask if these testers ever report a hang? Yes, they do. If an application recovers before they kill, that's a hang.


I understand that an application might have hanged because it has crashed but how do you know? Oh yeah, allowing the GUI to fool you and me?


Here is an excerpt ( and tweaked to hide confidential information ) from an issue that I reported on Sep 30, 2010 @ 12: 13 PM IST (thank you Jira) while testing a new OS that is soon to be launched. No, not Chrome OS.


"I opened Media Player application and made an attempt to subscribe to a podcast. 
The application appeared to hang and it also did not allow me to close using the X mark on top right corner.


In an attempt to kill it, I navigated to XXXXX (product name masked) and tried closing it from there. However, the XXXX is open and Media player still seems to be remaining in the hung state.


From that point, I might be forced to reboot the system to get out of it or can escape by waiting for a longer time that I waited for Media Player to recover (>5 mins). No user to my knowledge would wait for more than 5 mins to see the Media Player function. Even a reboot appears to be a faster option" 

Now, if that was the Description, here is the summary :

"Unable to kill a XXXX when the application in it appears to hang or is busy"

• Why I posted the above? Is it because I wanted people to note the usage of the word "appears"?
• Why did I make a few words in it bold? Is it to highlight it?

Long ago, well, not so long ago, I blogged about how teaching testing is helping me test better. The above post and the bug report I posted, is another example of how teaching testers has helped me do it a lil better.


Now if you are going to be sitting at my workshop and be worried if you are going to make mistakes that I am going to highlight, please be informed that you are paying to my workshop to get into the safest environment to fail. No managers watching you. No clients frowning at you. No appraisals being done. Just your own dream of personal excellence aching you for not being there yet but being happy that you know why you are not there. Its a wonderful feeling.


Now, for some marketing again :) You can find the details of my upcoming exploratory testing workshop titled "Accountable & Manageable Exploratory Testing" by clicking on this link 


Happy Republic Day folks!

the 5 years of blogging as Tester Tested

I am a changed man today. I didn't know I would be here when I started this blog exactly 5 years ago. I want to thank you all. I don't know if this blog has influenced you in any way but it has definitely had a huge influence on one tester I know - me.

Thanks to all those who motivated me to reconsider blogging when I almost announced I will stop after a lot of plagiarizing incidents. Today, I am least bothered if someone plagiarizes. I have learnt sick people exist in this planet. Hey, it wasn't bad learning. It also told me that there were great people and I should care for them.

Instead of me doing my usual blah blah, why not you comment and tell me the posts you like from this blog and why? If you don't comment, I won't assume anything :)

News - Moolya Software Testing Private Limited launched

I have been patiently waiting to write this post. Many times I wanted to but then I postponed it to this moment and I would tell you why. The news is: Santhosh Tuppad and I have co-founded Moolya Software Testing Private Limited in Bangalore.

What this means to customers, you and the testing community?

That's an important question we'd like to answer. We are going to be offering testing services. Take a look at our logo and that would tell you the first part of the story. Do you know what Moolya means?

We wanted our name to depict what kind of testing we practice and offer our customers. The central theme of our testing is "cost versus value". Moolya is a Hindi word which has two meanings: cost & value. We simply loved it the moment we discovered it. Added to that was domain name availability. It was available and we just jumped on it. 

We crowd sourced the logo design and ITdude (as the designer likes to be called) from Philipines did this excellent logo for us that symbolizes what we wanted to depict as our next theme of testing than cost versus value - using brains - thinking skills & not rote procedures. My uncle who has been a logo designer himself, gave a little touch of his own to the logo to add a vibrant color and choose the font and design our business cards and letter heads.

Then on the services part, we choose to target people who value good testing. Fortunate for us, even before our incorporation, we had a customer wanting our services. Our first project was to test a Cloud Based Operating System. We felt blessed to have that kind of a start for our company. The client was and is happy. They have given us more business.

For those planning to outsource their testing work or seek consulting, the services we offer are

• Offshore testing services
• Exploratory Software Testing Services & Session Based Test Management
• Check (Test) Automation & Test Design Automation
• User Rejectance (Acceptance) Testing & Beta Testing
• Consulting & Training
• Staffing++

So what, everybody provides that? As every company says they are different, we'd like to say, we aren't just like those different folks out there. You should consider visiting the Services page for more details.

For testers  

We hire testers, isn't that good news? ;-) More than that, our interviewing isn't going to be traditional or easy. You don't send us your resume, you send us your test report, a contact number and an email id we could get in touch with you. We would discuss about your test report and get you to test software and put you in different contexts. That's our way of hiring. Even if we scale to thousand testers, maybe, in a couple of years, we will hire that way. Right from freshers to senior people, they should be good at testing. If in case you have a certification, we don't have a problem with that. We don't care about your certification because we care for you. We are working hard at planning and creating a women friendly organization. We are also going to be tapping a lot of hidden talent.

We believe and practice what Fiona Charles said, "Lousy customer service often comes from unhappy employees. Treat people well & they'll pass good will on." 

We will treat you well. You may like going through our Careers page

For the community

We are working on putting our office open to all testers during Sunday. We are going to be stocking lots of good books (The Weinberg, The Kaner, The Bach, The Koomey, The Guaspari, ...), providing you power and internet and you may make the best use of it. You may end up meeting other testers who have come in to read books or practice testing, and can enjoy what you enjoy the most - learning to test & continuing to be better at it. You might find Moolya employees on Sunday chilling out if they need with you folks. Wouldn't it be great if we provide free wi-fi to those who wouldn't download movies but use it to learn testing? Yes, it would be.

We currently have a 25 seater office and as our business expands, we'd like to care for more of you. We just hope to make this company a dream company for good testers. We know we will make it.  

Why we think Moolya Testing is special?

Moolya belongs to a very important time period in testing. It is started by those who started their career as a tester, have remained hands on & shall remain hands on. They may hold the designation as the Director or CEO but they can test good if not great. They have at least played a small role, if not big, to stir the beginning of Renaissance in Indian Testing. They know what customers want, they know what testers want. They are young yet experienced, with lots of energy & passion. Most important of all, they have nothing to loose, so they can be crazy, creative, sound jazzy, cool, and do things that other companies just isn't doing. They are the Microsoft & Apple of 1970's. They are the Google of the 1990's. This would probably be the first Indian services company that would not talk about "head count" but talk about "brain count" of their employees.

Our culture

Just because we are testers, it doesn't mean we haven't educated ourselves on anything else. We have put special emphasis on our culture. We have been working on things that can make a great culture to a company. What is that? We'd get our employees tell you those stories, than we letting all of it.

My wishes to Santhosh Tuppad

I'd also like to mention that by having co-founded Moolya with me, Santhosh Tuppad, must have become the youngest tester entrepreneur. Congratulations to him. You are a bravo.

Going forward, India might see more such. As I said, Moolya Testing is the first of its kind company from India that is aligned with the Indian Testing Renaissance. 

Thanks

A note of thanks to my colleagues Parimala, Sharath Byregowda, Manoj Nair, Dhanasekar S & Mohan Panguluri, Vipul Kocher, Nandan Pujar, Satish Thakur, James Bach & Michael Bolton for the support they have offered so far. Needless to say, without our parents, siblings & family help, we wouldn't have been able to achieve this. 

Follow Moolya Testing

Feel free to join us on Twitter, Facebook & LinkedIn. Peruse through our website. I postponed writing this post multiple times to be able to write this from the office of Moolya Software Testing Private Limited. We are in JP Nagar 2nd Phase, Bangalore. Feel free to contact us. The story of starting Moolya Software Testing Private Limited will be launched as a book in 2011. It's going to be self-published.

"Consider engaging Moolya for your testing needs, we'd like to put smiles on *your* customers face." 

Bangalore Workshop on Software Testing - 2 on 3rd April

If you have been my blog reader for a while, you are likely to be cognizant about Bangalore Workshop on Software Testing or BWST. If you don't know about it, no problem, the post and details are still there. So, BWST – 1 was attended by testers from Bangalore, Pune, and Mumbai. Oh, you should read the experience report and you’d realize how much fun we had or how much fun you missed. 

So here comes the announcement of BWST 2. Santhosh Tuppad and I are organizers of this event and Parimala would be facilitating the workshop. Vipul Kocher, President, Indian Testing Board has volunteered to be a venue sponsor for it.

“Cutting (c)trap and getting good things done”

Many experienced testers of India that I have come across, claim to have made at least one proposal of doing better testing to their management. Most of them also claim that the management doesn’t help to implement the proposed ideas. At times lot of gyaan is also given to them. Some of those testers, cut traps and get good things implemented. We thought it would be valuable to listen to such stories and real life experiences of how testers cut the traps that were trying to prevent them from doing better testing. We also love to hear failures. So, if you failed miserably or maybe you just failed and want to tell us that story, we’d be glad to hear that.

You have a story like that? Send us a one page abstract of your story to banwost@gmail.com with subject "Sharing my story at BWST2" and we will let you know if it makes to one of the six presentations of BWST – 2. If it doesn't, we shall invite you to be a part of BWST2. 

So, if you are not speaking at BWST-2, you still can participate in it.

This is an invitation only kind of workshop. However, you don’t need to upload your jazz dance video to Youtube, to get invited to this. It’s simple, you write an e-mail to banwost@gmail.com with subject "Participant at BWST2" providing details of you, your work and explaining why you should be attending this workshop.  As the cap for participants of this workshop is 30, we would urge you to hurry up. Details of venue and other help you might need will be communicated over e-mail to those registered participants.

As such a workshop is not happening elsewhere in India, we want to keep this open to people all over from India and for people like Mike Kelly, who might be planning to come down :) . We hope that such workshops might jump start in other places from India, too. 

Well, I don't quite understand why testers from other cities allow only Bangalore testers to have every bit of fun in testing? Whatever!

Cost

You don’t need to pay for anything unless you volunteer to sponsor a coffee for all. We just ask you to take care of your expenses such as your travel, stay (if you are coming from other places), and food.

If you are in Bangalore and willing to host a tester who comes from outside Bangalore, send an e-mail to me. Parimala has agreed to host one female tester who might be interested in this workshop and is coming from elsewhere in India. I am hosting one. Oh, by the way, we don't have a Taj Mahal view and gold rim wash basins at home.

Update : March 22: All seats have been filled. If you were planning to request for an invite, you are too late. I am sorry.

Progress Report 2009 : Pradeep Soundararajan

On clicking that image, the progress report should download. Hate that idea? You can download the same file by clicking on this link, too. 

Other updates: 

• There is a public workshop on Skilled Exploratory Testing planned in Chennai on Saturday, March 27th, interested testers send an e-mail to me at pradeep.srajan@gmail.com OR if you know of any testers in Chennai who want to attend this please pass them on the information. The fees are very nominal but please don't ask for Ranganthan Street rates!

• I am releasing a book this year. No, not the interviews book. Not that you have to pay for it. I am going to make it available online for free. I am tired of the process of getting it published. Maybe if it does well, some publisher would volunteer to slow down the process. Sharath Byregowda knows what book I am talking about. Hard bound printed versions shall also be available on demand. I need someone with real good English to help me copy edit the draft I have. 

Oh, don't forget to checkout 2009 Progress Report. It is a PDF file for sure. Thank you all.

Secrets of a Buccaneer Scholar : Free Download Limited Period

About a couple of years back, I had an opportunity to read "How I learn stuff" from James Bach and was excited about it. I had a concern about it that it was not complete and kept asking James for his plan on it.

Little did I know then that it would turn out to be a great book for the community and not one that was accessible to those who work with James. When I learnt from James that Simon & Schuster have agreed to publish it, I was excited about it and my urge to read the complete stuff skyrocketed. I must say that I had reviewed its initial draft and reading the book today is a fascinating experience.

I also thought I had enough money to gift it to all those people whom I care about. I certainly do care about those who read my blog and here is a gift that Simon & Shuster, James Bach has provided - It's free download till July 24th. The hard copy is going to be released on my birthday. ( Just a coincidence )


Why is this book one of the most important one's for software testers?


Learning

I recognize that learning and unlearning are skills that are absolutely important for any profession anyone is in. Today, I see a lot of testers struggling to learn the latest version of a tool when it is released, although they are aware of its earlier version. Learning requires mental modeling. If you have a model of learning then no tool or none of its version can intimidate you. Secrets of a Buccaneer Scholar can be of help to you.


Scouting

We witness so many tools everyday that we didn't know earlier. When we discover a tool that could have solved our problems in our last project, we are worried about what tools we are missing to solve today's problem. If you learn how to scout, you wouldn't find it tough to find the tool you want for today's need. We are in the Google age and we don't get to know the right link although we search for it because Google is not kind to everyone. It is kind only to those who know how to scout. Secrets of a Buccaneer Scholar can be of help to you.


Competitiveness

All of us want to be the most competitive in our field but honestly, how many of us are putting in the work that requires to do so or how many of us know what to do to be able to get competitive. Secrets of a Buccaneer Scholar can be of help to you.


Writing

I see that some testing bloggers mostly ape the way other successful bloggers write their posts. Doing that for sometime they are lost of what their original ways are and get into the rut of aping. While aping could be a way to start, it ain't the way to proceed. Secrets of a Buccaneer Scholar can be of help to you.


Fear of unknown

When you ask someone why aren't they self employed, most often you would find that they fear the unknown. The unknown is always bad according to most of us. I meet credible testers in India and ask them, "Why do you think you can't be an independent consultant?" and they say, "Currently my job is secure". Recession times guys - there ain't anything called "secured job". Secrets of a Buccaneer Scholar can be of help to you.


Value of reading

Most testers don't read books. What a great advantage they offer to people like me. Good for me but so bad for them. I am concerned about them. I wish they read just this book ( which is for free till July 24th ). I wish they read because I think after reading this, it might be influential enough to them to be able not offer me the advantage that I had.

To all those testers who don't have the practice of reading books: In case you come across this post or the book and you choose not to read the book, no one can stop you from remaining in your most stable state - ignorance.

Why good software testers should come out of the well?

One problem that I constantly spot whenever I meet a good tester in India - they don't blog and publicly write or speak. That''s why some people continue to think about me as a good tester.

The recognition that an organization gives could be fine as long as you stay in the organization or as long as the organization is doing fine. That's why many people stick on to an organization for quite sometime because they start hating fresh water. They accept to be in a well. With growing infrastructure needs and changing economy, some wells have to be wiped out and all frogs in it have to hop to a different destination.

I was once surrounded by bad frogs who made me feel that I was a great tester. I would never want to be there again because that hampers my learning although it pleases my ego as long as I am with them. A couple of months back I interviewed a tester who had been awarded as the best among 1100 testers of his organization. He was pathetic and I think the right one in the organization didn't get the award.

A tester from Mumbai who claimed to be superior to me in knowledge and skills wrote to me and said, "You are misguiding the community by giving wrong ideas" and my reply to him is this, "Well, if you are so concerned about the community then you should write a blog and say to the world that Pradeep Soundararajan is giving wrong ideas and the reasons of why his ideas are wrong" for which he never got back to me with his blog link.

There are several testers whom I helped to start a blog and only some of them are doing fine with it. Some people started a blog and sent me a link with a note that - you inspired me. If I revisit their blogs, most of them ended up not continuing it because they realized its hard to keep blogging. The other dimension is - it is easy to blog if you are just doing a cut copy paste plagiarize, not owe credits to original authors and expose yourselves as a fool.

2 months back, I interviewed Harish, who had lost his job from a reputed organization which decided to shut down its operations in Bangalore as they faced the worst part of recession at their US office.

Harish is the kind of tester whom I'd want to work with for the way he challenged my arguments, sharp eyes that observes little things going around the screen and has good reporting skills, good communication skills, but then, my client had to postpone their recruitment plans. I couldn't get an opportunity to work with him. If you are looking for one, I'd suggest you talk to Harish.

I wish I could have linked to his blog to get you curious about him and that's what is missing. I asked him:

PS: You don't blog?
Harish: Why should I?
PS: For the world to know about a good tester.
Harish: Why should the world know about me?
PS: Consider asking yourselves as to why shouldn't the world know about you?
Harish: Let me think about it.

After a month, Harish calls up, "Hey Pradeep, I haven't found a job yet. I realize this wouldn't have happened if the world knew about my testing skills. The interviews test something different than my skills"

So here is a post on my blog for all those Harish of the world to wake up and start blogging. A blog of your own serves a core purpose that surrounds all of us - to learn - things, ways, people, testing, ideas, challenges, and more...

Myths that surround wannabe-tester-bloggers

If I should blog, I should have good writing skills: Ha! You should read Pradeep's first post and then you would realize that he was more pathetic in writing than what he is today (or what you might have been a couple of years back). However, as you peruse through the blog you would realize that I have improved a thousand leaps. It comes from practice and a blog helps you to practice writing. Two things never happen to people with this myth - better writing skills and blog.


If I should blog, I should be an expert: I must admit that I thought of myself as the world's best tester till I met James and then more people like you. My blog has helped me meet thousands of people who helped me understand that I am not the world's best tester. That's important to learn because it gives me learning opportunity to try to get as close to what I think I was. You don't need to be an expert to blog but people commenting on your posts can help you to be an expert of the field. They might surprise you with a question that you think over for the next 2 years to find answers for it and in search of an answer to that question you discover a whole new world of testing.

If I should blog, I should have thousands of readers and comments: I am my first blog reader. I primarily write to practice writing and thinking. I have been writing this post over 2 days and I test my writing. It helps me writing some good documents at work that influences decisions. If my writing can be of help to others then I am glad. I do not write to get thousands of readers or commentors. No matter the world stops reading my blog, I would continue to write for one regular and serious reader - that's me.

If I should blog, I should write in a way that fetches appreciation: Saurav Ganguly, a cricket player from India was axed out of the team for poor performance a couple of years ago. The internet in India was full of jokes about his poor performance but then he made a great comeback to the worldcup squad. He was interviewed in NDTV for his comeback and a journalist asked him, "How did you make this great comeback when most parts of India, including Kolkata, your hometown was against your performance?" to which he replied, "I didn't spend time bothering things that are not under my control ( people making fun and jokes about his performance) and focussed on spending more time for things that are under my control ( practice, improving performance, consistent results in league matches) and I think that's what helped me". I took this as a great lesson to myself and focussed on doing things under my control and not bothering things that are not under my control.


If I should blog, I should have more time than what I have: Actually, we spend time on lot of useless things everyday. If you cut that out of one day in a week that provides you time to blog. I usually laugh at people who say they have no time to blog. I woke up a little early today to complete this post. I think I wouldn't die if I get up early. As James Bach said on Twitter: "I don't teach my son the value of discipline and hard work, because that *can't* be taught-- only learned."

If I should blog, I should be a good tester: A real good tester would want to get tested to see if he is really good and would be glad to know he is not good since that helps in improving him. A blog is probably one of the ways in which you get to know about the holes in your education as a tester. Once you know that, start plugging them. You could aim to be a good tester and start blogging than wait for you to become a good tester and then start blogging.

There are number of other ways you can demonstrate to the world about your testing skills and I think you should do that. Ah! No, not by saying you are proud to be ISTQB certified, that would drive away people.

PhilK recently interviewed many tester bloggers and I was one of them. Read my interview here and do not forget to read other interviews as well.

If you are good, the world should know about you. If you are hesitant to let the world know about you - you aren't good enough, maybe. Good tester doesn't mean you offer advice to the world, it means you present your work and be open to learning from others if they happen to argue. You may be a good tester and choose not to write a blog, I still respect that but I think you can get better by writing one.

So, time for you to get back to your work, ignoring all things in this post and continue to say, "If I should blog,". If you are already doing it get more people to be like you or do more with that.

Update: There is a test challenge at Test Republic that might be of your interest

Bangalore Workshop on Software Testing - BWST - 1

I interact with the Western world as much as I interact with the Eastern part. One of the things that the Western world does well that the Eastern part does not even do (significantly), is Peer Workshops. When I funded myself to be at CAST 08 conference, Toronto Workshop on Software Testing (TWST08 ) was a huge bonus for me. Thanks to Fiona Charles and Michael Bolton for allowing me to participate in it.

My first day at Toronto, Canada started in TWST08 even before I could get over the jet lag. I found that the Workshop was a great way to overcome jet lag. What I learned from TWST is still resonating in me and is of great help to my career.

I cant afford to fund myself to attend such peer workshops every year but I can definitely afford to participate in ones that happen in India. I tried to make testers meet happen in Bangalore when Michael Bolton was around here last time and it did not gain momentum after the first meet. I am forced to think that people turned up to hear Michael Bolton and they would turn up again when he's back. Prove me wrong.

Since then I was in a constant look out to meet people who would turn up for learning and I have found a couple of them. am also aware that there could be more people and that's why I am blogging about it.

There were lots of informal meets between Ajay, Manoj, Shrini, Rahul Verma, Vipul Kocher, Dhanashekaran, myself etc... and we did keep craving for more such things to happen. I think India cant afford to wait more to get started with Peer Workshops and this is an announcement for the same.

Mohan Panguluri, COO, of Edista Testing Institute who was awarded for his Thought Leadership in Software Testing in 2008 has opened up Edista's office premises for this Workshop. He has vowed to provide space to all future BWST workshops. Thanks a lot Mohan. You are setting a great example for other CXO's to follow.

Theme of BWST - 1 : Changing the way people test and think about testing
May 2nd, 2009

I believe that the first testing assignment that anyone did was handled pretty bad by them as compared to what they might be doing after a couple of years. However, growth stops at some point for many testers and only a handful make it to be real good testers. Those who turn out to be real good testers constantly kept changing themselves as they learnt new things and those who turn out to be bad were the ones who hardly changed. In India, we know, some of us struggle to change the environment around us to learn as much as we do.Similarly there are people who without much struggle get the environment around them to feel happy without any learning.

So, you could have changed your way of testing or others way of testing and you could have been resistant to change. Send in an ( one page ) abstract of your experience report that you wish to present at the first Bangalore Workshop on Software Testing by 18 April, 2009 and you will be informed if your talk is accepted for presentation. Failure stories are more inspirational than the success ones. I hope everyone has plenty of both sides.

The max limit is of 10 (maybe 15 if pressure builds) participants for the first BWST and hence if you plan to attend, remember that we work on First come First Serve basis. So, send in your abstracts of your experience report that you wish to present and keep in mind the theme when you do that.

Handbook : Please refer to LAWST Handbook and those that can apply to our context, will. We are flexible in changing things based on our first few Workshops.

Note: This isnt open to testers only from Bangalore. Anyone's welcome.

Also, you can start your own set of peer workshops in anywhere in India ( or anywhere in the world ) and no one is going to stop you. When you start, kindly let me know about it in advance so that I can plan to be there, learning from you all.

Email id to send in your abstracts: banwost [ at symbol ] gmail.com and we will have our own website soon. By May 19th, I will post an update on this and that's how we proceed. Are you going to remain silent? Are you going to change?

Excerpts from participants work - Practical Hands on Software Testing Training

• Are you curious to look at excerpts of the participants work that we have been consistent in achieving from Hands on Testing Training that I talked about in 2008?
• Are you aware of the power of young generation?
• Are you aware of the power of coaching them with better education in software testing?
• Are you aware of the impact of providing better education in software testing to young generation today is going to be one of the key factors of deciding the future state of software testing?
• Are you aware you can read more about this?

Read more... and write to us ( isupport [//at//] etifinishingschool.com ) know if you'd like to support this initiative.

Audio Podcast :: What Software Testing Could Be?

If you haven't noticed that I have been doing audio [and video] podcast series Testing Stories from India, no problem. You have known it now.

Here is my latest podcast: What Software Testing Could Be? [ 3.18 MB ]


Summary:

• There could be about 28,000 definitions of software testing
• What? Are there rules of software testing?
• Many testers don't test their own definitions of software testing?
• Certified testers hardly speak about the definition they learnt to get certified.
  
• What is Pradeep Soundararajan's definition of software testing?
• What tests did I do on the definitions I subscribe to?
• What is your definition of software testing?
• Have you tested the definitions you subscribe to?

Previous Podcasts:

• The word "TEST"
• Test Plans Aren't Ice creams
• Testing Lessons from Beer
• Indian Testers and Fake Experience

Software Testing Videos:

• http://www.viddler.com/explore/testertested

If you can't download these because your organization firewall doesn't appear to have bugs that let you download these, write to me, I shall send you a copy in an e-mail.

Learning to test better by teaching testing

Make a list of some of the teaching staff that considered bad at school or college. You might be able to notice a pattern - most of them were not willing to learn while they were teaching. Here are some of my stories and attempts that I made during my experience as a coach in software testing.


Story 1

I was teaching at Datamatics 2 weeks before. When it was time to officially end the workshop, a participant asked me, "What did you learn in these 2 days of workshop?". I was so happy to have got that question. I thanked her for the question and listed some of the learning I had in those 2 days. 

I also mentioned to them that I make a note of the learning I have in one or the other way. I also mentioned that my blog acts as my note taking tool at times. As you might have seen my Progress Report, the list of events and experiences that I had in every year is well documented.

The question, "What did you learn by teaching me?" is a powerful question to ask someone who is claiming to teach you because if the person has nothing then you know you might not want to sit in that class anymore or being in that class is a waste of your time. 

In some places I have an answer, "I learned that you can't be taught at least by me" and thankfully those people don't ask me that question. Learning and teaching needs an open mind. I think I must have a close mind to say, "Not everyone have an open mind".

I have learned some great deal of stuff about how to test better by teaching testers how to test. I understand that my brain is not capable of asking all the questions that I'd love to ask myself and hence I need other brains to ask me those questions. Where do I find those brains if I am stuck in one place and I keep interacting with just the same team for over years?

An year and a half back Ben Simo mentioned to me the idea of "Apply inputs that force all the error messages to occur" from James Whittaker's book while we were discussing about error messages. I liked the idea and it then got included in my armory of heuristics to test a product and helps me in model the product in more ways than what I have been doing.

Recently when I was teaching the Hands on Testing Training for Freshers for Edista Testing, Muhammed Kothari, pointed out a tool to me that helped in displaying all error messages programmed in most Windows applications. At every workshop, I ask the participants to challenge me in demonstrating the kind of testing I talk about. At Datamatics the challenge was to demonstrate testing on Microsoft Freecell game. On using the Process Explorer tool, I demonstrated how I could learn how many error messages the product is programmed with and designed my tests to all those error messages ( in other words, all printable strings from the program ). That's one way of demonstrating coverage.

Some curious testers were excited about it and came up and said, "I'd like to use the tool. It helps me find out areas that I might have been missing while testing the product" -- which is cool. [ some? well, one. :-) ]

That's just one of the many ways in which Process Explorer can be of great help to a tester. Note that Process Explorer is a tool. A tool that a tester can use to augment his testing effort and do a better testing. Tools are not just QTP, Winrunner, Loadrunner, Silk, Cotton, Wool etc...

Story 2

Lunch tables are a great learning ground. At Datamatics, I was joined by a group of testers at the lunch table. I ordered for a Dal Kichdi that some other people had ordered too. As I ordered late, others had started off with what they were served. When I got my Dal Kichdi and rowed the spoon over it for grabbing the first bite, I saw a hair (hopefully human one) in it and then found more. I picked a hair and showed it to testers and asked, "Did we order for this?" (meaning, no one order for bugs to be served with the software they buy) and then the brilliant Saurabh Sahoo, Test Lead at Datamatics asked, "Do you know why you found the hair while we didn't?", and the curious me said, "Can you explain, please?" for which he said, "You were looking at the plate while we were so much engrossed in the discussion and were watching each other's face".

That's a nice observation. It helped me explain to the people over table - that's what happens when you run scripts or test cases that have an expected result, "You are too much focused looking at the expected result that makes you blind to see other things happening in the environment. Having multiple oracles in your mind helps you see more than just the expected result and hence you'd be able to spot more problems than what you have been doing". 

I also added to it and said, "I wish we could say to our customers, why are you looking at the screen?" when they say they found a bug with our software.

I think that at least made Saurabh Sahoo convince that its worth spending time to learn things that I was trying to teach (and learn) and he spend an additional two and half hours after the workshop with me and he is determined to do a much better job. I learned a great deal answering the questions he asked me on clearing traps.

Answering questions like that definitely helps me in negotiating with management and clients.

Story 3

I was teaching at a Fortune 100 organization in Pune a couple of months ago. Within just 20 minutes of starting my workshop, the Test Lead announces to the whole class "This is class is a waste of time. Lets go back to work".

• How do you deal with such a situation? 
• How do you teach someone who doesn't want to learn from you?
• How do you put them in a receptive mode? 
• How do you know what to speak to them? 
• How do you know if its worth speaking to them anymore? 
• How do you know if they are more right than you?

What if you are in front of your customer and your customer wants to walk out of a meeting because they didn't like your idea? You might not be able to afford to lose all customers especially if recession is around.

I made an announcement, "All of you have the freedom to walk out of the class but I'd be happy if you answer a question: Have you ever walked out of a movie just because the titles of the movie suck?
 
If your answer is No, why would you want to do it here?"

Plus

I did something that I learned from the book Turning Numbers Into Knowledge that again cites Bruce Lee's master. 
I took a tea cup and poured water into it and kept pouring despite the cup overflowing and quoted Bruxe Lee's master, "Either your cup is too small or it is already full of opinions".

The result: I am teaching in the same organization again next month. The legs that rose up to walk out sat back and enjoyed the ride. Some even wrote to their management to have the class for other testers in their group.

Story 4

A common problem that most testers talk about - is being caught for missing a bug when a customer finds it. A tester in one of the previous workshop said, "It is my responsibility if I miss a bug and hence I have to be more careful with the tests I do". I was reminded of what Michael Bolton said, "I am a character in the story of how a bug got missed". It indicates that, we testers are a part of the entire story and we do not play the hero role in a bug that missed our hands.

That tester was adamant that testers should be made completely responsible for it and not anyone else because it was their fault and they shouldn't have missed it. I tried asking him, "How about making the person who put the bug into the product more responsible for it than you?" and yet that didn't help.

I made a pretty bold move, "I am going to slap you now. Would you blame yourself for standing in a place where I was swinging my hands or blame me for doing something I shoudn't have done?"

That tester remained adamant but other testers got the message that a tester is a character in the story of how a bug got missed and not the hero in the same story. Later that night when I was self retrospecting, I realized that I should have used a non violent example to explain it. Teaching testing to experienced testers helps in correcting your communication and thinking aspects.

Some important points to consider

• It is easy to teach dull minds that don't oppose and appear to nod for every idea that you share with them. Teaching bright minds are tough and demanding. They teach you a lot about how to test better and what more I want than that.

• Most people who teach testing in India at several training centers haven't done testing at all or haven't done enough testing. So, those who have remained a hands on tester and teaches testing gains a competitive edge.

• If you have that competitive edge then there is good money as well.
  

• Helps in meeting a lot of different kinds of testers and understanding different contexts, problems and different solutions to problems. It helps in avoiding traps much better and faster and translates to better testing.
  

• It is a challenge to get to know more about ourselves, get tested , refine communication, thinking, learning, teaching and testing skills.

• Make a list of some of the great testers you know ( in my case Jerry, Cem, Ben, James, Michael, Scott, Kohl, Elizabeth, Vipul ... ), you'd find that they teach extensively. Oh, you have been doing that as well but probably you have been teaching yourself all this time. Think about why do they do that?
•  
•  Go, at least teach yourselves. 
•  
• Teaching, teaches the teacher about teaching
  

If you are a tester and is interested to join a small test group that specailzes in coaching, consulting, and testing services, write to me. You'd work with some of the upcoming very good minds who care and live for benefitting the software testing community. Write to me: pradeep.srajan@gmail.com

Progress Report 2008 :: Pradeep Soundararajan

Click on the image below to download the full verison.



Alternatively, you may right click on this link and save the file to your desktop.

Hands on software testing training - Change we need!

All workshops that I conduct has lots of elements of hands on testing and thinking exercises. I myself benefited a lot from hands on testing training approach that James and Michael do in their Rapid Software Testing class.

Over the last few months, I have been working on models of hands on training on software testing for freshers and people who are interested to be good enough to start testing computer software and for organizations who have a tough time getting people to test with lesser supervision than the current magnitude.

I have always been worried about the value of showing thousands of slides on software testing without actually getting a person to test, especially when a person hasn't had any testing experience.

"An ounce of practice is better than tons of theory" - Swami Sivanada

So, here comes a 30 day course on software testing that is hands on training from Satisfice India in partnership with Edista Testing Institute. Edista would be happy to place the participants of this kind of training to their clients who have been wanting freshers and candidates who can test as their resources.

If you were to make a choice between a A+ certified tester who got certified A+ merely based on answering 100 questions versus someone who has a certificate of successful completion of a hands on testing training, whom would you choose?

If you know of any fresher in India, or, if you want someone to benefit from this training kindly ask them to call Noorie @ +91 96322 22326 or e-mail her at noorie.a@edistatesting.com and ask for the hands on testing training for freshers.

I wish I can take a bet against those certification people to challenge those who attend this kind of hands on training for the same 30 days that the certified people take and ask them to see the value. I think I definitely can when I show you the results in the coming months.

Now, what I have written here might not be so wooing as a commercial ad of a testing training but I believe there is more value for the cost and is more worthy of someone's time if they want themselves to be trained good enough to start testing a software.

Oh! I didn't talk about the cost. This training costs twice as much as my 2 day Exploratory Testing class. Yes, its that affordable! And, there are only 6 more seats to be filled.

The good news is, I interviewed Testing Heads/ Vice President - Testing / Founders / CXO of organizations like - Wipro, Applabs, Patni, HP, Target, National Stock Exchange, Infosys, AIG, Edista Testing, VM Logix, ITKO Lisa, Deloite Consulting... at STC 2008 conference last fortnight and asked them a question about hands on training than mere slide show. You guess what their answer would have been or watch the videos at Test Republic in a couple of days.

One of the change India needs is here!

--
Pradeep Soundararajan :: Software Testing Videos: http://www.viddler.com/explore/testertested

Note: If you are interested to attend a 2 hour session on Exploratory Testing in Chennai on Dec 9th e-mail Noorie

Grammy Award for Michael Bolton and others

Michael Bolton, the singer has won Grammy Awards. This Michael Bolton , a little known mandolin player and largely known singer of good intellectual software testing has been awarded for his innovation and contribution to the community you and me live in, at EuroStar 2008, one of the biggest conferences in the world.

Wait a minute, T H E Y won the award!

I just want to celebrate this more than any of my own success because it makes me so proud that my singing is influenced by THEY. Read more ->

Some Indian testers won thought leadership award at Test 2008 conference. Wondering who they are?

Plus, at STC2008 conference that concluded today, Sharath Byregowda, ( another proud moment for me ) won the Best Contributor award for Test Republic

What does all this say to you?

If you want to be a tester who goes beyond the traditional, great recognition awaits you BUT if you do things just for recognition you won't get it. Come out and communicate if you haven't been communicating or else you will see yourself vanishing.

I am sandwiched between my guru and my student winning the award at around the same time. What a fantastic moment for me. During the toughest of the times, I kept hoping that software testers who focus on human skills should shine in the future and those who aren't willing to challenge their minds should vanish.

This is just the beginning of a greater success of these people. Wake up or Vanish!

Exploratory Software Testing Demonstration Videos

You have read enough things from Pradeep Soundararajan. Some of you even believed what he wrote. Some of you thought it was stupid. Some of you follow it very closely. Some of you got irritated by it. Some of you relied on what he wrote for guidance. Some of you enjoyed the writing and others hated it. Some of you thought he was faking. Some of you didn't bother to read what he was writing all these days. Some of you thought he is talking about ideal world. Some of you thought what he talks isn't practical. Some of you will always think good or bad about him no matter what he does. No matter whatever you think of him, he will keep doing things because what fuels him is, himself, primarily.

Now here is my testing open to public scrutiny. A Rapid Tester stands up to scrutiny. Here is something that can stand up to public scrutiny:





That's just one of the 7 videos I have come out with. If you are reading this post, you could find others as well. 7 isn't my limit but at a start. From now on, every week or two, you could find a new video. Not all of them would be published on my blog so don't rely on my blog to get updates. Figure out a way. Also you could download those videos if you wish to watch it offline or to watch it more than once.

Jonathan Kohl wrote about the importance of testing videos here .

For all things you couldn't believe about exploratory testing, human testing skills, rapid testing, context driven approach, pair testing, etc... here is one of your chances. Alternatively James Bach, Mike Kelly and other testers have their own videos which you could find on Googling.

The horse can be taken near the water. The horse won't drink the water if it thinks its not thirsty or it can live without drinking that water or for whatever reason the horse decides not to drink. I know, you aren't a horse or at least you don't appear so.

If you wish to be a part of these videos, drop an e-mail to me. Thanks to Ajay Balamurugadas and Sharath Byregowda for their enthusiasm in helping me with these videos and for pair and trio testing with me.

Operation Roshan has just begun.

Update: 18 Sep: When we watch a movie, we usually fall in love with the actor and actress and forget the work of people who made the movie to happen being at the backstage. Similarly, I forgot to include our host for about 2 days since I posted this who facilitated the video creation, place, resources and provided space to sleep overnight - Edista Testing Institute and Test Republic. When I asked what Edista means, I got a reply as "Facilitation" and this is an organization living up to what its name means.

Thank you folks!

--
Pradeep Soundararajan - http://testertested.blogspot.com - pradeep.srajan@gmail.com

"The test doesn't find the bug. A human finds the bug, and the test plays a role in helping the human find it." --

Great testing stories from India (Created by Not Following Any "Best Practices")

I would be presenting my workshop on Rapid Software Testing Excersises + a paper at Asia Pacific Software Testing Conference at Kuala Lumpur, Malaysia between Feb 24 to Feb 29, 2008. I wish to thank Vishal Manghani of Processworks Sdn Bhd for the invite.

So, here goes the abstract for the paper I am presenting at the conference:

Great testing stories from India (Created by Not Following Any "Best Practices")

Authored and Presented by Pradeep Soundararajan, Consulting Tester - Satisfice Inc & Test Manager, TriVium Systems, India

When I was 4 years old, I used to eat sand (not because my mother didn't like me eating sand nor for the reason of poverty but as a child, I think, I liked exploring sand as another food option for me) . It was my mother who helped me know my act of eating sand during child hood and referred to me as 'naughty' during childhood.

I could eat sand without knowing it was called 'sand' and I could be naughty without knowing I was called 'naughty'.

When I started my career as a tester and found the first few bugs, I was told by a senior to do more such "negative testing" to find more such bugs. I asked him, "What is negative testing?" and he replied, "Whatever you did to find these bugs is negative testing".

I could do negative testing without knowing that someone refers to what I am doing as 'negative testing'.

Years later, I blogged that I still didn't understand what negative testing means but ideas of what it could be.

It took me a couple of years to learn that I do many things without knowing how someone calls it and then learned from others how some parts of the community I live in calls it.

All these stories indicate that we might be doing great things without knowing it. What is important to us is doing great things and not necessarily knowing the names but it is good to know the names of the great things we do when we intend to communicate with other people.

Anything that works great for me could make you fail badly. For instance, I can live a 100 years eating curd rice and pickle but you may die falling sick of it OR what medicines that could save me from a headache could kill you because although the common problem we might have is headache, the actual root cause is different .

If you disagree to it, 'best practices' fit you well.

If you agree to it, then I am sure you understand why doctors prescribe different medicines for the same person, the next time he /she gets a headache.

In this presentation, you would hear some of the great stories of Indian software testing that fortunately I was a part of and played a role in helping teams achieve the success. What might surprise you is the fact that those teams who did not follow 'best practices' tasted success that teams who claim to follow 'best practices', dream to achieve.

If you are going to listen to these stories in my presentation, I warn you to be aware that you *cannot* see the same success if you try doing things we did.

Welcome to context driven testing!

I would not be able to reveal anymore details about the presentation unless I am done with it but I welcome arguments, questions or success stories that you might want to share with my readers. I think I should be able to publish the slides for the same, post my presentation.

--
Pradeep Soundararajan - http://testertested.blogspot.com - +91-98451-76817 - pradeep.srajan@gmail.com

"The test doesn't find the bug. A human finds the bug, and the test plays a role in helping the human find it."

"If you can see it in your mind, you will find it in your life" -- Scott Barber

I saw in my mind that someday, I would be attending Jerry's workshop.
I saw in my mind that someday, I would see James Bach in live testing action.
I saw in my mind that someday, I would show Ariel ( Michael Bolton's daughter) how autorickshaws in India zoom.
I saw in my mind that someday, I would go around Toronto with Michael Bolton.
I saw in my mind that someday, I would get a chance to meet with Dr Cem Kaner.
I saw in my mind that someday, I would see Mike Kelly hosting a conference.
I saw in my mind that someday, I would have lunch with Karen Johnson discussing our experiences in testing.
I saw in my mind that someday, I would meet Scott Barber and learn more about Performance testing.
I saw in my mind that someday, I would meet Jon Bach and explore exploratory testing with him.
I saw in my mind that someday, I would meet my dear friend Ben Simo.
I saw in my mind that someday, I would meet David Gilbert and learn stories of his creation - Test Explorer.
I saw in my mind that someday, I would meet Harry Robinson and develop my model based thinking.
I saw in my mind that someday, I would meet Matt Heusser and learn more Creative Chaos.
I saw in my mind that someday, I would be introduced to John Kohl, a musical exploratory tester.
I saw in my mind that someday, I would meet Geordie and get a chance to listen to Rapid Tester Song, live.
I saw in my mind that someday, I would meet Adam Goucher and thank him for his constant feedback of my blog.
I saw in my mind that someday, I would see Braidy Tester gathering ideas to make more developers cry.
I saw in my mind that someday, I would attend Johanna Rothman's testing workshop.
I saw in my mind that someday, I would meet Elizabeth Hendrickson and help myself think more agile.
I saw in my mind that someday, I would see all stars glittering a few centimeter from my eyes.
I saw in my mind that someday, I would see and experience more things than what I see in mind.
I think I am going to find most of the above in life, this year, at CAST 2008.

If you have such a dream and being in India makes you feel as disconnected from all great action, send a paper to CAST 08 conference and you would see it in your life, too.

If you have all the above in mind then I urge you to have one more thing -- to travel with me on a 24 hour flight to Toronto, Canada from India, discussing and playing testing exercises or testing the in-flight entertainment system [ of course, without bringing the plane to a halt mid air :)) ]

I am all set to travel to Toronto, Canada for CAST 08 where all the action is set to happen. If you enjoy testing, learning and challenges - CAST is one of the ways that can cast you in such a situation. My current boss has disagreed to sponsor me for this workshop but that doesn't stop me. I have decided to attend CAST 08, shelling out all expenses I would incur from my own pocket. No, I am not rich but I feel I would be too poor as a tester if I dont make it there this time.

Are you going to be on my next seat?

Pradeep Soundararajan - http://testertested.blogspot.com - +91-98451-76817 - pradeep.srajan@gmail.com

"Pradeep's first language is not English--his first language appears to be testing." -- Michael Bolton

Progress Report 2007 of Pradeep Soundararajan

Happy New Year wishes to all my readers.

It is exactly one year since James Bach officially hired me to represent Satisfice Inc in India. James Bach wrote in his post Satisfice India, "A Satisfice tester, (as my brother Jon, at Quardev will tell you from working for me for 18 months) is expected to be quantum cut above normal testers. We achieve that not through wishful thinking, but through study and practice. A Satisfice tester is always ready to be challenged about his work".

So here is my progress report for 2007 that you might want to go through. When I wrote the report, (which took me a long time to compile, think, laugh and cry as I remembered each moment of 2007) I understood why I think I am one of the most passionate software tester without excluding the fact that I am living among other passionate testers. I finally feel eligible of what credit I got one year before, this day.

-- Pradeep Soundararajan - http://testertested.blogspot.com - +91-98451-76817 - pradeep.srajan@gmail.com

"Pradeep's first language is not English--his first language appears to be testing." -- Michael Bolton

The most challenging software testing quiz online

This quiz created by me challenges a tester to answer several common and uncommon questions. At the end those who finish the quiz get to know what prize they win. ( which means, there are a lot of prizes to be won)

Last time I announced I would give free books - Lessons Learned in Software Testing and I did give it to those testers who proved to me that they deserved it by working on an exercise I gave them. This time I am keeping it as a secret because those who finish the quiz will get to know their prize when they see their performance and results. I have some questions that are easy, some which are moderate and some that only experts can crack - so whoever you are - you have a challenge.

Update me your score because if your score is more than other testers who have taken this quiz then you have a chance to win the many hundred dollars that I plan to give as a bumper prize. So here is the link to The Most Challenging Software Testing Quiz (I could ever think of creating)

Good luck!

Update: 12th October 1300 IST: The quiz is updated with HTML formatting and looks more great to my eyes. Thanks to Adam Goucher for his suggestions. 3 more very challenging questions are added. So you might want to re-take and check your score. If there is any betterment of your score update me so that you dont miss the grand prize.

Update: 12th October 2345 IST: If you dont see your comment for this post it is because I felt your comment contained some clue about the answers which might distract new people taking the quiz. In case you want to blog about this quiz please make sure you don't give the answers or let the people know the answers or experience as they might lose the excitement and opportunity to learn.


-- Pradeep Soundararajan - http://testertested.blogspot.com - +91-98451-76817 - pradeep.srajan@gmail.com

"Pradeep's first language is not English--his first language appears to be testing." -- Michael Bolton

Tester Tested! coming soon to your city

I offered a public class recently and there were testers from Thought Works, Philips, IBM, McAfee, MarLabs, Mphasis, Mopat Solutions ... (other names that I can't recall) At the end of the session each of them looked thrilled and excited. We had hours of discussion even after the session officially ended and that is a clue to me about the excitement and joy of learning they had.

Now, all my public classes have been in Bangalore but that's not the only destination where there are testers. India is wide spread and I have decided to travel different places, which also helps me take a break by meeting different people and visiting new places.

More than a dozen testers from Chennai, Mumbai, Pune, and Hyderabad have been in touch with me over e-mails and looking at my stats I am sure there are at least more than a hundred testers from each of these places who read my blog regularly. I am sure that each one of you who have been interacting with me also know couple of testers whom you think might be interested to attend such a session.

In case you are interested to have the testing skills workshop in your city, please do get in touch with me by writing an e-mail to pradeep.srajan@gmail.com with subject line "Workshop - ( your city name). I shall share the contacts of other testers from your place who have been in touch with me, we could discuss over e-mail and get the workshop up in your city, too.

Lalit Patil, a tester from Mumbai did organize one such session of mine in FEAST, Indian Institute of Technology a couple of months ago.

This intention of mine to travel different places is not to come back from each city with loads of money but with an intention to benefit testers who are away from the reach of my Bangalore public workshops. So that doesn't mean its free! Based on the number of testers who are interested there would be a cost each has to incur to support my travel and other expenses.

Despite my workshops always have been in Bangalore, so far, I am very happy that there were 4 testers who traveled from far away cities to attend it. One came from Thailand, One was from Hyderabad and the other two were from Chennai.

I dont expect great things to happen after this post and I also wouldn't be too surprised if nothing happens. I am just hopeful that testers from places other than Bangalore would be as interested as my fellow Bangaloreans are.

Hope is an important thing I rely on and so I hope at least there would be at least one other city in India that is as good as Bangalore.


-- Pradeep Soundararajan - http://testertested.blogspot.com - +91-98451-76817 - pradeep.srajan@gmail.com

"Pradeep's first language is not English--his first language appears to be testing." -- Michael Bolton