Are Experienced Software Testers Testing their own CV / Profile / Resume?

Re-written the article on April 20, 2009 & Previous version also available at the bottom

For the question : Are Software Testers Testing their own CV / Profile / Resume?, my answer would be - most of them don't.

What would you think about a tester who hasn't tested whatever he has developed? I think the same way you think about them - they don't know testing or its value.

Over these years, I must have looked into about thousand three hundred testers profiles and only very few of them caught my attention. One of them was my own :)

Need and value of testing your own resume

I have been practicing writing and this blog is an evidence of the same. I think our public writing demonstrates how effectively we can work. For instance, if my resume looks bad then would anyone believe me that I write good bug reports? If they believe that I'd write good bug reports when my resume sucks then what do you think about their communication skills?

I got coached by Mr Ravi Joshi of Bangalore on the aspects of writing a good resume. I probably practiced it enough to match his own writing and then trying to surpass it. All he did was to help me learn how to test my own resume.

I discovered that testing a resume was so similar to testing a software. For instance, our resume is full of claims that we have made. If we dont test for the claims we have made and what we can actually deliver, it costs us an opportunity to get an offer letter.

An example from my life experience is: There was a person who mentioned about Apache Web Server as one of the technologies he had worked on. On questioning him about it, he said, "Sir, it was running in the back end and I used to turn it off and on whenever a crash occurs". Now, is that sufficient to say, "I know Apache Web Server"?

I want you to let me know about it.

Career Objective

Also, most of them steal the Career Objective section and that indicates the person does not have his own great ambitions in life or a vision statement. It is important for anyone to write their own career objective. If you have a typical career objective, "I am looking forward to work in an organization that challenges my abilities and potential", no one would be interested at that.

Here is another interesting thing: A career objective is a long term vision but what most people end up writing is - I need a job to show my potential - which is not a career objective but your immediate objective in life.

At some point of my career, I have even removed that section and yet people kept calling me for interviews. Doesn't it help you understand that people are not calling you based on it because they are already bored reading more or less same stuff?


Projects

This is a very interesting part. Recently, I was interviewing a tester who had a 7 page resume for a 2 year experience. He had detailed out his project on his resume and that's a bad idea. I helped him understand that it was a bad idea and he went ahead arguing with me that he had to mention all details. A question that I asked him was, "How many pages should Hon Prime Minister Manmohan Singh have?"

I hope you understand why I asked him that question and also hope you won't make the mistake. You must note that people who might be looking into your profile might already know about the product or project and don't need super fine details of your project. You can make it to one or two sentences. This gives you a tactical advantage in interviews if you were to explain your project.

Your contribution

It is another common bias to show whatever little stuff you did in the organization as a great one. Again, people are tired of listening to such stuff. You might want to consider elaborating an experience or the challenges you faced and how you fared in it.

For example: When I was a rookie Test Manager, people reporting to me found it hard to digest the fact that I was much younger than them. I had to fight through their ego battle and yet get work done from them. I learnt a lot about managing people, especially when they dont want to listen to you.

Lessons learnt

You could consider jotting down some very quick points of the lessons you learnt from each of the project you worked and that could be an attractive thing for the interviewer. You may consider listing your failures as well although you think listing your failure could cause you lose an opportunity to get an offer. Come on, the whole world understands that every human is fallible and everyone has failed in their life more than a dozen times.

Documentation Guidelines & Crispness

You wont be given a job because your profile looks amazing and it is a booklet of 30 pages of your achievements. So, it means you have to work in an interview to crack the puzzle of getting a job offer from them.

I received one of the worst resume from a software tester who mentioned that he has excellent documentation skills and the word documentation spelling was incorrect. Are you dumb to call him for an interview?

You do not need to search for resume template and fill in because that is a clerical work and I hope you don't want to be a clerk. Clerical type software testers get clerical pay and they are happy with it as well.

Extras and tactical advantage

You could impress the interviewers by testing a web application or an open source project and attaching your test report with it. This gives you a tactical advantage over all other people attending interviews as the interviewers get to see how you can actually test, how you report problems, how you investigate problems, how you can prepare a test report, how good is your writing skills and all that.

Peer Review of your Resume

You might be knowing the value of peer reviews in software engineering. How about bringing that to resume writing? Ask any of your friend's or peers to review your profile and spot problems. As you are the developer, it is likely that you will make mistakes and you might be blind at spotting them.

Progress Report Reference:

I have been compiling my Progress Reports over the last two years and I want you to have a look at it. Search for Progress Report of Pradeep Soundararajan and you will find the PDF files.

Interview skills

This one is quite famous : Yeah this one : The (bad) state of software testing interviews in India

If you are interested in watching my presentation of the same, here is the link to the video

Old version of the same article
( and there are some good points there as well )

