INF3121: Lesson two

Testing throughout the software life cycle

1. Software development models

Sequential development model (The V-model)

- Testing needs to begin as early as possible in the life cycle. 

- Testing can be integrated into each phase of the product life cycle. 

- The V model (sequential development model), testing especially takes place in the early stages, and late in the life cycle.

The interactive-incremental development is the prosess of: 

- establishing requirements
- designing
- building
- testing a system
(Done as a series of shorter development cycles)

- An increment, added to others developed previously, forms a growing partial system, which should also be tested.

- Regression testing is increasingly important on all iterations after the first one.

Testing within a lifecycle model:

- In any life cycle model, there are several characteristics of good testing:

- Test levels can be combined or reorganized depending on the nature of the project or the system architecture.

2. TEST LEVELS

Component testing

Component testing includes testing of functionality and specific non-functional characteristics, such as: resource behavior, robustness testing and structural testing.

Integration testing

It tests:

- interfaces between components

- interaction with different parts of a system, such as: the operating system, file system, hardware, interfaces between components.

System tests

Testing the behavior of the whole system as defined by the scope of the project.

Acceptance testing

To establish confidence in the system/part of system/non-functional characteristics of the system.

3. TEST TYPES

Learning goals: Compare the following test type: fictional, non-functional, structural and change related.

Fuctional testing (black box testing)

What the system does:

Suitability
Interoperability
Security
Accuracy
 Compliance

Non-functional testing

How the system works

Performance, load, stress

Reliability

Usuability

Efficiency

Maintainability

Portability

Related to change

Confirmation testing

Regression testing

Structural

Code coverage

4. MAINTANCE TESTING

Maintance testing is done on an existing operational system, and is triggered by modifications, migration, or retirement of the software or system.