A Rapid Tester

How SEO Works

2010-03-07T17:45:00.000-08:00

We all hear about SEO ( Search Engine Optimization) on a regular basis, yet we are not sure about what is exactly is. How it works? We just feel that SEO is a complex thing and it requires expertise to be called SEO champion. Well not all is true. SEO is not as complex as we think, yet proper thinking and analysis will go a long way in making SEO effective.

You've finished your web design, uploaded your files, and set up your blog, but you're still not getting as many visitors as you hoped for. What is wrong here? Chances are you haven't started working on one of the most important ways to market your site and which is Search Engine Optimization (SEO).

Search Engine Optimization refers to the collection of techniques and practices that allow a site to get more traffic from search engines (Google, Yahoo, Bing). SEO can be divided into two main areas: off-page SEO (work that takes place separate from the website) and on-page SEO (website changes to make your website rank better).

One of the basic truths in SEO is that even if you do all the things that are necessary to do, this does not automatically guarantee you top ratings but if you neglect basic rules, this certainly will not go unnoticed.

SEO can be a 30-minute job or a permanent activity. Sometimes it is enough to do some generic SEO in order to get high in search engines – for instance, if you are a leader for rare keywords, then you do not have a lot to do in order to get decent placement. But in most cases, if you really want to be at the top, you need to pay special attention to SEO and devote significant amounts of time and effort to it. Even if you plan to do some basic SEO, it is essential that you understand how search engines work and which items are most important in SEO.

Keywords – the Most Important Item in SEO

Keywords are the most important SEO item for every search engine – actually they are what search strings are matched against. So you see that it is very important that you optimize your site for the right keywords. This seems easy at first but when you get into more detail, it might be a bit confusing to correctly determine the keywords. But with a little research and thinking the problem of selecting the right keywords to optimize for can be solved.

1. Choosing the Right Keywords to Optimize For

It seems that the time when you could easily top the results for a one-word search string is centuries ago. Now, when the Web is so densely populated with sites, it is next to impossible to achieve constant top ratings for a one-word search string. Achieving constant top ratings for two-word or three-word search strings is a more realistic goal. If you examine closely the dynamics of search results for popular one-word keywords, you might notice that it is so easy one week to be in the first ten results and the next one– to have fallen out of the first 30 results because the competition for popular one-word keywords is so fierce and other sites have replaced you.

2. Keyword Density

After you have chosen the keywords that describe your site and are supposedly of interest to your users, the next step is to make your site keyword-rich and to have good keyword density for your target keywords. Keyword density is a common measure of how relevant a page is. Generally, the idea is that the higher the keyword density, the more relevant to the search string a page is. The recommended density is 3-7% for the major 2 or 3 keywords and 1-2% for minor keywords.

3. Keywords in Special Places

Keywords are very important not only as quantity but as quality as well – i.e. if you have more keywords in the page title, the headings, the first paragraphs – this counts more that if you have many keywords at the bottom of the page. The reason is that the URL (and especially the domain name), file names and directory names, the page title, the headings for the separate sections are more important than ordinary text on the page and therefore, all equal, if you have the same keyword density as your competitors but you have keywords in the URL, this will boost your ranking incredibly.

These are few of the Basics of SEO. I recommend that we as testers should be knowing these basics to increase our knowledge.

Happy Testing.

Madhukar

Speech by CEO of Mind Tree

2010-03-03T19:42:00.001-08:00

I would like to share with you one of the best I received just a few days ago. Its a Speech delivered By Mr Subroto Baghchi, CEO Mind Tree to the class of 2006 at IIM Bangalore defining success.

Here are a few parts of the speech.

My mother used to take ash from the chullah and mix it with the earth and plant seedlings. This time when they bloomed, the neighbours asked her why she was taking so much pain to beautify a Government house? My mother replied it did not matter to her that she would not see the flowers in full bloom.She said," I have to create a bloom in a desert and whenever I am given a new place, I must leave it more beautiful than what I had inherited".

That was the first lesson in success," It is not about what you create for yourself, it is about what you leave behind that defines success".

Imagination is everything. If we can imagine a future, we can create it. If we can create it, others can live in it. This is the essence of success.

