Program and method of acceptance testing sample. Program and test procedure

G O S U D A R S T V E N N Y S T A N D A R T S O YU Z A S S R

Unified system of program documentation	GOST 19.301-79 (ST SEV 3747-82)

PROGRAM AND TESTING METHODS. REQUIREMENTS FOR CONTENT AND DESIGN

United system for program documentation. Program and methods of testing. Requirements for contents and form of presentanion.

Decree State Committee USSR according to the standards of December 11, 1979 No. 4753, the introduction period is set

from 01.01.1981

This standard establishes requirements for the content and design of the program document "Test Program and Methods", defined by GOST 19.101-77.

The standard fully complies with ST SEV 3747-82.

1. GENERAL PROVISIONS

1.1. The structure and design of the document is established in accordance with GOST 19.105-78.

Compilation of the information part (summary and content) is optional.

1.2. The document "Program and test methods" should contain the following sections:

test object;
the purpose of the tests;
program requirements;
requirements for software documentation;
composition and procedure for testing;
test methods.

Depending on the features of the document, it is allowed to introduce additional sections.

2.1. In the section "Test object" indicate the name, scope and designation of the test program.

2.2. In the section "Purpose of the test" the purpose of the test should be indicated.

2.3. In the section "Requirements for the program" the requirements to be verified during the tests and specified in the terms of reference for the program should be indicated.

2.4. The section "Requirements for software documentation" should indicate the composition of the software documentation for testing, as well as special requirements, if they are specified in the terms of reference for the program.

2.3, 2.4. (Revised edition, Rev. No. 2).

2.5, 2.6. (Deleted, Rev. No. 2).

2.7. The section "Tools and procedure for testing" should indicate the hardware and software used during the tests, as well as the procedure for conducting tests.

2.8. The Test Methods section shall provide descriptions of the test methods used. It is recommended to arrange test methods for individual indicators in the sequence in which these indicators are located in the "Program Requirements" and "Program Documentation Requirements" sections.

The test methods shall contain descriptions of the tests, indicating the results of the tests (test case lists, test case printouts, etc.).

2.7, 2.8. (Revised edition, Rev. No. 2).

2.9. The appendix to the document may include test cases, test case printouts, tables, graphs, etc.

* Reissue (November 1987) with Amendments No. 1, 2, approved in February 1982 (IUS 5-82, IUS 9-83)

The program and test procedure (PMI) is white paper, which formalizes the product testing stage and is compiled for an automated program (ACS) or system. The document is intended to identify the parameters that provide the definition of the causes of failure, indicators of the quality of the system, its compliance different requirements, checking and obtaining design solutions, and also characterize the duration and period of testing.

PMI directly determines the reliability of a system or subsystem, its compliance with the set requirements and the expected level of reliability. The program is compiled on the basis of the document RD 50-34.698-90 and it specifies all the checks that determine the effectiveness of this design solution.

A typical test program includes sections:

Test object. This indicates the scope, name and other information from the terms of reference that relate to the program under test.

The purpose of the test. The main purpose is to test the product and verify the characteristics of the program. In fact, the purpose of the test is considered to be the delivery of the project to the customer.

General provisions. The section includes the basis for testing, duration and place, a list is established required documents and participating organizations.

Scope of testing. It describes the stages and modes of testing, qualitative / quantitative parameters, as well as a list of work that should be carried out based on the test results.

Test tools. Description of all hardware and software tools that are used to conduct the test.

Test methods. The methods and techniques of checks that can be applied to the tested object are indicated.

Development of a program and test methodology

Our company is engaged in the development of PMI according to the design documentation or the technical specifications of the customer. A document of this type allows you to further identify the quality and effectiveness of the product. Therefore, the test program and methodology should be developed by experienced engineers. Design documentation and test programs in accordance with GOST are comprehensive documents.

Examination prototype includes the following steps:

Checking for compliance with the terms of reference.

Checking the package of related documents.

Determining the completeness of the program.

Checking the quality of documentation and software support.

Determining the qualifications of workers.

A program is a document containing organizational and methodological information about ongoing product research (object, goals and objectives, types and sequence, conditions and procedure, terms and place of testing, means and reporting procedure).
The test methodology is a generalized information about the methods, methods and techniques, conditions and means of conducting checks, algorithms for performing operations, forms of presenting information and assessing the reliability and accuracy of test results, security requirements environment and safety technology.
Taken together, the test program and methodology is the most important component document in the process of testing any product, usually equipment. This document defines the order of studies and how to evaluate their results.

Drawing up a program and test methodology

The process of developing a test program and methodology is based on technical and design documentation, similar programs and test methods used when testing similar types of products. A technical specialist should be involved in drawing up a program and test methods at enterprises, but, in his absence, it is advisable for management.
Quite often, the program and test methodology is required during the certification procedures, especially after the introduction into it. technical regulations Customs Union, which provide for mandatory product testing. In addition, Rostekhnadzor requires it to be provided during registration. Therefore, the preparation of a program and test methodology is becoming more and more mandatory and in demand.

Main elements of the program and test methods

The program and test methodology includes the following mandatory sections:
- general provisions(name and purpose of the object of study; purpose of testing; conditions for providing the object for testing; procedure for interaction between the contractor and the customer);
- General requirements to the conditions of testing, the conduct and provision of tests (place and means of testing, their list; personnel preparing and conducting tests; conditions for testing and preparing the product for testing);
- safety requirements (during the preparation of the object, testing, completion of tests);
- test program (test indicators and allowable measurement values are determined);
- test modes (test order, restrictions in test modes, conditions for interruption / cancellation / termination of tests);
- test methods (methods, techniques for conducting research, deriving results);
- reporting (documents drawn up based on test results, their content, purpose, storage period and recipients);
- Additional Information(applications, etc.)
The test program and methodology as a separate document should be drawn up for each type of product individually, since the products of production are different in their parameters and, therefore, the methods and methods of their verification should also be different.

You can get answers to all questions about the program and test methods simply or by filling out the form below.

Ask your question now

To formalize the process of testing the system in a set technical documentation include the Test Program and Methods (PMI) document. What exactly is causing this need?

Purpose of the program and test methodology

After the formation of the technical proposal, the moment comes when it is necessary to clearly define how the issue of the system's compliance with all the requirements described in project documentation how the degree of its reliability will be determined, and, most importantly, the level of suitability of the system for its intended purpose. This is exactly what the Test Program and Methods (PMI) document is intended for.

The composition of the standard program and test methods

PMI in accordance with GOST 19.301 should include the following sections:

– Test object. Here indicate the name of the system, its designation and scope.

– Purpose of testing. This section indicates the purpose of the tests, or goals, if there are several. Usually the main goal is to check the system for compliance with the requirements.

– Program Requirements. This lists the requirements described in terms of reference on the development of the system, compliance with which must be established.

– Requirements for software documentation. This section indicates the list of documents that must be presented by the time of testing, as well as special requirements for tests.

– Means and order of tests. Here is a list of hardware and software required for testing, as well as the procedure for conducting individual testing stages.

– Test Methods. In this section, it is necessary to describe the methods and methods of testing. Descriptions of checks are immediately given with indication of the results of the tests (lists of test cases, test printouts of test cases, etc.). The test cases themselves, graphs, diagrams, drawings, etc. for ease of use can be presented as attachments to the document.

Program Standards and Test Methods

The above scheme of the document according to GOST 19.301 is mandatory, and in the case of using GOST series 34, a different scheme should be used in accordance with RD 50-34.698. Also, we must not forget that the PMI, like any other document from the set of project documentation, must comply with the requirements of GOSTs for registration.