So think about these points and also read what I wrote long back when my own English wasn't as good as how it might be now:

Old version of the same article:


Hi Reader,

I would have spent at least 300 hours by now, in this life time, helping out my friends, modifying their CV/Resume. It was interesting initially, especially when I had learnt the art of writing a good CV for myself. Thanks to Ravi Joshi, who spent his valuable time with me, teaching me "The art of writing a wonderful CV" .

I dare to share my learning and would want to provide a template to those sending me CV's to modify. Become an expert by experimenting with your own CV .. after reading this.

__ Are you testing your CV ? __

Trust me, I have modified CV's for developers too but a majority of the CV's I have touched is of a Tester.

Some common stupid mistake I and you make in the CV V/s How better can things be -

Junk Objective - To secure a challenging position in a well established firm and want to develop further as a tester OR Looking for an opportunity that can extract my potential in terms of technical and management OR Seeking a position in your valuable organization to grow in my career.

Clear Objective - Being a passionate Tester for x years and having won ... credits ... , I am looking for an opportunity to augment my career further, since I feel a new environment could make me learn things better and can work towards contributing at higher levels OR Having proved the ability to learn and a developed interest towards Test Engineering, I want to take my career to a stage of delivering high customer satisfaction by joining the services industry yet bringing in the product based company's expertise OR I am a self proclaimed passionate Tester. I want to put myslef to test by taking up challenges that your organization is currently offering and feel satisfied when the work quality meets the claim.

Gyaan -

1. Never copy someone's objective, which is the most stupid thing any person can do.
2. Frame your own objective, what it costs is 100 MIPS for your brain.
3. Your objective should say a) Who you are ? b) What are your skills c) Why are you looking for a job d) What can you bring to their table OR e) What is the value addition if a company hires you ?
4. If you have prepared for GRE_TOEFL like exams but could not get through and the by product is - you become a Indo-US English guy. What it means is, your english is neither as bad as most of the Indian's english nor as good as the true American English. Such people tend to use complicated words. If you do so, the person reading your objective may not even understand it. ( It is truth, if you want to say "No Pradeep, you are wrong" , you better say "Hey Dude, you suck and your english is wrotten kinda stuff", I shall understand the by product you posses.)
Junk Project Explanation -
Bluetooth Audio Product Testing - Bluetooth is a wireless standard given by SIG. It operates in 2.4 GHz ISM band. Bluetooth audio product is to listen audio or music over bleutooth wireless product. Testing is a major phase in Bluetooth Audio products and invlves audio testing abd bluetooth testing.
1. What the hell ? Why should I write about bluetooth technology in describing about the product ?.. ( 10 % of the resumes I have modified, explained the technology of the product ).
2. Although Mircrosoft has given a spell check, most of them do not use it. When you open today's Indian Tester resume, you will see a lot of Red and Green colours. Simple, they think Microsoft is recognizing their resume and by default underlining it to make it colourful.
3. Indents and Formatting.. This was the toughest thing I ever handled. I wonder how people write word documents wherein I try to modify its format but returns to the same when I press and Enter or Backspace at some points.
4. Bold is not beautiful - Janta does not know what to make Bold and what to not. They feel every one word out of 20 should be bold. Italics, at their own will. They draft the CV and see they have not italicised some words and they start doing it.
Let me try to re frame the above project explanation -
Bluetooth Audio Product Testing - A wireless audio solution for people who would want to listen music on the move without getting entangled with the headphone wires. This project was intended to achieve CD quality music while streaming audio over Bluetooth. A broad classification of the testing challenges would be in measuring the scientific quality parameters of the audio, loss of quality in comparision to wired headphones and testing the user friendliness of the whole product apart from testing the product for battery life and other MMI based testing.
Isn't that giving a fantastic view to the person looking at your CV of what project it is and what you could have done in it ?
Client/Customer Name - Everyone of us are happy to mention that we worked for Microsoft, Google, Yahoo, Adobe, Cisco ... not directly but they being the client/customer of the product you were working for.
Ethically, it isnt good. You think a company would hire you just because you worked for the above companies ? What you do not know is you are revealing your customer info to the person looking at your CV.
What if your CV reaches the competitor of your current place of work ?The person interviewing you would be happy and hire you if you say him "Sorry, I cant tell the customer info" , if he asks such a question.
Unwanted Info -What we all should learn is CV/Resume has no standard format and if you can form your resume. You would be amazed to hear that one guy prepared a CV in flash and song a sang ... for it. Can you believe there were companies in queue to hire him ? Want to know who is he ?
Right click and open to CHECK THIS OUT !
Common sense questions you should ask yourself -
When you cannot draft a good CV without spelling mistakes, formatting mistakes, meaningful sentences... Why should I hire you ?
1. You proved you dont have good documentation skills.
2. You proved you will be unable to report a bug you find with non meaningful sentences writing being your flair.Complicated english words, Will the customer understand ? ( All customers are not smart )
3. Client/Customer name... so will you let know my customer details when you look for a job outside my company if I hire you ?Overall, all your claims look false if your CV negates your claims of being a good tester.
4. Does anyone mention Microsoft Excel as a tool they know ? Trust me if a tester knows the full features of MS Excel he can create more wonders. Some secrets better reamin closed unless it reaches people like me who dare to share.
5. False info - We Indians like mentioning lots of tools in our resume to get job. We are least bothered to check with ourselves whether we really know those tools in depth to take up an interview.
6. Did you know that the time required to hire someone will come down by 50% if good , true CV's are prepared by you all ?

