Interface test related document management specification

3.1 Testing the document scope
The types of documents that the interface Automation test primarily needs to manage are as follows:
Interface Description document, test case document, test report (Result) document, test script (JMX type), meeting minutes, review document, and other test related documents.
3.2 Test Document creation instructions
documentation for the requirements class (e.g. interface documentation) is provided to testers at the initial stage of the test, where the tester writes the use case according to the interface documentation, where the documentation is not standardized and requires timely feedback to the development, urging modification of the interface documentation that provides the specification.
The test case documentation is that after the tester has taken the interface documentation, the understanding of the requirement begins to write the document, and the test case document is continually optimized for review at a later stage. Once the test case document has been written, you can begin the preparation of the test script, which is based on the test case documentation.
A test script is a test output that is formed during a test run by a tester that requires scripting to conform to the scripting specifications under the document, which facilitates later script maintenance and management.
Test report document is the tester after the completion of the test, the test results of a summary report, the requirements of the company provided by the specification template written, and submitted to the Test leader audit, audit error to the corresponding product or project development, business, leadership and other relevant personnel.
Documents such as meeting minutes, review documents, etc. are generated throughout the testing process according to the needs of the project, which can be grouped into a requirements document and used as a guide and specification for testers ' testing work.
3.3 Test document archiving requirements
After the test task is finished, the testers need to tidy up all the relevant test documents and upload them to the SVN server's corresponding directory. The test assets that form the entire test group. Each tester is required to attach importance to this link, and all test documents must be archived at the end of the test.
It is strongly recommended that test teams in each region have their own SVN management catalog, testers who complete the project or product test, because the product or project has its own SVN catalog, and during the test, the development manager will also require test documents such as test cases, test reports, etc. to be uploaded to the SVN of the corresponding project. But after the test, the tester will also need to complete the final Test related documents (interface description document, test case document, test report (Result) document, test script (JMX type), meeting minutes, review documents, etc.) by type to the SVN management directory under their own test group, so that the test document is controlled by the management of the test group To form the test group's own assets.
The following is an example of the test document archiving requirements for the Beijing Test group, which can be referenced by other local test groups to organize the archived test documents according to their own projects.