INTEGRATION AND SYSTEM TESTChapter 9

CONTENTS

Testing Principles The TSPi Testing Strategy Build and Integration Strategy System Test Strategy Test Planning Tracking and Measuring Testing Documentation The Test Process

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

In TSPi, the purpose of testing is to assess the product and not to fix it. You should have found and fixed

almost all the defects before the testing phase.

The quality of a product is determined when it is developed. When you put a poor-quality product

into test, you generally get a poor-quality product out of test.

Testing Principles

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

Build the System Using the developed and unit-tested parts, build

the system Integration Test

Integration-test the system to verify that it is properly built, that all the parts are present, and that they function together

System Test System-test the product to validate that it does

what the system requirements call for； Regression Test

In subsequent cycles, regression tests are also needed to ensure that the development work for this cycle has not unintentionally changed the functionality or performance produced in prior cycles.

TSPi Testing Strategy

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

The purpose of the build process is to ensure that all needed parts are present, to assemble a working system, and to provide this system to integration and system test.

Integration testing should merely check that all the components are present and that all their calls and other interactions work. You should not test the

components’ functions.

Build & Integration Strategy

You should not test the components’ functions.

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

Put all the parts together and see whether they work.

Advantage: it requires the least amount

of test development；

Disadvantage: it is rarely successful, particularly with

poor-quality systems.

Build & Integration StrategyBig-Bang Strategy

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

Put all the parts together and see whether they work.

Advantage: With each addition, you look for problems with the newly added parts

Disadvantage: This strategy requires more test development work.

Build & Integration StrategyThe One-at-a-time Strategy

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

This strategy is to add parts in clusters.

You identify a class of related components and integrate them.

Build & Integration StrategyThe Cluster Strategy

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

This strategy is to integrate all the highest level parts first and then delve down into successive system layers in parallel. You identify a class of related components and integrate them.

Advantage: You can detect system-wide issues early；

Disadvantage: it usually requires large numbers of stubs or special scaffolding

to provide dummy returns for all the functions that are not yet

available.

Build & Integration StrategyThe Flat-system Strategy

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

Firstly, test each of the system’s intended functions

Check operation under stress conditions, evaluate usability

Finally, measure performance.

System Test StrategyThe Function-first Strategy

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

Cover all aspects of each functional area before moving to the next functional area.

You might start by testing Numerical calculations for normal and

adverse operation； Usability Performance Quality

System Test StrategyThe Functional Area Strategy

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

Test lower level functions for normal, abnormal and stress behavior；

Move to the next higher level and test functional aggregates to ensure that they work together. Check them under various normal and stress conditions；

Continue testing at progressively higher levels until you have covered the full system.

System Test StrategyCombining the Preceding-two Strategy

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

Test the highest level functions and work down, doing normal and stress tests

System Test StrategyReversing the Preceding Strategy

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

The completed testing plan should have…

A list of all the testing steps to be performed

The supporting materials required for each test

The results that the tests are to produce An estimate of the defect-free run time,

the defects to be found, and total time for each test

An estimate of the work required to develop each item in the test plan.

Test Planning

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

The test log (LOGTEST FORM) contains a summary of the tests run and the results obtained

With the test log data, you can readily determine which tests were run and which found the most defects

You can also determine the test run time and the defects found per testing hour

Data from this log can help you select the most efficient strategy for regression-testing modified programs

Tracking and Measuring Testing

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

In the TSPi test phase, part of the team drafts and reviews the user documentation while the rest of the team conducts the tests.

A well-designed manual should be organized around the reader’s needs and not the product’s structure. Generally The first section should address what the

user needs to know first: how to get started Next, you might explain what the user can

do with the product Finally, make it easy for people to find what

they want to know.

Documentation

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

Writing Style Write short sentences； Use simple words and phrases； Use lots of lists and bulleted items.

Documentation

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

Document Review Document Organization Document Terminology Document Content Accuracy Readability Understandability

Documentation

Testing PrinciplesThe TSPi Testing StrategyBuild and Integration Strategy System Test StrategyTest PlanningTracking and Measuring TestingDocumentationThe Test Process

The Test Process

http://casper.cii.saxion.nl/se/SEscripts/test.html

22

Test Scripts

Test script includes: Develop build, integration test, and system

test procedures Determine size, time, and materials needed

for each test Build the product Conduct integration testing Conduct system testing

From Glenn Booker INFO 637

23

Test Scripts

Produce user documentation, review and fix it

Outputs include An integrated and tested product for this

cycle Completed LOGD and LOGTEST forms for

all tests Completed user documentation Time, size, and defect data in TSP system

Have a nice day!