Найден интересный док по тестированию, так вот общий смысл конечно понятен, неясным остается как перевести Validation Testing & Verification testing. Эквивалента из отечественных ГОСТов не припомню
Идеи есть?
http://www.cs.scranton.edu/~dmartin/dsindex.html
3. Verification Testing
3.1. Unit Testing
For each unit in the SDD, there must be a test that the unit works properly. List each unit and the approach you will take to test it. The more specific this section is, the more valuable it will be to maintenance developers. (See note above.)
3.2. Integrative Testing
This section may be divided into several sections. The design of the project determines how many intermediate levels are distinct enough to rate a separate section here. Such levels are often called modules, components or sub-systems. Do not create levels to test just to make this section look impressive. (See note above.)
4. Validation Testing
4.1. System Testing
This is actually the top level of integrative testing. At this level, we validate requirements. We have fully described the needed behavior of the system in refer to the use cases in the SRS. We have then shown how our design provides realizations for these use cases in the SDD. Here we test each use case realization to make sure that it works as promised. (See note above.)
Use cases must also work in combination so we include sequences of use case tests to check on coordination. Again, give as explicit a set of tests as possible. This section may be divided into more sections if needed. (See note above.)
4.2. Acceptance and Beta Testing
List plans for acceptance testing and/or beta testing. (Exact terminology differs so be sure to define these terms in the Glossary.) This is testing with real data by the development team (acceptance testing) or the customer (beta testing). Tell how the results of such testing will be reported back and handled.