Success Story of Er. Saurav Patel - Senior Test Engineer at Sapient shared on 14 Jan 2016:

Dear Testing Genius Team; My name is Saurav Patel. I want to convey my great thanks to you for providing very good study material and question banks for ISTQB foundation level exam. By reading this material time ang again I have cleared my foundation level exam with 72% without going to any training center...thank you so much... Now my next ambition is to prepare for certification for HP QuickTest Professional (UFT) as I my job profile demands expertise of this tool. Kindly mail me its full study material.

Thank you once again , Saurav

Published with the consent of Er. Saurav Patel
saurpat78@gmail.com

Before delving on the intricacies of going into a pilot project, I would like to describe few common pitfalls involved in the large-scale implementation of automation tools.

1) “Ease of use” of course being one of the key consideration in selecting an automation tool, can never overlook the prime requirement of good functionality. A tool can easily be misused while it may fail to do few simple things.

2) In the absence of a structured assignment of roles and responsibilities towards centralized methodology of using the tool, the users tend to get absorbed In several standardization attempts that land up evolving equal number of confusing approaches. Different users of the tool try to use it in different, ways as per their own convenience leading to collapse of the standardization efforts.

3) True value of a test automation tool can be better understood by carrying out a small-scale pilot project before a mass roll out.

Software Testing Genius

Due to this reason, in small sized organizations, the test managers lay greater stress on the pilot compared to selling their concept. They believe in avoiding doing anything new on a large scale.

Why Go in for a pilot evaluation project?

The objective of pilot project is to provide a safer opportunity to the organization to test the new automation tool, demonstrate its true value and discover deficiencies if any, well before spending significant amount of money, time and other resources on a full-scale project.

How to perform Poor Testing-A Primer for Self Improvement

This article is not aimed at inculcating negativity among the software testing community, rather it is a live pointer to various mistakes poor testers make in the real world scenario. This is better viewed as an opportunity for self-improvement in our software development initiative.

Poor testing leaves an adverse impact on the customer experience of the software product. Such poor impact on the customer leaves big dent on sales of the software product as well as affects the profitability of the company. It can lead to legal implications as well on occasions.

Poor testing can prove to be more expensive in the longer run. Spending lot many hours and considerable amount of money on software testing and missing out many problem areas and non conformances of the software product is the worst part of it. It is a sheer wastage of the organizational resources, and on the other hand it provides a false sense of security to the testing team and the organization.

Software Testing Genius

Important Do’s & Don’ts of Poor Testing:

Don’ts of Poor Testing:
Never do the following if you want to do a poor testing;

1) Do not Add Stress:
We can not learn much out the software product, by testing it at a low level of vigor. Hence it is essential that the product is tested against most severe levels of stimulus

An insight to Innovative Agile or Spiral Software Testing

The intent of life cycle testing promotes testing by software testing professionals from some agency outside the development organization. The prime advantage of testing with life-cycle approach are that we have crystal clear requirements defined before hand, and it is comparatively easier for an external expert to verify the facts. Software testing is generally considered as a destructive activity aimed to challenge the work done by the developers.

On the contrary, spiral-testing psychology promotes more cooperation among the development organization and the quality assurance. The is based upon the hypothesis that, in an environment of rapid application development, all the available requirements may not be that precise as expected, or may be varying drastically. Unless precise requirements are in place, it would be extremely difficult task for the software testing engineers to define the test criteria. The best possible solution remains is that software testing & development teams must work in tandem.

Bridging the gaps between Tester and Developer Perceptions:
Understanding of the stumbling blocks in the way of healthy relationships between the software testing teams and the development teams, it is important to respect the roles & responsibilities of each other. Both testers and developers need to break the age old ice and rise above the traditional confrontation.


Software Testing Genius


The need for secure systems is growing day by day, so is the requirement of powerful and sophisticated security testing. One of the reasons of this is exponential growth of e-commerce & e-business market & at the same time development of more and more applications aimed to get Web access for something or the other.