Success Story of Mr. Veerendranath M - Quality Assurance Engineer shared on 17th July 14:

First of all I really appreciate your website which helped me a lot,dealing all kinds of testing information. I followed your website and cleared ISTQB exam. I'm very much grateful for that. Now I am trying to clear HP Quality Center Certfication. I tried to take sample test from online.I am attaching the exam questions which I answered. Please let me know the correct answers for the questions.

Thanks a lot !!!! Regards, Veerendranath M
Published with the consent of Mr. Veerendranath M

Software testing managers declare some sort of well defined exit criteria to ensure that they have some form of closure to their testing strategy for a specific product. This product or service may receive further testing but, if the testing team is part of a development sequence, there must be some well-defined criteria that tells when the product is sufficiently well developed to be released to the customers.

If we are using failure mode and effects analysis (FMEA) tool during product development, we will ascertain if we have developed our verification and validation plans to respond to this document. Because the FMEA approach is a systematic effort to eliminate significant issues before they actually become problems, we need to ensure that our test documents are designed to reflect such a need.

Ethics of Software Testing: Good software testing managers maintain & follow certain ethics during the entire testing life cycle, few of them are being shared here.

Software Testing Genius

A) Ethics related to our Test Plan:
The minimum test plan we must execute against a product will be derived from the customer specification or our own standard, if we have one. We also recommend that our test group conduct product tests to failure and thence to destruction (if destruction makes sense in the characterization of the product). We should submit the compliance test plan for approval by the customer. This document may also contain some tests, verifications, and validations we have recommended.

B) Ethics related to the Test Reports:
When we execute a test plan, we generally update the plan in such a way that it transforms into the report - this way, all the relevant information will be contained in a single document. For any test required by the customer, we will indicate the results honestly and clearly. In some ways, we are nicely positioned in the enterprise because we report what is wrong - it is not our responsibility to fix the issues we discover. On the other hand, we have a tremendous responsibility to report everything we see.

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 GeniusThe 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.