"The art of writing good CV should come from the heart"

Testing like Osama

Hi Reader,

Well, I did want to mean "Disastrous Testing" when I wrote "Testing like Osama", sorry if you could not grasp it. Its perhaps been the longest time interval between two posts ( just 10 days though ) because of me doing some interesting testing stuff @ work.

In this post, I would want to share one of the shocking experience I have had while observing a Tester at work

_ Testing like Osama _

It was hard to digest lot of work, sometime back in one of the companies I have worked for. I thought of easing myself sitting with my colleagues to observe the way they work. Seriously, I did want to learn something from them and I did, but ...

Mr A was a Test Tool Developer/Tester and I sat beside him for a while to observe his way/style of work. ( of course, after seeking his permission )

He kept on executing the cases as a focused tester . It was time I had seen enough of his style and was about to leave..... something caught my attention and I still cant digest the shock I had that day.

He was testing a mobile phone's multimedia feature and one such feature is to download an mp3 song from the server and play it on the phone.

What he did ?

He did not know the settings to be made on the mobile phone in order to connect to the server and hence downloaded a song from his PC via USB and was playing the mp3 file in order to execute that case.

My surprise did not stop there ...

He played the entire song and by all manual mistakes he marked the next case in the list as Pass.

Wow ! He read a case, executed someother case and declared a "Pass" for some other case.

This is a classic example of destroying the quality of the product and I am sure I can never come across such a worst scenario of Testing and probably missing out 3 bugs at a time for every test case executed.

When I tried to make him realize his mistake by letting him know what he had done ... he said .. "Dude, relax, go back to your place" ... "This test case execution has come to me because you and the other guy were unable to complete the test cases in the given time".

What I learnt seeing that ?

• If you do not know how to test a case, do not find a work around for that.
• If you do not have the energy to test something, at least at that point of time, take a break and ensure you come back only when you can deliver better quality of work.
• If you are unable to execute all the cases in the given time, do not manipulate test reports/data.
• It could be possible that your manager is disappointed that you did not execute some cases because you ran out of time but ensure every test case you have tested does ensure the product's quality.
• Managers do not look at people who have taken strain to execute each test case with care and keep appreciating the ones who completed the test cases on time, without knowing they have done some wonders like Mr A.
• Test cases executed by one should and must be verified by someone else too before making a major release to a client/customer.
• Putting pressure on Testers, without motivating them will result in missing 3 bugs for every test case executed.
• Mistakes can happen, it is better to select cases randomly and re-execute it before we give our individual test reports.
• Managers, do not estimate the time that needs to be go in to test and produce a quality

I recently heard a shocking news from the same person when he called me up and told "Hey dude, I have been promoted"...

"Shit, for what ?" ... I was so disappointed by that news that I cried. There were other testers in my team who were worth a promotion. What's going wrong in this industry ? Why is all this happening ? Will things change or should we too change the way the industry likes us to be ?

I am clear that the day I am in a position to command, I shall spend time with Testers ... motivating them , making them realize the importance of a test case and would hire 2 extra testers at the cost of my salary to ensure Testers get time to meet quality standards.

Sorry if I have got emotional, as a passionate Tester, I am unable to bear the pain after seeing people not passionate about testing and yet continuing with testing.

__End of _ Testing like Osama __

Trust me, I feel Osama bin Laden has some good testing skills. When he did architect the attack on WTC .. he took into account the fuel on the plane and the heat needed to bring down the building by melting the TOR steel. He is a Civil Engineer.. hope you know that ?

If you are a good Tester, you learn from Osama too ... if not even Kem Caner, James Bach , Jerry Weinberg nor Tester Tested can make you learn.

"Firing such testers is a golden contribution to Testing community"

Regards,

Pradeep Soundararajan
pradeep.srajan@gmail.com

Disclaimer : This post is to let out my personal fury against the incident I witnessed, since I feel I am passionate about testing and I respect Testing.There is no confidential info I have let out here and I am not holding any company/organization responsible for anything that has happened. I should also thank that incident, since after that I am taking utmost care to ensure I have executed the right case and I am marking the result against the same. To learn testing books are not the only source, roam around the world.. when you return home you would be a better tester. I wish someday I write "Mr A has realized his mistake and today is a competent passionate tester".