The safdurjung Hospital is a cockroach infected dirty place. The over-worked under resourced sisters are victims of de-humanized life at its worst. One morning attending to my father i realized that the blood bottle was empty. Fearing that air would get into his blood I summoned the sister to do the needful. she very rudely asked me to do it myself. In that horrible theater of death I was in pain, frustration and anger. Finally when she relented and came my father opened his eyes and murmured to her," why have you not gone home yet?" here was a man on his deathbed more concerned about the overworked nurse. I was stunned at his stoic self.

I learnt that there is no limit of how concerned you can be for another human being. Success is your ability to rise above your discomfort whatever be your current state.

Two years at the age of 82 my mother had a paralytic stroke. I flew down from US and spent two weeks with her. She was neither getting better nor moving on. I had to leave back to work. while leaving her behind I kissed her face. Int he paralytic state and garbled voice she said," why are you kissing me? Go kiss the world!"

At the confluence of life and death a woman whose life was crowned by adversity was asking her son to go and kiss the world!.

Success is about giving back to life more than you can take. It is about creating extraordinary success with ordinary lives!!

Are you on uTest... I am....Check out the interesting things happening...

2008-03-13T00:41:00.000-07:00

Boston-based uTest has raised $1.7M to bring to market a crowd-sourced quality assurance
(QA) marketplace and community. The service has begun recruiting testers in anticipation of its official launch, expected in early 2008.
No fuzzy logic here; uTest presents clear and communicable value propositions: For companies in need of QA, uTest is providing an on-demand environment for the management of full testing cycles.
The company’s founders recognized that QA and usability testing solutions are inefficient. QA departments are either under-utilized when waiting for versions to test, or over-extended when a new version comes out. To most SMBs, QA outsourcing is neither cost effective nor available “on-demand”. Then, of course, there are cost-cutting measures that leave companies unable to sufficiently fund QA efforts, ultimately shipping buggy applications to users like us.
The uTest testing platform itself is entirely Web-based and provides the management of complete QA cycles, from creating/loading test scripts, to selecting the target community (profile and environment) of testers required. The platform also provides test case management tools, real-time information on bugs and defects logged, statistical information on release maturity level, as well as QA coverage and market readiness. Support for bug tracking systems includes Bugzilla, Jira, FogBugs and will be expanded over time.

In a smart business move, uTest will not charge companies to use their platform to manage testing and QA cycles—this will be entirely free of charge. uTest will only charge for the services provided by the community of testers.
The uTest offering makes a lot of sense to me and I expect it will be warmly embraced for several reasons. First, consider for a moment that for many SMBs, QA management solutions such as those offered by Mercury or IBM-Rational are beyond their reach. Speaking from personal experience, the majority of the testing cycles I’ve seen have been “managed” on Word or Excel. The “on-demand” model which has been proven time and time again on the Web from CRM to ERP, should work just as well for QA. The fact that the platform will be offered free of charge, pushes the offering to “no-brainer land”.
Second, beyond the manageability aspects of uTest’s service, companies will obviously enjoy the cost saving aspects of paying testers by the bug. It’s this aspect that in my opinion will make uTest’s offering relevant not only to SMBs but to large organizations as well. Logic would dictate that if they embraced off-shoring and near-shoring, crowd-sourced QA shouldn’t be too jagged of a pill to swallow.
Third, recruiting a userbase of testers should not be difficult. There are droves of potential testers in countries such as India, China, Russia, Bulgaria, Estonia, etc. Also, getting hired through sites like Elance and RentACoder is becoming increasingly difficult due to the growing number of service providers. These same individuals can theoretically provide testing services instead of programming.
All-in-all uTest sounds quite promising and has earned a place on my companies to watch in 2008 list.

Confused IT Engineers

2008-01-19T06:19:00.000-08:00

I was reading this very nice article about this famous fable "Grass is always green on the other side of the fence". It reminded me of an conversation which i had with a IT Engineer some time back. He wanted to move from his present company due to few reasons which gives an insight into confused IT engineers mind. Somehow i feel like that the same confusing situation is present in every Software Engineer's mind or rather the phenomenon is more common in entry level candidates as they don't know what is that which they exactly wanted to do. Some get fascinated by the Higher salaries, some by onsite opportunities and some just want to jump without proper analysis about the type of work which the Organization where they are going to join will be offering them. I feel that this situation is more prevelant among the group of people who are in early Years of experience levels say people with 1-3 years experience. Here goes the conversation:

IT Engineer: What is the promotion cycle in Company X? Do they give any weightage to previous experience?
Madhukar: Since u have around 1.5 years exp only earlier hence u might get prmotion to senior software engineer at least after 2 years but that all always depends on your performance. It might happen earlier as well. If you had around 4 years to 5 years of prior exp then they would have taken you mostly as senior engineer, but not now.

IT Engineer: 2 years after I join them or of total experience?
Madhukar: 2 years after u join them would be an ideal time, however it might happen earlier as well.

IT Engineer: ok
IT Engineer: and do they have salary blocks for Engg and senior Engg?
Madhukar: no..average hike will be 10-15% or 12-16% every year like other companies normally give but this as well depends on the performance.

IT Engineer: ok and what is the componenet of there salary like basic pay, felxible benefits and Specail compensation plan etc.
Madhukar: lta, basic, bonus, gratuity etc.

IT Engineer now stops asking questions. I thought why not i ask him some questions just to know his opinions.

Madhukar: What difference does it makes if you are not hired as a Senior Software Engineer at Company X...?Means what is your take on this?
IT Engineer: Right now I am working as Senior Executive Quality and if I stay with this compnay longer I would become lead executive by end of this year so If I decide and go to Company X ... then I would have to start as fresher and then after minimum two years I will become what I am right now.

Madhukar: Ok why do you want to change your present job when u feel u have so much opportunities at the current company?
IT Engineer: tell you honestlyI was thinking of leaving my organisation 3-4 month back

Madhukar: hmm ok...

IT Engineer: and now this came to me like a surprise because i was not expecting anything like that now and here in my company in last 3- 4 month things have improved a lot.

Madhukar: So what are your priorities and long term goals?
IT Engineer: I learnt a lot in this company and still I am learning and if i stay here for another 3-4 months I would get the oppurtunuty to impement CMMi in my company.

Madhukar: What CMM level does Company X has?
IT Engineer: they dont go for CMMi, they say they have there own standards.

Madhukar: Then what is the compelling factor which says you to change since in this case you will be moving to a place where you will not be able to work on your interest area. Lets say a company Hires you as a Lead In qualtiy will you join that company? I mean to ask what do you look while making a change Designation, Money, type of work? what?

IT Engineer: right now I looking for more money because I took a home loan and want to repay that fast and I know that kind of profile I am looking for ... is always challenging
Madhukar: How will joining Company X help you in that? What is your total expenses at present location after spending on room rent, food, transport and all like going to your hometown once a month etc......If at Company X you have a higher take home salary then on the other hand you might also have higher expenses per month in the new city as well.

IT Engineer: thats what making me rethink each and everytime because my major concern is this only.
Madhukar: means i am interested to know how does joining Company X gaurantees you that you can repay home loan quickly.

IT Engineer: yes true
Madhukar: Hmm which means designation does not matters?

IT Engineer: it wont help me, Designation do matter to me.
Madhukar: How? Don't you feel that all these designations are the fancy names given to just seperate out people and make the people happy....Ok what are your responsibilities as a senior QA engineer at present role..and how do you gaurantee that being Senior QA at Company X also will give you same? Might be Company X's definiton of Senior QA and the roles and responsibilities is quite different than other companies.

Madhukar: In India if you are not promoted to a higher level by attaching a fancy tag to your
Visiting Card then people start to change the companies and thats the game companies play to lower down the attrition rate,....The Thumb rule in India is 0-2 Years Entry Level, 2-4 Years Senior Engineer, 4-6 Years Lead..., 6+ years Manager
IT Engineer: yeah you are absolutely correct as i told you that I was not at all expecting the call from Company X once i received a call I thought why not to give an interview and see where i stand in the market clearing the first round gave a confidence and then clearing a second round gave me more confidence

Madhukar: Ok, i was just asking the questions because of my curiosity.
IT Engineer: ok

Madhukar: It was not meant to demoralise you or stop you from taking any decision....I just wanted to know if you have thought from all angles and was just making you realize the impact which this decision can have at a later stage.

The discussion continued for a long time and i made few observations: Software Engineers in early career just dont realise the big picture and want to change companies because of money, better work, onsite and several other reasons. We should always see as to what extent we fit in the next company, what goals and benifits are fulfiled and finally we should not move by the feeling that better things exist on the other side. Better things do definitely exist however they needs to be explored properly.

