Home / Projects / Quality assurance

Quality Assurance

Table of contents

  1. General
  2. What we do
    1. Testing
    2. Coding Rules
    3. Reviews
    4. Tools

1. General

2. What we do

See the QA WIKI page for the latest news.

2.1 Testing Code

See the Testing Wiki page for the latest news.

This table describes different types of tests
Unit Testing Also known as component testing and class testing. A class is tested "in vitro". In the "bottom-up" testing model, unit testing is the lowest level. All the functions should be tested for all possible input values (i.e. using data especially generated for the tests).
Integration Testing Integration is carried out when all the sub systems have been individually tested. these tests should be designed to find errors which result from unforseen interactions between components. The tests should be designed to demonstrate that all the functions specified in the requirements have been implemented.
Regression Testing Regression testing must be carried out when a modification has been made to a previously working system. It is not sufficient to retest the component which has been modified. Regression testing makes sure that the results obtained by a system are the same as those at some previous time, or if they are not the same, then the reason is understood.

2.2 C++ coding standards

2.3 Reviews

See Archives of ATLAS SW reviews.

What is a review? The Philosophy (and Psychology) of Software Reviews

2.4 Tools

We no longer provide support for any tools, but here are some notes on tools which tools users may find helpful for code management and testing.

See also

Other ATLAS software QA pages

Other experiments

Further Reading

↑ Top