1

Introduction to acceptance testing

• What is software testing and acceptance?
• The difficulties of testing and noncompliance.
• Tester psychology.
• Test players: Acceptance manager, tester, automation engineer, ergonomist, etc.
• Functional testing.
• The concept of “V&V”, verification and validation.
• Types of tests.
• The notion of test coverage.

2

The project context

• Understanding roles within the project (project owner, lead contractor, acceptance team, users).
• The project lifecycle: Traditional and Agile modes.
• The various processes.
• The deliverables (technical and functional specifications, acceptance plan, testing, etc.).
• Requirements (typology, quality criteria).

3

The approach to acceptance testing

• The acceptance process and its interactions.
• The steps of the acceptance approach (synoptics).
• Acceptance in the project schedule.
• Versioning.
• Non-regression tests.

4

Managing tests and non-compliances

• The principles and practices of test management.
• Test reference spaces, functions. Market tools.
• Test architecture.
• Principles of non-compliance management.
• Anomaly managers, principles and market solutions.
• Test configuration management (principles and practices).

5

Test design

• Design principles.
• The course of design.
• Traceability of requirements and tests.
• Techniques of partitioning or defining "equivalence classes".
• “Limit testing” techniques.
• Decision tables or defining input-output combinations.
• Cause-effect graphing. Finite state graphing.
• Non-functional testing techniques (ergonomics, usability, performance, etc.).
• Covering test objectives.

6

Implementing tests

• Principles and conditions of implementation.
• Providing functional specifications.
• Testing platforms
• Manual testing.
• Test campaigns, databases.
• Test data generators.
• Automated testing: Principles, benefits, and drawbacks.
• Functional test robots (overview).
• Peer review of tests.

7

Executing tests

• Preparing the campaign.
• Delivery of the version being tested and its documentation.
• Conducting the tests.
• Recording the results and anomalies.
• Corrective/upgrading versions (Change Control Board CCB).
• Consolidating the results.
• Stopping and acceptance criteria (Go/No go).
• The acceptance report.