"Some birds aren't meant to be caged, their feathers are just too bright"- Morgan Freeman, Shawshank Redemption. This blog is from one such bird who couldn't be caged by organizations who mandate scripted software testing. Pradeep Soundararajan welcomes you to this blog and wishes you a good time here and even otherwise.

Thursday, January 28, 2010

Black Viper Testing Technique


The following conversation is a copy paste from LinkedIn's Software Testing & Quality Assurance group in which I write a lot.


Senior Software Engineer - Quality Assurance from somewhere responds:

Never heard about it?I googled the term and found one helpful link. http://www.phadkeassociates.com/index_files/robusttesting.htm but Wiki doesn't have any results for it, as per me its not as concrete as other testing techniques.


and then XXX, PMP, Associate QA Manager from some_organization

Robust testing means the degree to which a software system or component can function correctly in the presence of invalid inputs or stressful environmental conditions

Sr Software QA Engg from elsehwere responds


Is it something like the stability Testing? I never heard of this terminology.


Pradeep Soundararajan : Independent Software Tester with an experience of 7 million and 4 hundred mistakes in testing responds

Same as Black Viper testing.

Friday, January 15, 2010

Test effort estimation: Getting it wrong before getting it right

While the world thinks test estimation is a very tough thing to do, I think, everyone gets test estimation right. The point at which they realize their estimates were wrong is the time they get the estimation right. I wish they corrected themselves. Mostly, it remains unfulfilled.

So, the deal is to communicate the number when you know you are getting it right and buy time to get it right. By "right", I mean, more meaningful than you would have when you provided an estimate even without looking at the product.

I don't know what's wrong in going wrong the first time. Most of us learned to ride a bicycle, someone did it in a day and others took a month. How would you have answered a question, how long would you take to learn to ride a bicycle? Some people might need more time to get out of the fear of falling from it and others need time to get the balance right. It varies and hence cannot be determined before even someone got on to a bicycle?

Wednesday, December 02, 2009

Why testers need to learn to write code that works?

One of the things you thought I don't do often as a tester is - to write code. You are not completely wrong. I immersed myself all these days trying to be a tester who is /mostly/ black-boxish and interacts with the software through GUI. Did you read it as, "A black box tester doesn't need to write code?". Stop reading it that way! Read a sentence the way it is written and not the way you expect someone else to make a mistake that you like them to do.

You shouldn't be surprised to know that in the past I have written little tools, utilities and batch scripts that helped me or a test team I worked with. At the worst case I used to edit those scripts written by others to suit my needs or the mission. No matter how small they were, the value was the key.

Perl has been my favorite (you think I explored others enough, nah) since I first discovered it being used to automate checks in my first job. A couple of weeks back I decided to focus on shaping myself to be a tester who can write code in Perl for automating checks for most kinds of software I test. Irrespective of whether I am hired to do so or not, I'd want to be equipped.

In order to practice stuff that I learn in Perl, I decided to create exercises, puzzles and games for testers. That way I am trying to have more fun learning Perl. Perl itself is fun in its true nature and imagine adding more fun to it.

So wanna check out the puzzle I have for you? Hold on, don't be in a hurry.

Saturday, November 28, 2009

Weekend Testing : 16 : Test and Experience Report

Mission: To find three conditions where Defender wins, Defender loses, and Neither Defender wins nor Attacker Wins for SpeedSim.

Deliverable: Send the combat report of the simulated battle for each of the conditions in a zip file.

Tester: Pradeep Soundararajan
Time: 3:00 PM IST , 28th Nov, 2009

Later there were more missions that were added (bad I didnt pay much attention but was able to recover quickly )

Notes:

# I downloaded the application and asked questions about the version of the file before I installed.
# Having some time, I discovered the existence of an online version of what I downloaded and installed.
# I am spending time trying to learn what the application does. Wondering how I should learn this game.
# Found a tutorial of what this app is all about at : http://www.speedsim.net/index.php?page=tutorial. Quickly brushing through it.
# Working on achieving the mission at 3:20
# At about 3:35, I feel I am close to accomplishing the mission but not sure if there is a trap in there.
# I wonder what a partial win is? For instance in one of the report below I saw a 98% win for Defender ( Can I achieve a 50% win )
# I realize that I am not getting caught by the complexity of so many fields to achieve the mission. Keeping it simple.

