Process

The FTSC testing/QA methodology is based on a 4 phase approach.
The process is a living practice that has multiple execution points that support dynamic implementation, enhancement and evolution of the process to correspond to your product advancement.

For example:

Test cases and test suites can be added or altered as needed.

Specific test modules or test suites can be run to validate a point release or patch.

Full or partial regression testing can be implemented to verify a defect resolution.


The four phases of the FTSC Process are:

Assessment << click for more info

A QA specialist will work with your staff to identify and capture the requirements that will define the testing and QA specification.

Definition << click for more info

The Definition phase is a two-part process.  Using the findings from the Assessment phase, analysts draft high level test plans and strategy.  Senior testers adapt these into detailed test cases and specifications for testing environments.  Throughout the process, clients are notified electronically of findings.  Errors, observations, and anomalies as well as detailed test plans which enable developers to reproduce errors are immediately available through our on-line test management and bug tracking systems, providing an immediate return on your investment.

Execution << click for more info

Thanks to our detailed scientific approach to test plan development, FTSC employs lower cost testers to exercise all or combinations of the test cases for your products as needed.   Results (positive, negative or ambiguous ) are documented and reported.

Evaluation << click for more info

During the Evaluation phase, and throughout all of the other phases, a dedicated QA specialist monitors progress, analyzes findings, and works with developers and engineers to ensure optimum results.

 

 

Assessment

Overview
Before any test plan or QA process can be established, it is necessary to clearly and completely understand key criteria about the product that will be under test.

Purpose
The goal of the first phase of the process is to identify the scope and depth of the testing needs.

Methodology
The Assessment methodology includes a thorough product evaluation, review of critical documents, and interviews with key personnel as needed to extract, define and recommend the types and specific tests to be developed.


back to top


Definition

Overview
A clearly defined and well documented QA test plan and strategy is critical to assure that quality practices can be consistently and efficiently reproduced.

Purpose
During the Definition phase, requirements and design specifications are translated into test suites, test cases, and use case procedures.  Errors, observations, and anomalies are reported electronically throughout the process.  Online access to these findings as well as the supporting detailed test cases enables developers and engineering to pinpoint and fix issues quickly and easily, providing an immediate return on investment

Methodology
The methodology includes documenting the steps for each test case, including input criteria, parameters, boundaries, tolerances, conditions, and expected results.


back to top


Execution

Overview
Execution must be consistent and reproducible. Attention to detail, thorough documentation and substantiation of findings are all vital to the Execution phase.

Purpose
The Execution phase exercises the programs and systems through implementation of formal test procedures in order to identify and document defects.

Methodology
Clients transmit software or ship physical products to FTSC for testing. This can be in the form of a full release, patch, or a specific component or module that requires validation.

FTSC specialists work with clients to identify the test suites required to validate the product or component under test.   During testing, strict adherence to the test plan is maintained and all results and/or events are stringently documented to assure that the smallest detail can be reproduced. Both success and failure results are captured and articulated to our clients.


back to top


Evaluation

Overview
Formal test assessment is critical to clearly understand the cause of defects, flaws and failures. 

Purpose
The Evaluation phase is designed to help clients reduce the number of defects in their product through a thorough understanding of how and where defects are found and how to adequately retest fixes.

Methodology
Our methodology involves providing clients with timely, comprehensive test findings reports and online access to the detailed test plans used to identify and reproduce defects. This can include conference calls or face-to-face meetings in which defects can be reviewed and developers can discuss and understand where and how they occur.

When resolution of critical defects proves difficult, FTSC may host a Root Cause Analysis (RCA) to determine and understand the origin of a defect or recurring problem.

FTSC also offers a release assessment report and/or review to determine if the product or software under test meets acceptable release or compliance criteria.

Optionally, FTSC can extend formal version and release management services to clients.

At the end of any test cycle, FTSC will hold a project closeout to sign off on test cycle completion. This may be a 5 minute meeting or a half day preparation for a new version release, depending on clients needs.


back to top