Programmer Tester V/s Non Programmer Tester

Hi Reader,

It has been long time since I have been thinking about something which I am sharing with you here, after I got an interim answer . It is a conflicting situation every tester passes through at some stage or the another. I have to warn you this early of the post that perceptions may differ and experiences vary from one person to another.

__ Programmer Tester V/s Non Programmer Tester __

Yes, I was wondering as a Tester should I spend some time learning programming or live a life concentrating only on Testing and nothing other than that. Its a tough call for any tester but more than 90% of the Testers I have seen learn programming after this kind of confusion coming up. The rest 10% could be split in categories like - unable to learn programming - feeling programming is boring - no passion for either testing or programming - feeling programming is a brainy job - happy with whatever job in hand ... To be frank, I too fall under this 10% category as of today.

What happens when a Tester learns programming ?

1. If programming is new to him, he may find more pleasure in development than testing since developers say "its more joy to make it work than to say it did not work".
2. If a tester gets skilled in programming his manager may move him to development since for the management they want to put you in a role where you can make more money for them, when you give a super duper hike to a tester to make him a developer, most of us would take it up.
3. A tester may look out for development jobs since it is better to join a new place as a developer than jumping from testing to development in the same company.
4. Exception - He may still continue in testing and start thinking of automating something that was making him painful to test a few scenarios/cases , helping co-testers.

What happens when a Tester doesn't learn programming ?

1. Simple, he makes an attempt to learn programming.
2. At some stage starts getting an inferiority complex and does some course or any certification that can suffice his complex-ion.
3. Exception - concentrates more on testing concepts and wants to become the best black/box or system tester.
4. Exception - utilizes the time he would have spent on learning programming on learning new protocols, doing some research work on his own....
5. Most common - Would want to move to management ASAP to avoid comparison of a developed tester.

Introducing you to the best automation tool you could ever see ...

"Pradeep, you were talking about tester learning programming and suddenly you are jumping to something else. Are you sure you want to talk about that tool at this point?"

Yes, I am 100% sure, there is a relation between the tool and the topic I have been discussing above.

The pic you are seeing in this post is the logo of a tool, a company called SPB software house in Russia developed. They have developed a fantastico tool that helps the non programmer Tester to do an automation of test cases ( of course without any programming )

How can that happen ?

Yes, it is not a miracle. What the Test Suite 2.0 does is to sit on your Pocket PC and note down what you do and ape you ( follow you ). That doesn't mean if you by mistake power of the Pocket PC , it will also ape you. You should be smart enough in telling it what you want it to do by doing it manually.

How it works ?

It kicks its action recorder once you ask it to do so and then notes down your actions. Example - you open an application give some input and close the application, it forms one test case.

You can see a product demo and read its documentation if you are interested ( if not, Close this internet explorer window you have opened , dont worry, you can open it again)

Now the question comes up - If such products come up in the future, do Testers need to learn programming ?

__ End of __Programmer Tester V/s Non Programmer Tester__

"In future Managers can track your performance, running this tool. Beware tools are getting smart enough to talk to the girl in the next cubicle"

Regards,

Pradeep Soundararajan

pradeep.srajan@gmail.com

Disclaimer : I am not a part of the organization that developed that tool nor am I into advertising it nor have I got any money from them to write about their tool. As a tester I felt its a tool worth its space in my blog. Everyone can/should learn programming based on their own interest and not just becuase the tester near you is doing it.

If you are a regular reader of my blog, go through this link.

How to prepare before a war (bug hunt) ?

Hi Reader,

This is one good article ( according to me and my perspective) for young testers of how to proceed when you are on the verge of starting testing. This article could also be helpful to those who have to start testing on a new product and new technology.

Well, I have been mentioning the word *this* and I am pretty sure, you would want to have a local copy of it right.

You just need to right click and open How to prepare for a bug hunt? - article available in Stickyminds.

Thanks and Regards,

Pradeep Soundararajan
pradeep.srajan@gmail.com

How do you explain testing to your children ?

Hi Reader,

Many active children we have seen, ask a lot of questions and sometimes we are left in a state where we are unable to give an answer for a question. If your son/daugther is an active child then try explaining testing to them, they shall give you a new dimension of testing. If you don't have a child yet , don't try for one without marriage but ensure you are active to have an active offspring.

__ How do you explain testing to your children ? __

Child : Dad/Mom, what do you do at work ?

D/M : I Test products, my dear child.

Child : What is Testing ?

D/M : Well, Testing is playing with a product.

Child : So have I done Testing too ? Will I get a job in your company.

