Software Testing, Thales Training Consultancy

SOFTWARE TESTING

Duration:

2 days (In-Company or Customised Course only)

Price:

On Request

Locations Available:

Suitable For

This course is aimed at software engineers, programmers, quality engineers, project leaders and staff about to assume responsibility for running an independent test team. It is recommended that delegates should have experience of software system development.

The course introduces the many techniques available for the identification of test cases and test data and how and when to apply them. Static analysis techniques are also covered in the course.

Objectives

By the end of the course delegates will be able to:·

Define the terms: verification, validation, dynamic test and explain the associated goals, capabilities and limitations.
Relate the VV&T activities to each phase of the software development lifecycle. ·
Use a four stage strategy to construct an optimal set of unit test cases.·
Explain the different strategies for integrating software and identify the strengths and weaknesses of each. ·
Use a structured approach to establishing integration tests. ·
Describe and use some static analysis techniques.·
Explain the importance of measuring V,V&T achievement and effectiveness and describe some specific metrics.·
Describe the features, strengths and limitations of the different categories of CAST tools available to support the V,V&T activities.

Course content

Introduction·

Causes of software defects·
Techniques available for avoiding software defects·
Verification, validation, & test·
The goals of V,V&T ·
Applicability of these activities through the lifecycle

General Approach To Software Testing·

The mechanics of testing·
‘Black box’ and ‘White box’ test approaches·
The economics of test case selection·
Recommendations appropriate to any software testing activityUnit

Test Case Development·

A four-stage strategy for the construction of test cases
Equivalence class partitioning and data boundary analysis
Function boundary analysis·
Error guessing·
Test coverage criteria ·
Characteristics of a good test environment·
Predicting test results ·
Checking test results·
Instrumentation ·
Data and control logging·
The implications of doing or not doing unit testing

Integration And Integration Testing·

Why integration testing is necessary·
Principles and disciplines relating to the phased build up of a total system ·
Establishing criteria for the integration test phases.·
Top Down, Bottom Up, Big Bang and other integration strategies·
The development sequence·
The system integration programme and its impact on the software integration (build) plan and build control. ·
The integration (build) plan

Integration Test Cases·

Identifying software-software and software-hardware integration test cases ·
Potential scope of integration test cases ·
Hardware and software environment for integration testing·
Controlling the S/W - H/W testing environment·
Testing documentation ·
Test information logging ·
Checking test results

Other Tests·

Testing changes ·
Regression testing·
Program mutation testing ·
Acceptance testing·
Acceptance test plans, specifications and schedules ·
Running acceptance tests·
Post acceptance test actions

Static Analysis And Symbolic Execution·

Control flow analysis·
Data flow analysis·
Symbolic execution

Reviews·

Different types of review and their relationship to dynamic testing

Tools·

The types of CAST tools to support V,V&T activities·
Advantages and potential problems with tools

Other Aspects·

Test plans, specification and schedules ·
Logging test activities·
Test results·
Communications·
Reports, test incidents, test summaries and test status·
Test certification·
The importance of metrics for monitoring and control V,V&T ·
Configuration management applied to V,V&T ·
Post course action