The uTest Testing Community: Get Paid for finding Bugs

2008-01-11T05:12:00.000-08:00

Found out a pretty interesting new concept uTest, check it out.

By joining uTestTM you will become a member of the world's first online community of software testers and gain access to the uTestTM Testing Platform. As a Tester in our community, you will be the first to try exciting and innovative applications, many of which are pre-released and have yet to be introduced to the public. Our network of testers (whose experience ranges from common consumers to highly trained testing professionals), forms a community from around the globe dedicated to experiencing and helping perfect bleeding-edge technology.

Our Testers enjoy extremely flexible hours - so you can work when you want to and at your own pace. In addition, the uTest Testing Platform can operate on any machine connected to the internet, which means Testers can work anywhere they want: from the comfort of their own home to their local coffee shop.

Appreciation and its impact......

2008-01-10T05:08:00.000-08:00

Was thinking from a long time to write some thing and after a long time here i am with my thoughts on a topic rarely in the discussions. The inspiration for writing this came from Shrini whose views i love to read.
I had a recent conversation with Shrini on testing ERP applications which made me write my experiences.

ERP , the vast ocean of Enterprise applications, I was doing this testing for an ERP application some time back and due to a showstopper in the application for which i was developing automation scripts i thought of doing some testing of my own. To my surprise i was finding bugs which could have been caught long time back and which were so obvious, this raised my curiousity to test it more and i started doing exploratory testing. As i was finding more and more bugs my excitement was rising.
I managed to find some 50 odd bugs in 2 days and was extremely happy that i found some real trivial and amazing bugs in the application. Then started the real challenge of explaining the management about the importance of rapid testing versus scripted testing as somehow i have the feeling that scriptd testing is considered by the management as a robot which will perform all jobs by itself and once completed we can run them to find if any bugs have been injected when a new build was released.

Here goes the conversation:

Me: I would propose ET (Exploratory Testing) for testing this application as i dont find any value addition in doing scripted testing which i have been assigned which does not finds the bugs which ET can find.
Manager: Why?

Me: Its been more than 2 years since the development for this application started and and still their are so many bugs in the application which should have been caught by now. I would like to know from you what are the benifits of we doing scripted testing when it is serving no purpose.

Manager: Well i feel that their is already another group who is looking after this aspect of the application.

Me: You mean to say after the exploratory approach of testing.
Manager: Well i don't know what is exploratory testing ( The manager is from a development background), i only can suggest you at this moment that we have some goals to achieve and we have clear directions from higher management of how we achieve the same hence your priority should be to perform scripted testing.

Me: But it is not finding any bugs which should be our goal.
Manager: I already told you that other groups are taking care of this.

Me: ( I knew no other such group is doing this kind of testing) I would like to know who is that other group and if such a group exists then i would like to see how they are performing testing as according to me these bugs should have been identifed by now.
Manager: At this point i have no clue as their are so many teams working acroos the Globe so it would be difficult to identify and provide you the details, hence you pay attention to your goals for this year that is scripted tests.

Me: Are you aware of something called “Pesticide Paradox”?
Manager: No, what is this pesticide killer you are taling about.

Me: Well bugs are like pesticides in software terminology. As pesticides over a period of repeated application of a specific pesticide acquire immunity to it and fail to show their presence, in the same manner software bugs fail to show up and become immune to repeated application of specific Test cases which we call scripted testing. Might be some bug is lying in the system which our tests dont navigate through at all.

Their are still so many bugs lying in the application but since the way we are looking at quality is just to make sure that the important business processes keep on running hence we are not seeing the so many hidden bugs which makes me more concerned about the quality of the product.

The discussion continued for a long time and the output was negative as due to vastness of ERP applications generally quality is given a backseat and thing which is made sure is that the main functionality or the Business flow should work properly which the customers are going to use.

Customers also being not taught about the application and with limited knowledge just know what they have to follow to complete a scenario and follow the same steps. The scripted tests also are made sure so that they cover the business flow. So many bugs are left in the application and no one complains about it simply because the business scenarios are running and thats what customers are going to use, but what if the customers deviate from the normal process and do a bit different?

The attitude for quality should be present during testing and this should be well supported at an organizational level, for this we still need to educate ourselves a lot and give due respect to quality.

The point i like to highlight here is:

If the software testing team gets appreciation and their views are taken with due respect then we have many passionate testers who can do wonders for the company.

