Method and system for testing software

Abstract

The invention discloses a method and a system for testing software, wherein the method comprises the steps as follows: a. determining a normality level corresponding to a tested item according to a received normality level instruction from a user; b. obtaining a first test activity set corresponding to the normality level; obtaining test processes formed by the first test activity set; according to the test processes, testing the software; c. during test process, after finishing executing working elements, generating document elements corresponding to the working elements; and d. according toa test document, generating instruction, obtaining a previously selected document template corresponding to the test activity in the first test activity set; filling the generated document elements into the corresponding positions of the document template; and generating a test document and saving the test document. The method not only can be widely applied to testing various required software items, but also can automatically generate required documents according to practical requirements.

Description

technical field [0001] The invention relates to the technical field of computer data processing, in particular to a method and system for software testing. Background technique [0002] The work of software testing is to perform functional and non-functional testing of products according to the testing plan and process. At present, using testing tools to test is a very common method to improve testing efficiency and quality, and even write different testing tools according to needs, design and maintain Test management and assistance systems. In each stage of the test, the form of documents is generally used to describe and constrain the work that needs to be done in each link of the test and the results of the work. [0003] The existing test work management platform generally takes the control process as the core. On the basis of the control process, prepare corresponding documents to record the execution of the process, but this model does not solve the following problem...

AI Technical Summary

Problems solved by technology

[0004] (1) The software testing process is often different according to different test types, even for the same test, such as the same unit test or acceptance test, in different project personnel, different software development life cycles, and different software integrity In the case of different levels, the testing process and the output of the testing process have different requirements, and it is often difficult to meet the actual needs by adopting a unified testing process

[0005] (2) Insufficient planning and design sense in the process of writing documents, which affects the efficiency and quality of testing work

To ensure unified management of test documents at the organizational level, testers cannot flexibly change document templates according to existing resource conditions and test needs

[0007] (4) It is difficult to review whether the test cases meet the design specifications

[0008] (5) It is difficult to reuse the test cases of manual testing

Automated testing tools can alleviate this problem in specific cases, but for a fast iterative development process, a lot of manual testing is still required

Without the support of suitable devices, manually cross-calling test cases in the test procedure description is a huge workload, it is difficult to revise the version, and the readability is poor

Therefore, test cases are often compiled with relatively large granularity, only listing test points and describing the relationship between input and output, and the specific test data is often determined during test execution, so it is difficult to reuse test cases; and the same A set of test cases is executed by different people, and different test results may be caused due to different criteria for determining input and judging output on site

[0009] (6) It is difficult to perform regression testing accurately

As mentioned in (5), when the granularity of test cases is large, even two tests of the same software may not use the same set of input data, so it is difficult to perform regression testing accurately

[0010] (7) Documentation is difficult to guide test execution

In the process of executing the test, without the support of a suitable device, it is often difficult to track and control whether the test execution is performed according to the prepared document, and the phenomenon of "writing is written, and doing is done" appears

[0011] (8) It is difficult to record the test execution in time

In the process of executing the test, without the support of suitable devices, often the test is not recorded or only the key points are recorded, and it is recorded only after the test is over.

[0012] As mentioned in (7) and (8), when the test is performed by business personnel who are familiar with the application field, in order to achieve high efficiency in the test process, the above tendency will become more obvious, which is not conducive to the accumulation of test assets, and is not conducive to test design and Test execution is performed by different levels of personnel

Images