Friday, November 13, 2009

Rahul Verma on Fuzzing for software testers : Nov 23, 2009

I think I was stupid to have missed mentioning this tutorial from Rahul Verma on Fuzzing for software testers in my previous post. My apologies to all testers from India for overlooking at our own indigenous talent. Rahul, please forgive me.

Fuzzing is a very interesting topic and I dont want to loose out on attending his session in Bangalore.Have you ever corrupted a file? Have you been curious to see what happens to your system when the database is corrupted? What happens to a live / production server if a file is corrupted? Have you ever experienced a file/data corruption at the customer end and the ripples it caused your organization. I know its very important and thankfully Rahul has focused on it much beyond most of us. If I could better my fuzzing skills, I can extend my competitive advantage.

Once I was a part of a test team whose responsibility was to test multimedia streaming on a Pocket PC. Pesticide Paradox kicked in and our test data was no longer helping us to find problems.

Monday, October 26, 2009

Title 1: Investment plans for software testers. Title 2: Michael Bolton RST training in India

Is it a best practice that a post should have only one title? ;-)


Sharath Byregowda has won the Best Performer award at Mindtree. You know what it means to win the best performer award in an organization that has about 8000+ technical force. According to Mindtree there was a special guest who was invited to give away that award and that special person for them that day was me.

Sharath's manager, Murugan, wanted to make the award ceremony a very special one and surprised Sharath by bringing me in for the award ceremony. A manager so excited about giving away an award of Best Performer of the organization to his subordinate - made me feel wow. While traveling together to Mindtree office, I discovered that Murugan had a good diversity throughout his career and even tried doing business in the United States long ago with his friends. With all that experience, he thought, freedom plays a vital role in testing and hence provided it to Sharath who seeked it. India needs more Murugans. I think they have lot of Sharaths out there.

Freedom with responsibility made Sharath get him the award. This is the second time my student is getting an award at the organization level. Most of you might not know much about Shaham Yusuf but then he won awards for slogging important bugs and an unmatchable record of the highest number of important problems found in Deloitte India.

Monday, October 12, 2009

Testers & Blocks Consulting - Puzzle 2

You haven't yet read Testers & Blocks Consulting - Puzzle 1? You know Testerlock, right?


"Are you Testerlock of Testers & Blocks Consulting?" screamed a voice on the road just when Testerlock was buying some vegetables. Before Testerlock could respond, the young man filled with excitement said, "I have watched you test at a webinar and I loved the way you brought in so many heuristics to your testing approach. I even wrote an e-mail to you a couple of months back".

"And you are..."

"Oh, I am Philip. A senior tester at PepLabs and I really wish I could learn more from you. In fact my whole team would love to learn from you"

"I am glad you are interested at my testing as much as I will be interested to watch your team test"

"We have a problem though. Our manager somehow wouldn't get convinced that we need your training?"

"Really? Do you have some time, let me pay for these vegetables and we can sit around for a coffee"

"Oh, sure"


A few minutes later, Testerlock and Philip were at a Cup-O, a coffee bar in Portland, Oregon, discussing about the problem that Philip raised.



After the first sip of a coffee, "So, you think your manager is a barrier to bring me in, to coach your team?"

Saturday, September 26, 2009

Approaches for interviewing in software testing - Book Kickoff & Launch of Interviews & Jobs portal



On September 1st, 2009, I decided to move away from my paying job to write this book - Approaches for interviewing in software testing. Before my bank sends an SMS "Lost your job?", I am hoping that I will finish this book and find a publisher. ( Also means: If you have any short assignments you can hire me or sponsor me for the book ). So, there you go. Now you know what I have been doing over the last 25 days.

A funny thing you should know - I had been writing another book over the last two years and then realized - writing a book is different from writing a blog or making a technical presentation at a conference. The kind of a book I was writing actually demanded a better writing skill from me that I dont possess right now. So, I have applied to be a participant at a workshop of how to write that kind of a book so that I better at least a little bit. ( let that remain a secret for a while )