D/M : Partially true but you are not a tester.

Child : I play well , you can ask my friends !

D/M : Ha ha ! No my dear child, Testing is not about playing with a product alone. It is more than that.

Child : I am not understanding, can you explain it in simple words ?

D/M : Ok, Let me take an example... If I give you a toy robot , what will you do ?

Child : I shall play with it.

D/M : Ok, can you explain how you will play with it ?

Child : Well, I shall move the hands, legs , rotate the head , make the robot to fight against another toy....

D/M : Well, given a toy robot, I would do the same but I do it better than you.

Child : How can you play with the toy robot better than me ?

D/M : I shall plan "How to Play ?" , "Write a document of various ways I can play with it" , "Play with it" and "Note down what I see".

Child : Why should you do all that, it isn't that difficult to play with a toy robot.

D/M : Good ! Now say you and I play with two different toy robot and we both notice that when we try to rotate the head of the robot , the head part breaks from the body. What will you do ?

Child : I would cry , what would you do ?

D/M : I would take steps to ensure no more children cry.

Child : How can you do that, would you buy them a new one ?

D/M : Dear, you have started to learn Testing ... I would take another sample toy, rotate the head slowly, measure the point/angle at which the head breaks, call up the company and inform them my observation.

Child : Are you seriously playing with the toy ?

D/M : Yes, what you call as a "serious play", we elders call it "Testing".

Child : Wow ! Will I be a Tester if I do as what you do ?

D/M : Yes, 100% but do you want to become a Good Tester ?

Child : I want to become gooooooooooood tester.

D/M : Then you must start playing seriously with whatever you see, use or feel and have to read a lot of books, teach your friends, write your own articles...

Child : Except of reading books, I can do anything else.

D/M : No Dear, you need not real all books, James Bach , a Test Expert I know, writes about Testing in simple words. You can use his book/articles as a bible.

Child : Dad , We are Hindu's , why do we refer to bible ?

D/M : Bhagvad Gita, Quran or Bible all tell good things and we should not block ourselves in reading any of those.

Child : OK, Let me test the goodness in all those three books.

D/M : I am proud of you , hope you become a better Tester than your Dad/Mom.

Child : Can I have your cell phone for a moment ?

D/M : May I know why ?

Child : I want to call up Bill Gates ?

D/M : ???????

Child : Well yesterday I was playing a game on our PC and whenever I used to keep the mouse pressed for a while to keep shooting the PC rebooted.

D/M : Oh my God ! This guy/girl is testing my patience :(.

___ End of __ How do you explain testing to your children ? __

"The child labour act : 2006 : says 'Parents who make their son/daughter a Tester at young age will have to face punishment on the charges of making their children smarter than others in the country"

Regards,
Pradeep Soundararajan
pradeep.srajan@gmail.com

Disclaimer : The above post is my own imagination and it is an effort to talk about testing in a simpler fashion that I can potray and not to affect any person or his business. The law mentioned above is the law that is presently pevailing in Mars and does not hold for people planning to protest against the law in this Earth.

Prepaid bugs !

Hi Reader,

Prepaid bugs ? "Pradeep do people pay in advance to see a bug?"

Yes, indeed, you too have been a part of it, if you are from India. For other country chaps, alert your mobile service provider...

Did you get any clue ?

__ Prepaid bugs __

We had 2 hours break in a training that I was attending today and I got a chance to interact with a guy. Can there be a chance where I have not talked about testing to anyone ?
Hardly any...

I started off introducing myself and so did he and then we started talking about testing.

He had worked with Tata Teleservices earlier and I happened to ask him
"What was the worst phase of your career with Tata Teleservices?" and the story goes...

Sometime back the prepaid billing system which is deployed in iN ( Intelligent Network ) went for a toss for almost 3 days. This is a well reputed company and how could they have allowed such a thing to happen. You should be aware that there are certain things that goes beyond our control and so it did happen.

The team there started to diagonize the problem and after a day they found out that ... the few servers that interacted with a Avaya soft switch where not communicating with the soft switch as per the design.

As per his explanation the pre-paid billing servers communicate with the Avaya soft switch in a Time Division Multiplexing manner but they found that the Avaya soft switch was unable to take the load as all the servers were trying to ping the switch at the same time and that lead to the whole problem.

Now there are a few questions that had to be answered ...

1) How did this problem occur when it was running fine for a period of 1-2 years ?

Ans: Personnel from Tata Teleservices contacted the Avaya support team and their query being a priority one was routed to the France R&D team and then Avaya consulted their sub-contractors who also worked on the same product. Finally it was identified that it was a hardware failure which lead to mismatch of time slots to ping the switch.

2) What is the solution ?

Ans: A new hardware had to be deployed replacing the faulty one.

3) Why did it further take 2 days to get it fixed ?

