Success Story of Mr. Bhaskara Rao - QA Test Engineer shared on 24th Dec 14:

Hi Yoginder!!! Many Many Thanks to you & your software testing genius team, Yesterday I have passed the CTFL exam with 80% in my first attempt. I just practiced all 1140 questions posted on your site softwaretestinggenius.com & from crash course questions also.

Now I am trying to prepare for CTAL - Test Manager exam in Feb. month. Could you please provide me links to the sample papers.

Thanks once more !!!! Best Regards, Bhaskar
Published with the consent of Mr. Bhaskara Rao
raobhaskarv@gmail.com

Intelligent software testing managers lay their key focus on the security testing of their system, right from the early stages of the system's life cycle.

The process begins with the drafting of the security test documents. Your starting point can be the security test plan if you were assigned to perform functional testing on a system that is new or new to you, & which can be to familiarize yourself with the product. Generally people prefer one security test plan per release, but you may have one or more functional test plans, mostly depending on the size of your system & its complexity.

Software Testing Genius

Next you can prepare a test case outline or test case document that will outline your test cases to be run with each test case. You can start by noting down & dividing the entire system into various security areas that you may be planning to use at the beginning of your test case documentation. Since test case outline document can grow to a gigantic size, you can have multiple test case outlines for every release. Each one of these can deal with a different security risk or product area.

The next you need to gather all the information you can find on the known product bugs & known security issues. You won't really analyze this information immediately, but you need to have some familiarity with it & have concrete data at hand to refer to later. With this you will have a much better idea of what security issues exist & a list of the ones you specifically want to consider.

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.