Structured testing in practice

Table of Contents

1 Introduction

2 General aspects of software development processes

2.1 Software development models

2.1.1 Waterfall-Model

2.1.2 V-Model

2.1.3 W-Model

2.1.4 eXtreme Programming (XP)

2.1.5 Conclusion

2.2 Quality factors and approaches

2.2.1 Capability Maturity Model Integration(CMMI)

2.2.2 Testing Maturity Model (TMM)

2.2.3 Test Process Improvement (TPI)

2.2.4 Comparison of TMM and TPI

2.2.5 Conclusion

3 Testing specific aspects of software development processes

3.1 The objectives and limits of testing

3.2 The Test plan

3.2.1 Strategical parts of the test plan

3.3 Test plan defined in IEEE 829

3.3.1 Test plan identifier

3.3.2 Introduction

3.3.3 Test items

3.3.4 Features to be tested

3.3.5 Features not to be tested

3.3.6 Approach

3.3.7 Item pass/fail criteria

3.3.8 Suspension criteria and resumption requirements

3.3.9 Test deliverables

3.3.10 Testing tasks

3.3.11 Environmental needs

3.3.12 Responsibilities

3.3.13 Staffing and training needs

3.3.14 Schedule

3.3.15 Risks and contingencies

3.3.16 Approvals

4 Concrete implementation of structured testing in a company

4.1 The starting point

4.2 Analysis of the current test activities

4.2.1 Test maturity matrix of testing at the starting point

4.3 The way to structured testing

4.3.1 The Test Browser

4.3.2 Storage management

4.3.3 Archiving process

4.3.4 Test automation

4.3.5 Test database

4.3.6 Build management

4.3.7 QaTraq - A web based software test case management tool

4.4 Conclusion

Objectives and Topics

This thesis aims to demonstrate the successful implementation of a structured test process within a company. The central research objective is to transition from unstructured, ad-hoc testing to a managed, efficient, and automated environment using established quality models and tools, thereby improving product quality and reducing development costs.

• Comparison of software development and quality maturity models (CMMI, TMM, TPI).
• Analysis of current test activities and identification of process weaknesses.
• Implementation of automated testing frameworks (Perl, Squish, Unit tests).
• Establishment of a centralized web-based management platform (Test Browser, QaTraq).
• Optimization of storage, archiving, and build management processes.

Excerpt from the Book

Summary of Chapters

1 Introduction: Summarizes the necessity of structured software testing to ensure quality and control costs in IT projects.

2 General aspects of software development processes: Explains software development models and quality approaches like CMMI, TMM, and TPI to measure and improve test process maturity.

3 Testing specific aspects of software development processes: Discusses the inherent limits of exhaustive testing and details the structure of a professional test plan according to IEEE 829.

4 Concrete implementation of structured testing in a company: Details the practical transition to a structured, automated test environment, including test automation, build management, and test case management via QaTraq.

Keywords

Software testing, structured testing, TPI, TMM, CMMI, test automation, build management, IEEE 829, test plan, quality assurance, software development lifecycle, QaTraq, Perl testing, Squish, unit testing

Frequently Asked Questions

What is the core focus of this thesis?

The thesis focuses on transforming unstructured, ad-hoc testing practices into a systematic, structured, and partially automated test process within a specific corporate environment.

Which quality models are central to this research?

The work primarily explores the Capability Maturity Model Integration (CMMI), the Testing Maturity Model (TMM), and the Test Process Improvement (TPI) model.

What is the primary goal of the implemented test process?

The goal is to improve the measurable quality of software products while optimizing the time and budget allocated to testing activities.

Which scientific methodology is applied?

The author uses a maturity assessment approach, identifying existing process gaps using TPI, followed by a targeted, step-by-step implementation of improvements and automation.

What topics are covered in the main section?

The main part covers the analysis of initial testing weaknesses, the implementation of automated testing frameworks, the setup of a web-based Test Browser, and the deployment of a test management tool (QaTraq).

What characterizes the keywords used in this work?

The keywords reflect the intersection of software quality assurance, process improvement frameworks, and practical automation tools for software testing.

How does the author verify the effectiveness of the changes?

Effectiveness is verified through the Test Maturity Matrix, which maps the improvements achieved over a one-year period in various key areas of the test process.

How does the thesis handle the limitation of software testing?

It explicitly acknowledges that complete testing of software is mathematically and practically impossible, thus emphasizing risk-based testing and the prioritization of critical software components.

How is the Test Browser utilized in the company?

It serves as a centralized, web-based platform that provides developers and testers with immediate access to test results, build reports, manuals, and metrics from any location.