Success Story of Ms. Janani Manickam - Quality Assurance Engineer shared on 23rd May 14:

Sir, I cleared my QTP 11.0 (UFT 11.x) certification today. The QTP study materials from your site helped me a lot in clearing the certification exam. Thank you so much for it. You are helping so many students like me, free of cost. Thank you for that and keep up your great job!
PS: There are handful of questions about connecting QC 11.0 / ALM to QTP that are asked during the certification exam. If possible kindly add those questions too in your list for future students. Regards, Janani
Published with the consent of Ms. Janani Manickam

Software Testing Genius
Tricks Involved in Selection and Implementation of Test Automation Tools

Smart testing managers use comprehensive selection criteria wherein a small-scale pilot study remains helpful in reinforcing the decision & understanding the value of a particular tool in a better manner.

Successful tool selection is no guarantee of its successful implementation within the organization. Majority of the organizations buy the testing tools that become mere show pieces or in other words “shelfware”, simply because the organizations could not derive intended benefits out of their investments due to one reason or the other.

The cost of buying a software testing tool remains quite small compared to the cost of the internal efforts required for its implementation. Testing managers spend sizable amount of their time & energy in promoting the tool internally, organizing training & support, and creating suitable infrastructure to support the test automation regime.

Tool Implementation & Iceberg Analogy:
Tool implementation process is analogous to an iceberg. Like an iceberg, nine-tenth of efforts on software testing tool remains below the surface.

Purchasing a test execution tool is the easiest job, wherein we are shown the tip of the iceberg that is the rosy picture of the test automation. Majorities of the organizations fail in test automation due to the poor visibility of the iceberg below the surface.

Software Testing Genius

The tool implementation comprises of following 3 key elements:

1) Infrastructure or an automated testing regime;
2) Internal promotion activity usually performed by the “tool champion”;
3) Continuous support from the implementation team & the management;

Techniques of Continuous Improvement used by the Expert Test Managers

Undoubtedly an impulse of patting your back powers you, the way you, as a manager of your energetic software testing team, maneuvered through the testing cycle of your product, just shipped. The fact remains is that you just happened to have a temporary escape from the defects that your customer might not be able to fish out at the moment. Hence you can’t afford to relax yet, as many more challenging tasks still remain for you. Remember that customer will not tolerate bugs which could cripple their business at any point of time in future.

Every tester knows the ground reality that every software contains innumerable defects, so it’s impossible to produce successful package once & then forget. As long as testers continue to test, they find more & more problems. This happens especially in case of complex products that operate under sophisticated environments, wherein customers club multiple software packages from many software & hardware vendors to build a solution to their business problem.

Anyway, once the current version has gone, get ready for another better version. You can certainly think of continuous improvements to prevent any mishaps from occurring on the next. Continuous improvement means solving problems which irritated you in the past so that you can avoid them in the future. It is quite important for every manager or tester not to lose sight of any shortcomings encountered in the previous version.

Here I am discussing five simple techniques on continuous improvement deployed by the intelligent test managers.

Software Testing Genius Technique-1: Doing self-evaluation to close the Project Loop

Software testing teams in good organizations perform a periodic self-evaluation to close the loop on the project. These are reviews targeted at identifying what worked well & what didn’t. The results can lead to adjustments in testing techniques & processes.

Attack-driven Testing of Payment Management Systems for Credit Cards

As credit cards being a status symbol are being used by almost everyone, managing their payments has become an increasingly complex area. Credit card payment management system is the most common banking application, so the need for having a foolproof secure system is of prime importance. Software testing engineers are building comprehensive threat profiles and test plans by proactively putting themselves in the shoes of smart attackers.

The objective of deploying such an attack-driven testing is that security holes in these sensitive applications can be plugged to the best possible extent before an attacker can find them. Of course there is no end to the imagination of evil minds, yet the testers have to stay constantly alert on the new potholes.

Software Testing Genius

An overview of credit card payment management systems:

Credit card payment management systems are used by banks to track the payments and follow up on past due payments. These applications automate a lot of the work in managing card payments and reduce the manual interventions required for ensuring payments.