Success Story of Mr. Rahul Chopra - California USA based Test Analyst shared on 14th Nov 14:

Thank you! I found your website for CTFL stuff on Google. I found your website very useful. I prepared for CTFL only from your website. Questions I found in exam are almost same as in your Database. I am sure anyone can clear the exam by going through your material and papers.

I cleared my CTFL exam today 14th Nov. 2014. I am impressed by your website and wanna to do QTP, LR, QC and CTAL (Technical Test Analyst) certifications. All the best! With warm regards

Thanks a lot !!!! Regards, Rahul Chopra
Published with the consent of Mr. Rahul Chopra
rahul.chopra762@gmail.com

Software Testing Genius
System Test Automation Primer-A Must Read for the Test Managers

It is essential for any software testing organization to be more efficient especially in test automation. The reason being automation is a strategic business activity, requiring sound support from the senior management; without which it can doom due to the lack of adequate funds & other resources. Automation is aligned with the business mission and goals and a desire to speed up delivery of the system to the market without compromising its quality. Automation remains a long-term investment and is an on-going process. Results can’t be realized overnight; expectation need to be managed to ensure that it is realistically achievable within a certain time period.

Software Testing Genius

Few Best reasons for system test automation are:
1) Better productivity of software testing engineers

2) Better coverage of regression testing

3) Better reusability of test cases

4) Better consistency in testing

Ethical Rules Practiced during Testing and its Exit Criteria

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 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;