Sadly we dont find such managers and stakeholders, everyone is busy in thinking that why should i put my head in this dirty work, let me do what i am assigned to and achieve the objectives and goals assigned.

Appreciation and freedom given to express views and taking prompt actions on the same goes a long way in building good testers.

What do you say?

Madhukar.

Testing Google- Boundary Values Explored

2007-06-02T09:37:00.000-07:00

Another interesting feature which i tested was Boundary value of Google's search box. I was reading this interesting post by Debasis and i found out the work done by him really impressive and thought of doing my own boundary value exploration for Google's search box...

Debasis has mentioned in his analysis that he found out the maximum no of characters which can be pasted in the box is 2048 and on further analysis he found that it is 1980 characters which when passed will result directly on a "Google 404 Bad request Page".

Here is what i have found:

I found that it is not the exact no 1980 which can cause the "Google 404 Bad request" page. I found it to be something else. I found that it is not the no. of characters which really matter for getting the bad request page, however it is the positioning and placements of few special characters like #,@, ( to name a few which were causing bad request page.

We need to definitely explore a bit in deep to find out what exactly causes bad request page because after my initial investigations i am now sure that it is something which needs time and deep investigation to be done to find out the exact reason.

I found out that i was able to reproduce the "Google 404 Bad request" page several times using different combinations and different placements of characters in the search string. The interesting part was that whenever i included a ( after several @ symbols in my search string, the result would automatically shift the line starting with ( on the next line. For more clarity check out the snapshot here.

I was surprised that why the search was displaying (, # and few other characters in next line of search results. I found out that increasing the no. of #'s in the search string was increasing the chances of minimising the 1980 barrier required to get a Bad request page. I pasted the string mentioned below which has 770 characters in it..

_________####_______________#############____________________+++++++++++++++++++++++++++++++++++@@@@@@@@######@@@+++++@@@@@@@@@@@@@@@@@(((((((((((((((((((++++++++))))))))))((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((((@@@@@@@@@@@@@@@@@((((((((((((((((((((((((@@@@@@@@@@@@@@@@@@@@@@@))))))))))))))))))))))##################################################################********************************(((((((((((((((((((((((((((((((^^^^^^^^^^^^^^^^^^^^^^^((((((((((((((((((((((((((((((((((((((((=====================================================================================================================================((((((((((((((((((((()))))))))))))))))))))))))))))))))))))))))))))))0#################################################(######

Paste the above string exactly in the Google search box and you will find that when we press Search Button we get the bad request error. Now if i reduce the above string to 769 characters i was not getting bad request error.

The interesting part was that sometimes this bad request error comes also when i have 765 characters and sometimes it does not comes.

Strange but true.. I see definitely here a relation between how we place characters and which characters are at what position has definitely to do something with bad request page.

I am sure that we can even further reduce the no of characters to get bad request page.

Output:

We need to explore more on what exactly causes Bad Request Page..

Happy Googling..
Madhukar.

Immediate boss is the reason people stay and thrive in an organization. And he ’s the reason why people leave.

2007-05-31T04:10:00.000-07:00

Sometimes back i was going through this amazing article written by Azim Premji which truly reflects state of the IT Companies in today's world....I am amazed to see the trueness which this article reflects...You might probably feel that you also have encountered this situation sometimes in your life...

What do you say...

Azim Premji, Wipro
Every company faces the problem of people leaving the company for better pay or profile. Early this year, Arun, a senior software designer, got an offer from a prestigious international firm to work in its India operations developing specialized software. He was thrilled by the offer. He had heard a lot about the CEO. The salary was great. The company had all the right systems in place employee-friendly human resources (HR) policies, a spanking new office,and the very best technology,even a canteen that served superb food. Twice Arun was sent abroad for training. "My learning curve is the sharpest it's ever been," he said soon after he joined.
Last week, less than eight months after he joined, Arun walked out of the job. Why did this talented employee leave ? Arun quit for the same reason that drives many good people away.
The answer lies in one of the largest studies undertaken by the Gallup Organization. The study surveyed over a million employees and 80,000 managers and was published in a book called "First Break All The Rules". It came up with this surprising finding:
If you're losing good people, look to their immediate boss. Immediate boss is the reason people stay and thrive in an organization. And he's the reason why people leave. When people leave they take knowledge, experience and contacts with them, straight to the competition. "People leave managers not companies," write the authors Marcus Buckingham and Curt Coffman. Mostly manager drives people away?
HR experts say that of all the abuses, employees find humiliation the most intolerable. The first time, an employee may not leave, but a thought has been planted. The second time, that thought gets strengthened. The third time, he looks for another job.

When people cannot retort openly in anger, they do so by passive aggression. By digging their heels in and slowing down. By doing only what they are told to do and no more. By omitting to give the boss crucial information. Dev says: "If you work for a jerk, you basically want to get him into trouble. You don't have your heart and soul in the job."

Different managers can stress out employees in different ways - by being too controlling, too suspicious, too pushy, too critical, but they forget that workers are not fixed assets they are free agents. When this goes on too long, an employee will quit - often over a trivial issue.

And finally the Golden Words...
Talented men leave. Dead wood doesn't...

Add Value to your Automation....

2007-05-30T06:30:00.000-07:00

Simplify Automation Creation and Maintenance....

I am sure anyone involved in automation testing would have encountered the situation below:

Your team is working hard on an application, lots of automation scripts are created, the test suite is running all fine when suddenly one day you wake up to find that all scripts have failed..
Nothing changed in your code..right? Then what caused this catastrophic failure..
Everyone is behind you asking for the reasons why it failed and you yourself do not know what happened...Strange isn't it...? How can a person who has written the scripts be unaware about why they failed in the night..
I will tell you why....

1. The scripts were procedural test scripts which were just recorded and replayed with some checks in place, some loops, some if else statements and so on...

2. These kind of scripts are difficult to maintain when the application changes, and in development the application changes quite frequently from build to build. Some new objects get added to the application, some old objects are not present, some objects have their properties changed and so on....

3. Testers generally have an attitude that automation tools are just about record and replay and nothing more, they are unaware about the capabilities which they can bring into it.

How do you overcome all these issues then?

You can simplify maintenance by avoiding to fall in the pitfalls of poor record and replay scripting..which will not lead you to automation success.

Automation becomes of little value when it does not provides useful information which can be reviewed by testers and most importantly my managers (after all managers are interested in the number game, in the % age of bugs covered by automation etc)...

Never rely on the tools built in reporting features. Create a library of functions which can be then reused by each test. Using the library the output can be given in so many formats. Find a few examples here.

1. HTML Files: People love coloured HTML pages, plus on top of it if you can add a little bit of Java Script to it then it can be more presentable.
2. Excel Sheets: Excel sheets can be processed easily by machines and people can do lots of manipulations with the data just by using few mouse clicks.
3. Database: Results can also be posted directly to a database and which can then be used to comapre with a pre existing standard template.
4. XML File: Another very popular medium of output.

Reported results should contain enough information which can answer the following:

What happened to the application when error occured.
Exactly at which point did the error occured.
Which script and which line of code caused the error.
What action does the Framework took when error occured.
How many errors were application specific and how many errors were due to errors in scripts itself.
How many test cases ran totally?
How many passed and how many failed?

One more feature can be built into the framework..Snapshot of the application can be taken and stored whenever an error occurs so that it becomes more easy to debug the errors.
Snapshots also provide a real proof of where the error occured. Snapshots can also be customised with the Log File ouput, for example the time stamp in the log file for a particulat step can be appended to the Snapshot file name so that it becomes easier to find the actual state of the application at the point when error occured.

Most Importantly remember:
An automation effort which runs for several hours is of little importance if it takes another several hours to figure out what went wrong and to interpret the results..

And yes i will be posting many new ideas for automation..so keep reading...

Happy automation..
Madhukar..

Tools for a Tester....

2007-05-29T09:39:00.000-07:00

I was reading some interesting artciles on the net and came across pretty good tools which a Software Tester should have handy for getting help in his/her testing....

The very basic utility that each tester should be aware of is Process Monitor which is a File and Process Monitoring Utility in real time..Its nothing new..its a combination of earlier known Filemon and Regmon...Now its the power of 2 in 1..
Have a look and enjoy the super power you are charged with...

Wanna have more...I would say that a Tester should always keep his guns loaded with destructive weapons which he needs most of the times..for example while testing an application he would always need the below mentioned:

1. Random Test Data to test applications reaction for different values.
2. Destructive data which is the data not acceptable to the application..always keep a notepad ready which has lots of combinations of special characters, ASCII characters, strings with different lengths, very long strings etc..

Have a look at various tools available which generate random test data for your convenience which might help a lot..One such example of a test data generator is here . Check it out it can be a handy tool to generate data in different formats like HTML, XML, Excel, CSV etc....

Also read the article by James Bach about more of weapons here.

Happy Testing....
Madhukar..

Test Automation Realities

2007-05-15T10:34:00.000-07:00

Ever Wondered why software Test Automation Fails

This is my First ever Blog on the internet and this happened just because of the person who i respect a lot and have learnt a lot of things from him. His name is Shrini, and he hired me at Aditi Technologies from where i started this career of Software Testing 4 years ago. Shrini as i know is a great follower of in depth learning about Software Testing and i have learnt a lot from him.

The views presented in the article below are completely mine and their might be people who do not fully agree to them. I am open for any comments for my views so that we can together make Software Testing better.
I know we all who are involved in this Software Testing world would have encountered sometimes in our Life a little bit of Test Automation using Testing tools. I would like to ask a question, what are the responsibilities of a Software Test Automation engineer?
The answer which i generally get is he/she should be able to automate the application after all that's what pretty simply is the definition about.

I have came across lots of people who will just be doing record and play back using the Test tools and do you feel they deserve to be called automation engineers? A straight answer is NO...

Well Test automation is not about recording and replaying the actions to see if something has broken. It is much more than that in fact and required lots of experience and skills to become a effective Automation engineer. The most important of which is to learn first what automation testing is all about and then rest all will fall in right place.

Do you find new bugs using Automation?

Their might be different views for this, but the truth is that Automation can never find new bugs.
It is always the same functionality and same scripts which you will be running usually called regression testing where you might say that this particular functionality which was working earlier is not working now but you cannot say that a new bug has been introduced because you simply don't have an automation script for that.

How Automation should be done then?

Software Test automation for most of the testers today is just a phrase. They don't really understand the meaning of it and just start jumping into it. To take an example in India we have these training institutes which i call money making shops which can be found at every nook and corner of the streets. But the reality comes when you actually join them. You find that there are no computers, no teaching faculty which is good enough. These shops do so many promises to you that we get lured by them, and yo here comes the easiest prey for them (The Fresher). A fresher who has just passed out from college who does not know ABC of Software Testing jumping into Software Automation...can you believe this? The shops charge heavy amount of money and provide with Placement guarantees at the end of the course...Heights..isnn't it....? If getting a Job was so easy then why do we in India have so many unemployed people still....A thing to ponder upon....

This happens because he has heard that get some knowledge about Software testing, learn 1 or 2 automation test tools which will add a Buzzword to your resume and then their are these so called recruiters who will do a CTRL F on the resumes to just find words like "Automation" and some famous automation tools and wow you have got an interview call. Now if you are smart enough then you can fake out the Interviewer and you are in....Look pretty simple...And the fact is that yes we have so many automation engineers today in so many comapnies but i would say that a person does not becomes an Automation Engineer just merely by working on a Tool and doing some scripting in that.

I still feel bad that people don't really understand the real meaning of Automation Testing. For most of them its just record and replay to test the application. If you want to be a good automation engineer then i would say do the following:

1. Spend some time to actually learn Software test automation and how is it different from normal testing.

2. Have your concepts and logic very clear so that given a programming language you can easily convert your logic and apply them in that language.

3. Learn a scripting language like Vb Script, Java Script as most of the Test Automation tools revolve around scripting.

4. Read good books on Software Test Automation, read articles by great personalities in Software Testing.

Only when you feel that you have done all what is mentioned above you should think of working on a Test Automation tool. To emphasise once again i would say that Automation tool is just a medium to achieve your goal. Their are thousands of people who call themselves automation test engineers and Good Test Automation Engineers are very few. To find them is also very difficult.

Don't be lost in this huge crowd of automation engineers, stand apart so that the world knows you. Browse the net and read interesting articles on Software Automation. Their is so much to learn and so less time. Don't waste time and prove your worth to this world. You are capable of doing it, it just needs a change in your attitude, your thinking and you can be a better Tester.

To be a Good tester you should have an attitude and most important you should be a better thinker.....Testing cannot be taught, it just comes out as a result from better thinking...

Madhukar....