Test Strategy Best Practices By Gabriel Rodriguez.

Test Strategy

Best Practices

By

Gabriel Rodriguez

Copyright 2006-2007. MSQAA Federation Chapter.

Agenda

Test Strategy Test Strategy Case Study Q&A Reference


Test Strategy


Test Strategy

The objective of testing is to reduce the risks inherent in computer systems.

The strategy must address the risks and present a process that can reduce those risks.

The two components of the testing strategy are: – Test factors

The risk or issue that needs to be addressed as part of the test strategy.

– Test Phase The phase of the systems development life cycle in which

testing will occur.


Test Strategy

Not all the test factors will be applicable to all software systems. The development team will need to select and rank the test factors for the specific software system being developed.

Once selected and ranked, the strategy for testing will be partially defined.

The test phase will vary based on the testing methodology used. For example, the test phases in a traditional waterfall life cycle methodology will be much different from the phases in a Rapid Application Development methodology.


Test Strategy

Test Factors– The risk factors become the basis or objectives of

testing. The risks associated with testing will be called “test factors.” The test factors themselves are not risks, they are attributes of the software that, if they are wanted and not present, pose a risk to the success of the software, and thus constitute a business risk.


Test Strategy

The following list describes the test factors:– Correctness

Assurance that the data entered, processed, and output by the application system is accurate and complete.

– File Integrity Assurance that the data entered into the application

system will be returned unaltered.– Authorization

Assurance that the data is processed in accordance with the intents of management.


Test Strategy

The following list describes the test factors:– Audit Trail

The capability to substantiate the processing that has occurred. The process of saving the supporting evidential matter is called an audit trail.

– Continuity of Processing The ability to sustain processing in the event problems occur.

Assurance that the backup information are available to recover operations should integrity be lost due to problems.

– Service Levels Assurance that the desired results will be available with a time

frame acceptable to the user.


Test Strategy

The following list describes the test factors:– Access control

Assurance that the application system resources will be protected against accidental and intentional modification, destruction, misuse, and disclosure.

– Compliance Assurance that the system is designed in accordance with

organizational strategy, policies, procedures, and standards.– Reliability

Assurance that the application will perform its intended function with the required precision over an extended period of time.


Test Strategy

The following list describes the test factors:– Ease of Use

The extent of effort required learning, operating, preparing input for, and interpreting output from the system.

– Maintainability The effort required to locate and fix an error in an

operational system.– Portability

The effort required transferring a program from one hardware configuration and/or software system environment to another.


Test Strategy

The following list describes the test factors:– Coupling

The effort required to interconnect components within an application system and with all other application systems in their processing environment.

– Performance The amount of computing resources and code required by a

system to perform its stated functions.– Ease of Operation

The amount of effort required to integrate the system into the operating environment and then to operate the application system.


Test Strategy

Four steps must be followed to develop a customized test strategy:

– Select and Rank Test Factors The customers/key users of the system in conjunction with

the test team should select and rank the test factors. Only three to seven factors will be selected. These should be listed in the matrix in sequence from the most significant test factor to the least significant.

– Identify the System Development Phases The project development team should identify the phases

of their development process.


Test Strategy

Four steps must be followed to develop a customized test strategy:– Identify the Business Risks associated with the System under

Development The developers, key users, customers, and test personnel should

brainstorm the risks associated with the software system.The risks should then be ranked into high, medium, and low. One-third of all risks should be indicated as high; one-third, medium; one-third, low.

– Place Risks in the Matrix The risk team should determine the test phase in which the risk

needs to be addressed by the test team and the test factor to which the risk is associated.


Test Strategy Case Study


Test Strategy Case Study

Select and Rank Test Factors:


Test Strategy Case StudySystem Development Phases:


Test Strategy Case StudyIdentify Business Risks:


Test Strategy Case StudyPlace Risks in Matrix:


Q&A

Any questions…


Reference

CSTE Study Guide 2002 by QAI CSTE Study Guide 2006 by QAI


Thank you…

Test Strategy Best Practices By Gabriel Rodriguez.

Documents

Transcript of Test Strategy Best Practices By Gabriel Rodriguez.