Ans: The software/driver/hardware was not available in India at that point of time and someone was sent to Singapore , he then purchased and after his return they fixed it.

4) Wasn't there any back up , come on I don't believe this ? ( This was my question too )

Ans: Yes there was but it took a lot of time to move a customer info from one server to another and that itself would take a lot of time and in the mean time the problem can be fixed and also it would take more time to move from one iN to another and then retrieve it back.

Lessons learnt as a Tester -

I consider this a good learning for me and hence here is what my perception of it ...

1) Ideally Avaya should have got the hardware which failed at Tata Teleservice iN and should put that as a tool to be used for Load Testing for the soft switch they are working on.

2) With an organization outsourcing a job and the outsourced guy again outsourcing to someone and the chain goes on ... will lead to testing becoming more complex at the blackbox/system test level.

3) If it is a real-time or critical application that are installed on real-time networks, there is nothing wrong for a Tester to suggest the organization to buy back up hardware or also maintain a list of nearest Vendor/Retailer list for the products they may be in need.

4) For such a scenario, had the France Testing team asked to reproduce the issue, it would have been the toughest phase of their Testing career and my dear Testers, when you are unable to reproduce something after exhausting your tries, time to burn your hardware and then making a last try.

5) Hardware Testers should take such examples and do a research to find out ways to indicate a hardware failure. Of course there are LED displays for some systems but remember the above problem occured with something called intelligent Network.

6) Testers should ideally look around the world and that is the only way they can progress, you maybe doing some testing on some applications and the above incident may not be of any help to you but if you think you can learn a lot.

__ End of _ Prepaid Bug ! __

"Thinking and Laughing is free of cost in this world , either you think or laugh at yourself"

Regards,

Pradeep Soundararajan

pradeep.srajan@gmail.com

Disclaimer : This post is not to affect any business of Tata Teleservices or Avaya and is an effort to learn from what has happened. Also I take no responsibility if the above incident was unreal and this post is in existance as per what the person I met narrated to me. He too maynot be responsible if he had lied since it is time to appreciate his imagination. No organization I am working with control my thoughts and this post is not from a PC that an organization has provided it to me for official usage. My current ip 192.168.1.100 which belongs to BSNL broadband connection :D

Where can you find the best testers of the world ?

Hi Reader,

This time it is going to be real serious post, no fun and no wild stuff but yet I am sure an inspiring and informative one.

The channel I watch to improve my testing skills are National Geographic and Discovery because it teaches a lot a testing through its Flight Crash Investigations. Whenever a flight crashes....

__ Where can you find the best testers of the world ? __

A Test Pilot is put to test !

Let me take an example of a flight crash which I felt interesting to talk about testing and then tell you why Flight Test Pilots are a cut above all of us doing so called Testing.

Aeroflot Russian International Airlines - Airbus A310-304 crashed on 23rd March 1994 which was heading from Moscow to Hongkong

You can read the story of crash here but let me explain to you after that how the investigation was/is done ( moreover , why you need to be a good tester if you want to be there investigating )

The Analysis -

1. The Analysis starts with an organization like National Transportation Safety Board ( NTSB ) collecting each and every part of the plane debris and also listening and reading the data collected by the Flight Data Recorder ( Black Box ).
2. Personnel from NTSB, in the above flight crash consulted a Test Pilot of Airbus to make a further analysis of why the Autopilot feature failed when a manual over-ride was forced on the so called most sophisticated On board computer auto pilot system.
3. The Test Pilot and NTSB personnel listened to the audio conversations to find that the Pilot had taken his children to cockpit, let them to fly it for sometime while the auto pilot was still taking control of the plane, of course they were shocked but still why should it crash ?

What did that Test Pilot do ?

1. He carefully noted down the Flight path, distance, speed, weather conditions, changes that the pilot did to the flight controls, auto pilot status, instrumentation details...
2. He documented his observations and got it verified with NTSB personnel.
3. He sat on an Airbus A310 simulator and did the same as the pilots from take off to 5 mins before the crash and also carefully did the same actions as the children on the plane's cockpit did.

What did he notice ?

1. He noticed that when the child tried to over-ride the auto pilot system , the auto pilot failed and more importantly without an indication that it had failed.
2. He also noticed that before the auto pilot cut off its control , there were some false trajectory projected on the pilot computer's display which further confused the pilot in the real time 2 mins before the crash actually happened.

What did this lead to ?

1. This lead to some major design changes and an intensive Testing was taken up to ensure there are no more accidents since that crash killed all 75 on-board.
2. This also lead the companies/certifying communities to release a plane only after testing it as completely as possible.
3. This lead me to realize that the Test Pilots are the best Testers this world has.

What should you learn from this ? ( if at all you want to learn )