Coming over to this book - you must first understand that this isn't just a book but something beyond the book. www.interviewsandjobs.com will serve as a platform to address all queries of testers related to jobs and interviews henceforth and also act as a flag bearer for the book I am writing. Santhosh Tuppad, my student at Practical Hands on Software Testing Training and a cool tester has been helping me a lot in the project.

I hope some of you will be willing to help in writing this book by contributing stories of your interview experience or other ways you will discover if you browse through www.interviewsandjobs.com

When you go to www.interviewsandjobs.com , don't miss out the teaser for the book. The teaser has the first 14 pages of the book and I hope it builds enough curiosity in you and your friends to ask for more and end up buying the book or sending the teaser to your friends through twitter, facebook, orkut or anywhere as you may like.

That's all, here. Go there and enjoy!

Tuesday, August 25, 2009

Testers & Blocks Consulting - Puzzle 1

At 9 AM on Aug 13th, 2008, Testerlock, Principal Consultant of Testers & Blocks Consulting, walks into the lobby of Seven Inc in Whitefield, Bangalore and asks for Peter, the Head of Testing. Testerlock, was supposed to attend a meeting with Peter and his team of Test Managers. There had been some testing problems in Seven Inc that had been causing concerns to top management. So, it was Peter's boss Nick Fry, who hired Testerlock to figure out what's going wrong.

After all security clearances, Testerlock was welcomed to a conference room by Peter where his team of managers, Sasha, Rubin, Maria, Vibeesh, Ratan and Ankit were waiting for the meeting. The conference room was quite big and could even fit 20 people with an oval table in the center and Featherlite chromium hand rest chairs . Testerlock's name was already written in one of the paper clips marking his seating position near the door. Everyone in the room had heard about Testerlock through his articles and published podcasts and interviews. As Testerlock sat in his seat introducing himself and shaking hand with the team, he smelled the coffee aroma and while putting his laptop bag down on the table, he asked, "Ah! Can I have a Nescafe too?" and that put Peter's team in surprise about Testerlock's ability to identify Nescafe aroma from other available ones.

The meeting started with Peter displaying the agenda planned and discussing each point with a little bit more detail than an e-mail communication that happened a week back. When Peter stopped, Sasha took over.

While these things were happening Peter was getting confused if Testerlock was listening to all that because Testerlock was constantly writing something on his Moleskine. Testerlock had to several times nod to acknowledge what Peter had said. Nodding has been a practiced way in India to acknowledge having heard something from the other.

Sasha, a Test Manager with Seven for about seven years. That's right, 7 years. Sasha had been a star performer at Seven's Texas office and she looked like one and spoke like one, too. Sasha then started explaining her team's challenges of unable to achieve 100% testing and test case being complex, bugs not being fixed and so on....

Testerlock had just one word to say, "Interesting".

From Sasha to Ankit, and from Ankit to Ratan the problems the team faced were...."productivity of testers, tester developer relationship, lack of good process, best practices not working, budget is too low for good testing to be done, test automation not yielding ROI..." and yet again Testerlock had to say one word, "Interesting" and kept writing a lot of notes on Moleskine.

When it moved from Ratan to Vibeesh and Vibeesh was explaining the challenges his team faced, Testerlock interrupted the meeting asking for directions to a rest room. Before he left for the rest room, Testerlock asked the team to continue sharing the problems faced by them.

When he walked into the room again, he had a kind of style in his walk that meant that he knew what the problem was. 

By then it had shifted from Vibeesh to Maria, and then new set of problems being listed.  By then Testerlock had stopped making notes and was sitting and listening to what Maria was saying.

It was about 11:45 AM when Maria completed flushing her list of problems. Peter was excited to ask Testerlock a question and without hesitating much, he asked, "So, Mr Testerlock, what do you think the actual problem is?"

This time, Testerlock stood up and gave a one word answer. It wasn't the word, "Interesting" but the answer to the question Peter asked.

If you were Testerlock, what would your answer be? ( Your answer need not be one word but it could be. If your answer was already listed by other people who commented think about a different answer or expand on the latter. Maybe you might hit a better one )