Te STING is it?

           Software Testing was , is , will exist....as long as you have a human to create software we need another  Homo sapien  with something called Brain Inside to Test it , not Intel inside......

     Offlate,  I have been hearing this from some Testing Workshops, where people i mean speakers are concluding that testing will be ,to be precise Manual testing will be obsolete in the coming years and there are tools coming up which can write tests if you provide a business case ,and as you know the test case can be automated once you have it ,there are more tools around for finishing a manual testers Job, It is hard for me to prove them wrong , At the same time I cannot accept it at the face value.

       First thing guys don't accept you as a Manual Tester , you are not . It should be hard hit with Functional tester , I can quote a example here Pepsi bottling is a Manual process , But tasting Pepsi is not , it is as simple as that , there are so many human interactions /senses that are active. we see a button , click something, add a text, press what is not to be while testing so all these are not Manual process hope you all accept it.

   

       While I started writing this blog , I know for the fact that there will be atleast 12k people who will be executing manual test cases around the world. Let me explain my justification of the fact that testing will remain as a entity in any development model as long as my statement I started with is true, With evolution of software engineering there are so many changes that is happened on the Software Development front like we have tools being designed to integrate modules , Frame works which get changed so many new languages from  C , Cobol to .Net , Java,  Oracle DB the list is endless all of which are accepted to fit or suit a software which would be built with  $X in Y months/days/Years. But if you look back from Day one Testing has not changed or there are no rapid changes like what happens in development do you know WHY.

 It's one of the Hidden fact , in any Technology Eaten Strongly To End Risk.

        In what ever development projects , which ever technology they use , They hire a manual tester and not a machine to validate their quality, my point is a Tester learns or aligns himself so quickly to the process , Domain , Technology and starts working with application or  people that  he is assigned to, we are taken for granted so much  that you hear something like  QA will do it...No matter what time we Get into the project, or  Complexity of project what skill you had before ..nobody bothers,  we are  together called QA or Tester.. and our Job is to clean the software and give it to the customer, Just like CEO's present the Gift cheque to the Winning team in Cricket.

      So if everything is fine in the above case a Regression suite is prepared and ROI is thought of and Automation is initiated ,so with this about 70% of  Customers deny Automation due to cost  so we are left with 30% which go thru the Big screens of Automation, so we need  Functional Tester in 70% of the cases to beat up the application. I don't conclude that functional Testers are for ever , read my disclaimer.

I know each one of you would have his/her notion, I am not contesting any body here, this is what I opine for.

Disclaimer : Do not read it , because you are a Functional Tester , read only if  you love being it.

  

Testing is testing ...

Yes , I have been doing this for many years now with no realization as to what is being going on, But I was involved in all types of testing ....... ,

 With so many activities as a Tester,Test lead or what ever as long as you have Test appended to your role you do so many  important activities but nothing is captured or documented on your profile .. reason is you are not capturing smallest to the biggest and over the period you loose them ,if not refreshed timely. So keep some time for this on a week end or a off day were you feel i  need this at the back of my head  and refresh it ..and not at the time of a interview :) or if any org you have to certify for.

 You need to intrigue yourself and find a way to find your testing knowledge health if its red or green or dead :) , unlike other technologies we do not have a text book or MSDN to tell you this is all i know and if this is all its not ... We/I have tested so many products for customer x, y , ....Z each product or project is unique were you are placed in different position each time , i mean when you have all day to test and rest some time in slog overs you need to win the cup by scoring high its indeed a stressed up and down situation,But we do it and shoot the developers with some defects ..some may be missiles..I am pointing it out to say that our learning curve is parabolic we start with so much of knowledge and it dies down and goes up on the other side were we learn new tools,techniques and so on.

What I know in Testing is  directly proportional to what I know by Testing .here one is activity and other is a topic.let me not confuse you more, An activity is the process of understood topic.always we forget the topic as we progress with our activity.

Why I say its testing is you need to know of it by the book value than , saying i have done it but just some time back were i cannot get it now....its dangerous..so keep in mind conceptual know hows .....of any topic you come across....while doing Testing.

' C ' You B y e

                   
                   Well I am wishing a farewell to none other than -  Dennis Ritchie  , He was with  us   & yet  no one ever remembered him  after their graduations  ,  There is less I know about him and more about his syntax in C' ..A true programmer has parted us. After the innovator Steve Jobs..Dennis was a True epitome of a Programmer...who  has touched every one of us ; just another nail to IT world.