1. Be it a flight crash or a system crash, investigate it properly.
2. Take time from your manager if you want to dig out to find what exactly is the problem.
3. Always try if there is a possibility of adding a data logger for the system you are working and be careful and ensure that atleast the Datalogger is tested properly. ( make it simple yet effective)
4. Be sure what changes are needed after you notice a crash and wants to get it fixed.

Note : There was a comment in my previous post that "No customer would do wild things with the product when every company releases a user manual from Selva" , now Selva ... for the above incident , dont you think the wild test case would be "Giving the flight control to children and check what is happening in the simulator atleast" would be the most useful wild case ? Also when Taliban hit the Twin Towers with fast moving plane, didnt you see it as a good wild test case to test building strength ?

__ Where can you find the best testers of the world ? __

For the question "Where can you find the best testers of the world ?" the answer is ....Within you my dear readers...

... if you have a narrow vision, you cannot become a best tester whereas you can become one among the passenger who didn't survive. Ask yourself whether you want be inside a crashing plane our outside it , investigating the missing test case.

"Narrow minded mediocre testers, show you the broadest way to hell"

Regards,

Pradeep Soundararajan

pradeep.srajan@gmail.com

Wild Wild Test !

Hi Reader,

Welcome to wildlife of Testing! Does it really exist?

Well in some interviews, a tester is tested to answer some wild questions but according to me those are really thought provoking. Whenever I am free I think of testing something with a wild touch. No, I am not trying to bring out a new testing concept “Wild Test” but just giving that name assuming it suits to what I have in mind.

__ Wild Wild Test __

Coffee Maker – One of my friends who went through Microsoft interview process in Bangalore was asked a question “Tell us one unique (wild) case that you will write to test a coffee maker.

Wild Test case for testing a Coffee Maker – Instead of pouring water for decoction, pour coffee itself and it would be interesting to watch what comes out and the test completes by tasting the outcome.


Pen – Some person had asked me about this after reading my Tester Tested in interview.

Wild Test case for testing a Pen – If fountain pen, fill it with blood and try writing a love letter. (Although this may look wild, one of my friend experimented it some years back and he said the pen didn’t write, although he didn’t get the girl, I got a test case from him and I am sure you must also have come across such love maniacs...)

Alternatively try catching some rodent near your house and try killing it with the pen you have in hand. Don’t you think this is a good wild test case? You should have by now noticed that many people have got hurt from pens since when someone strike you with a sharp pointed pen, it hurts a lot, you shall then agree that a pen is mightier than a sword.

Mosquito Repellent – This could be a futuristic interview question and it did look interesting one for me.

Wild Test case for testing a Mosquito Repellent –Leaving the mosquito repellent ON for a few days in a room where there are dead mosquitoes. Are you surprised why this test case is anyway valid?
This test case will ensure that a mosquito is repelled and its body is not burnt or affected by any means. (Too wild isn’t it? zzzzzzzzz)

Microwave Owen – Some truth is going to come out here…

Wild test case for testing Microwave Owen –Try putting in a pressure cooker, which contains rice, and water that needs to be cooked into the Microwave Owen. Are you surprised why I may be talking silly? You need not actually since when one of my seniors my previous company made a first trip to US, did this and trust me; today he is cognizant of all products.
Subjecting the Microwave Owen to an Ultra wave/sonic test while a Microwave is functioning.

Washing Machine – Out of my own personal experience…

Wild test case for testing Washing Machine –Put some coins in your shirt and trouser pockets and allow them for a gentle wash in your own washing machine. This will prove a design fault which is the 1 Rupee Indian coin blocks the water outlet and the whole washing machine should be dismantled sometimes to remove it and bring it to normal functionality. Trust me, I gifted the so-called best washing machine for my mom and I am talking about the same one.

Note – Most of the above are true and as a tester when I witnessed such outcomes and heard such outcomes from people using the product in a wild way added another dimension in the testing I do.

Now for some testing gyaan for you –

As a Tester of a product, always think there is a wild animal that is going to use the product you are testing and ensure to a certain extent that the wild animal is not affected physically by using it in its own way.

As a Tester try to imagine some out of the box scenarios that may or may not occur in the future and moreover think futuristic while writing test cases, its your lead or manager headache to remove the test case but you write it…

As a Tester learn and implement subjective testing, means – ask varied kind/class of people to use the product and see how and what for they use it, without telling them what the product is. (I too know what usability testing is, don’t confuse yourself, subjective testing is something different)

__ Wild Wild Test ! __

“The wildest Tester India should be proud of is Lalu Ji, he spits pan over every mic ”

Regards,

Pradeep Soundararajan

Pradeep.srajan@gmail.com

Disclaimer: This is my perception and my own views and does not reflect anyone’s but surely some points are inspired outcomes. You maybe having a more wilder test case for above products and I would appreciate if you could jot it down for your own progress.

Manual Testing - no more a shit job !

Hi Reader,

Oops , I chose a very controversial topic of whether Manual Testing is a brainy job or a shit job and fortunately or unfortunately as you have started reading this stuff, I reccomend you to go through it completely. ( later think on it if possible )

Note : This post is targetted to 0-3 years of experience readers who still remain naive. Others, this maybe the one you wanted to speak out.

There is a misconception about Manual Testing and as a passionate Tester, here is my effort to make it clear. After reading this if you disagree with me , send me your CV, I shall look for an Automation Testing job for you.

__ Manual Testing no more a shit job ! __

Automation has its own merits and de-merits and so does Manual Testing but people are partially blind and look into De-merits alone. Isn't it a responsiblity of we people who have been into Manual Testing to show them "Its half glass full and not half glass empty alone".

Moreover, you cannot apply automation everywhere ... most of you must be dealing with software that runs on a PC or a similar platform but you should be aware that there are a zillion number of products we use in our daily lives which are not software and also don't run on a PC.

If you look at the sky from the well , you will be able to measure the diameter of sky, count the number of stars in the night and also see the shining sun for a few minutes in the 12 hours that it is available. Hope this post acts as a rope hanging in the well through which you shall climb and ..... ( don't look back at the well )

As I mentioned there are a zillion ( just a big number I cant think of ) products that cannot be automated and I am sure if you are testing something, despite a tool doing it, you are hired because it needs a manual effort. Loadrunner , Winrunner , QTP , Silk , Cotton , Wool .. whatever maybe, it still needs _____ ( fill your name , spelling mistakes are permitted )


What a tool cant do , which you can -

1. A Tool can have limited intelligence and does execute and report whatever it is programmed to and I am sure the tool will have more limitations than you.
2. A Tool is not worried about the product it is Testing but I am sure, you are, worried since you want to progress as a Tester.
3. A Tool doesn't care about its appraisal but I am sure most of us do and we perform or outperform.
4. A Tool put to work overnight gives you sleep but if it failed midway on a Thursday night, you miss your girlfriend the same weekend.
5. A Tool is purchased and can be used illegaly too, can you be exploited illegaly ?
6. A Tool is thrown away if a different project comes up and a new tool is purchased based on requirements, Are you thrown out because a project got over ?

Well the above points are made in order to make the Manual Tester realize that they are an important element for an organization when compared to a tool.

Now for some more gyaan ...

Why is Manual Testing a brainy job ? ( You V/s Tool )

1. Assume you are Manually Testing a product and parallely an automation framework is executing the same cases as yours , can you tell me who will report the most number of bugs ? can you also tell me who will be able to validate/investigate/reproduce/create new test cases after one cycle of testing. Is it going to be you or the tool. The tool may overtake you in finishing the test cases but tell your manager you are a tortoise and not hare.
2. You know more about testing than the tool , isnt it true ? then who is a better tester , you or the tool ? Tool is identified by its release number and you by your skills. ( This point should ideally hit those testers who worship tools and ill-treat those who Manually Test )
3. A tool can always replace a tester who just executes the test cases but can never replace those planning/documenting and analyzing test plan/design/cases.
   
4. People obssesed about tools are the person with whom you should not be talking anything about testing, they are like people from the well and they seek for help to come out and in turn pull you inside.
5. Tools are like aliens , they come in , influence you , evade you and rule you... When are you going to celebrate your Independence Day.
6. Some decades before Robots and Automatic Machines replaced people at work but I am amazed to look at the software industry where such Automated tools make the company hire more people to work on it. :D cos the so called automated tools require more manual work. ( Some communist party is supporting these tools I guess )
   
7. All Automation Testers are Manual Testers but all Manual Testers are not Automation Testers. ( pretty confusing , that's what I wanted )
   
8. Say a demon came and told you "I will erase some part of your brain , which do you want to sacrifice - your knowledge about tools or your testing skill?" What would be your choice .. ( of course, the demon will not earase the memories of the girl/guy who rejected you )

__ Manual Testing no more a shit job ! __

Please be aware that I am not against any Automation Testers because I see that they too are Manual Testers but as a matter of fact they may not agree as their pride and ego doesn't permit them to admit. Tools are a vital part but you and your testing skills are more than vital to any project.

I give you two choices -

Choice 1 - No, I was not conviced
{ sorry for wasting your valuable automation testing time and reccomend you to waste 5 more mins looking at this }

Choice 2 - Yes, I was convinced.
{ you should then spend 5 more minutes reading this }

"Respect a Manual Tester , God will gift you free tools"

Regards,
Pradeep Soundararajan
pradeep.srajan@gmail.com

Disclaimer : [ Intentionally left partially blank to check who is still in the well ]