CN113094267B - Test result collection method and device - Google Patents

Abstract

The present invention can be used in the financial field or other fields. The present invention provides a test result collection method and device. The test result collection method includes: generating a listening class in the system according to the test logic corresponding to the test results to be collected; The class configures listening parameters in the system; and collects test results of the system according to the listening class and the listening parameters. The present invention enables testers to automatically report running results while executing automated test test cases in the IDE, and collect and register them in the database. By hooking up the relationship between scripts and cases, the invention can automatically analyze the actual execution status of project cases and reduce manual errors. Influence.

Description

A method and device for collecting test results

Technical field

The invention belongs to the field of big data technology, and specifically relates to a test result collection method and device.

Background technique

Automated testing, as the name suggests, automatically completes testing work. Specifically, some automated testing tools are used to simulate manual testing work and verify the results to complete the entire testing process. TestNG is a testing framework in JAVA and is a very popular and practical automated testing framework. Testers generally use IDE tools to write and execute automated test cases for the TestNg framework. After the execution is completed, the case status is manually updated based on the script execution status. The test manager mainly evaluates the project's testing progress based on the case execution status reported by the testers, and cannot accurately understand the execution results of the actual cases in a timely manner. It is easy for automated testing to fail, but project cases pass, which poses hidden dangers to project quality.

Contents of the invention

The test result collection method and device provided by the present invention have the following advantages: they are lightweight and only need to write a small amount of code to implement the logic code for registering and analyzing test results, and are suitable for use by test teams with weak R&D capabilities. Deployment is simple, just submit the tool to the git repository, the tester pulls the latest code and configures it in the IDE to complete the deployment. The collected test results are accurate and timely. By linking the automated test cases with the project test scenarios, the automated test results directly reflect the test progress of the project. The test manager can execute statistical logic at any time or regularly to understand the latest test conditions.

In order to solve the above technical problems, the present invention provides the following technical solutions:

In a first aspect, the present invention provides a test result collection method, including:

Generate listening classes in the system based on the test logic corresponding to the test results to be collected;

Configure monitoring parameters in the system according to the monitoring class;

Collect system test results according to the listening class and the listening parameters.

In one embodiment, generating a listening class in the system based on the test logic corresponding to the test results to be collected includes:

Use the testng tool listener to generate a listening class based on the test logic;

Set the monitoring class in the GIT repository;

In response to a listening class pull request from a distributed client, sending the listening class to a plurality of distributed clients.

In one embodiment, the test results of the collection system based on the listening class and the listening parameter include:

The test results are collected through the GIT repository.

In one embodiment, the test result collection method further includes:

Establish a mapping relationship between the test results and their corresponding test cases;

Determine the test progress according to the test results and the mapping relationship.

In a second aspect, the present invention provides a test result collection device, including:

The listening class generation module is used to generate listening classes in the system based on the test logic corresponding to the test results to be collected;

A listening parameter configuration module, configured to configure listening parameters in the system according to the listening class;

A test result collection module is used to collect test results of the system according to the listening class and the listening parameters.

In one embodiment, the monitoring class generation module includes:

The listening class generation unit is used to use the testng tool listener to generate the listening class according to the test logic;

A monitoring class setting unit is used to set the monitoring class in the GIT version library;

The listening class sending unit is configured to respond to the listening class pull request of the distributed client and send the listening class to multiple distributed clients.

In one embodiment, the test result collection module is specifically configured to collect the test results through the GIT repository.

In one embodiment, the test result collection device further includes:

A mapping relationship establishment module, used to establish a mapping relationship between the test results and their corresponding test cases;

A test progress determination module is used to determine test progress according to the test results and the mapping relationship.

In a third aspect, the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the steps of the test result collection method are implemented.

In a fourth aspect, the present invention provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the steps of the test result collection method are implemented.

As can be seen from the above description, the test result collection method and device provided by the embodiments of the present invention first generate a listening class in the system according to the test logic corresponding to the test results to be collected; then, configure the listening parameters in the system according to the listening class; and finally, according to the The monitoring class and monitoring parameters collect the test results of the system. Specifically, the present invention has the following beneficial effects:

1. It is lightweight and only requires writing a small amount of code to implement the logic code for registering and analyzing test results. It is suitable for testing teams with weak R&D capabilities.

2. Deployment is simple. You only need to submit the tool to the git warehouse, pull the latest code and configure it in the IDE to complete the deployment.

3. The collected test results are accurate and timely. By linking the automated test cases with the project test scenarios, the automated test results directly reflect the test progress of the project. The test manager can execute statistical logic at any time or regularly to understand the latest test situation. .

Description of the drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are: For some embodiments of the present invention, those of ordinary skill in the art can also obtain other drawings based on these drawings without exerting creative efforts.

Figure 1 is a schematic flow chart of a test result collection method in an embodiment of the present invention;

Figure 2 is a schematic flow chart of step 100 in the test result collection method in the embodiment of the present invention;

Figure 3 is a schematic flowchart of step 300 in the test result collection method in the embodiment of the present invention;

Figure 4 is a schematic flow chart 2 of a test result collection method in an embodiment of the present invention;

Figure 5 is a schematic structural diagram of a test result collection system in a specific application example of the present invention;

Figure 6 is a schematic flow chart of a test result collection method in a specific application example of the present invention;

Figure 7 is a block diagram 1 of the structure of the test result collection device in the embodiment of the present invention;

Figure 8 is a structural block diagram of the monitoring class generation module 10 in the embodiment of the present invention;

Figure 9 is a block diagram 2 of the structure of the test result collection device in the embodiment of the present invention;

Figure 10 is a schematic structural diagram of an electronic device in an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments These are some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without making creative efforts fall within the scope of protection of the present invention.

Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

It should be noted that the terms "comprising" and "having" and any variations thereof in the description and claims of this application and the above-mentioned drawings are intended to cover non-exclusive inclusion, for example, a series of steps or units. The processes, methods, systems, products or devices are not necessarily limited to those steps or units expressly listed, but may include other steps or units not expressly listed or inherent to the processes, methods, products or devices.

It should be noted that, as long as there is no conflict, the embodiments and features in the embodiments of this application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and embodiments.

The embodiment of the present invention provides a specific implementation of a test result collection method. Refer to Figure 1. The method specifically includes the following content:

Step 100: Generate a listening class in the system based on the test logic corresponding to the test results to be collected.

First introduce related terms:

TestNg: open source automated testing underlying framework

IDE (Integrated Development Environment): an application used to provide a program development environment. It integrates code writing functions, analysis functions, compilation functions, debugging functions and other integrated development software service suites. All those with this feature Software or software suites can be called integrated development environments. (This patent mainly uses Eclipse software as an example)

GIT: an open source distributed version control system that can handle version management of small to very large projects efficiently and at high speed

When implementing step 100, you can reference the testng tool listener and write a listening program to automatically trigger the registration of execution result information into the database after the automated test script is run. The monitoring program can be triggered by configuring relevant parameters in the system under test without the need for testers to modify their own script code.

In addition, it is understandable that a class is a reference data type, similar to basic data types such as byte, short, int (char), long, float, double, etc. The difference is that it is a complex data type. Because its essence is a data type, not data, it does not exist in memory and cannot be directly manipulated. It only becomes operable when it is instantiated as an object. If the data types provided in a program directly correspond to the concepts in the application, the program will be easier to understand and easier to modify. A well-chosen set of user-defined classes makes programs cleaner. Additionally, it makes various forms of code analysis easier to perform. In particular, it would also make it possible for the compiler to check for illegal uses of objects. The class encapsulates properties and methods internally, which are used to operate its own members. A class is the definition of a certain object and has behavior. It describes what an object can do and the methods to do it. They are programs and processes that can operate on this object. It contains information about how an object behaves, including its name, properties, methods, and events. The composition of a class includes member attributes and member methods (data members and member functions). Data members correspond to attributes of a class. Data members of a class are also a data type and do not require memory allocation. Member functions are used to operate various attributes of the class, which are unique operations of a class. The monitoring class in step 100 refers to the class used to monitor other programs.

Step 200: Configure monitoring parameters in the system according to the monitoring class.

It should be noted that the system in step 200 refers to the monitored system. Preferably, the system can be an IDE environment (Integrated Development Environment, integrated development environment), which is an application program used to provide a program development environment and integrates code An integrated development software service suite with writing functions, analysis functions, compilation functions, debugging functions, etc. All software or software packages with this feature can be called integrated development environments.

Step 300: Collect system test results according to the listening class and the listening parameters.

Specifically, when the test results of the system under test are generated, the listening parameters in step 300 will be triggered, and the listening class will collect the test results at this time, thereby achieving the purpose of collecting the test results.

As can be seen from the above description, the test result collection method provided by the embodiment of the present invention first translates the workflow model to be tested into an executable preliminary test script; then, adds test assertions to the test script to generate a final test script. ;Finally execute the final test script and compare the execution results with the expected values. The present invention enables testers to automatically report running results while executing automated test test cases in the IDE, and collect and register them in the database. By hooking up the relationship between scripts and cases, the invention can automatically analyze the actual execution status of project cases and reduce manual errors. Influence.

In one embodiment, referring to Figure 2, step 100 includes:

Step 101: Use the testng tool listener to generate a listening class based on the test logic;

The testng tool listener is an open source automated testing framework. TestNG is designed to be used for various types of testing: unit testing, functional testing, end-to-end testing, and integration testing. The testng tool listener has the following characteristics:

Support Java annotation function;

Tests run in an arbitrarily large thread pool, with multiple running strategies to choose from (all test methods run in their own thread, one thread per test class, etc.);

Thread safety;

Flexible test configuration;

Support data-driven testing;

Support parameterization;

Powerful operating model;

Supported by a variety of tools and plug-ins;

Embedded BeanShell to further enhance flexibility;

The runtime and logging functions of JDK are provided by default;

Provides methods for application server testing dependencies.

Step 102: Set the monitoring class in the GIT repository;

The GIT repository can be simply understood as a directory. All files in this directory can be managed by GIT. Git can track the modification and deletion of each file, so that the history can be tracked at any time, or at some point in the future. Can be "restored".

Step 103: In response to the listening class pull request of the distributed client, send the listening class to multiple distributed clients.

Specifically, the latest code is pulled through the GIT client tool, and the relevant code will be deployed to the local machine of each tester.

In one embodiment, referring to Figure 3, step 300 includes:

Step 301: Collect the test results through the GIT repository.

In one embodiment, referring to Figure 4, the test result collection method further includes:

Step 400: Establish a mapping relationship between the test results and their corresponding test cases;

Step 500: Determine the test progress according to the test results and the mapping relationship.

In steps 400 and 500, first establish an association (mapping relationship) between the test case and the test script, then analyze the running details of the automated test script within the project cycle, and finally count the project test progress.

In order to further illustrate this solution, the present invention also takes Eclipse as an example to provide a specific application example of the test result collection method.

This specific application example also provides a test result collection system, see Figure 5. The system includes: an automatic trigger collection and reporting automated test execution module 1; an analysis project test progress module 2. specifically:

Automatically trigger collection and report to automated test execution module 1: The automated test project is managed in the GIT repository. Each tester submits and pulls the test script code through the GIT client. The automated test project references the testng tool listener and writes a listener. A class program that automatically triggers the registration of execution result information into the database when the automated test script is finished running. The monitoring program can be triggered by simply configuring relevant parameters in the IDE, without the need for testers to modify their own script code.

Analyze project test progress module 2: Analyze project test progress based on the script execution details registered in the database.

Referring to Figure 6, based on the test result collection system, the test result collection method provided in this specific application example specifically includes the following steps:

It is understandable that Eclipse is an open source, Java-based extensible development platform. Is a framework and a set of services for building development environments through plug-in components.

S101: Write a listening class and collect test result logic in the automated test project: Under the automated test project, write a TestNG listening class to automatically trigger the collection function when executing the TestNG case.

S102: Submit the code for the listening class and collection of test results to the GIT repository.

S103: Use the GIT client tool to pull the latest code and deploy the relevant code to the local machine of each tester.

S104: Configure the TestNG plug-in in the IDE to start the listening class.

S105: Collect the results of automated test cases executed by the local IDE.

S106: Associate test cases with test scripts.

S107: Analyze the running details of automated test scripts during the project cycle.

S108: Statistics of project test progress.

To sum up, in the existing technology, testers mainly execute automated test scripts in the local eclipse software, and then manually update the case status after the execution is completed, while the test manager mainly evaluates the test progress of the project based on the tester reports, which cannot be timely and accurate. Understand the execution results of actual cases. As can be seen from the above description, the test result collection method and device provided by the embodiments of the present invention first generate a listening class in the system according to the test logic corresponding to the test results to be collected; then, configure the listening parameters in the system according to the listening class; and finally, according to the The monitoring class and monitoring parameters collect the test results of the system.

Based on the same inventive concept, the embodiment of the present application also provides a test result collection device, which can be used to implement the method described in the above embodiment, such as the following embodiment. Since the problem-solving principle of the test result collection device is similar to that of the test result collection method, the implementation of the test result collection device can be referred to the implementation of the test result collection method, and repeated details will not be repeated. As used below, the term "unit" or "module" may be a combination of software and/or hardware that implements predetermined functions. Although the systems described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

The embodiment of the present invention provides a specific implementation of a test result collection device that can implement a test result collection method. Referring to Figure 7, the test result collection device specifically includes the following content:

The listening class generation module 10 is used to generate listening classes in the system according to the test logic corresponding to the test results to be collected;

The monitoring parameter configuration module 20 is used to configure monitoring parameters in the system according to the monitoring class;

The test result collection module 30 is used to collect test results of the system according to the listening class and the listening parameters.

In one embodiment, referring to Figure 8, the monitoring class generation module 10 includes:

The listening class generation unit 101 is used to use the testng tool listener to generate a listening class according to the test logic;

The monitoring class setting unit 102 is used to set the monitoring class in the GIT version library;

The listening class sending unit 103 is configured to respond to a listening class pull request from a distributed client and send the listening class to multiple distributed clients.

In one embodiment, the test result collection module 30 is specifically configured to collect the test results through the GIT repository.

In one embodiment, referring to Figure 9, the test result collection device further includes:

Mapping relationship establishment module 40 is used to establish a mapping relationship between the test results and their corresponding test cases;

The test progress determination module 50 is used to determine the test progress according to the test results and the mapping relationship.

As can be seen from the above description, the test result collection device provided by the embodiment of the present invention first translates the workflow model to be tested into an executable preliminary test script; then, adds test assertions to the test script to generate a final test script ;Finally execute the final test script and compare the execution results with the expected values. The present invention enables testers to automatically report running results while executing automated test test cases in the IDE, and collect and register them in the database. By hooking up the relationship between scripts and cases, the invention can automatically analyze the actual execution status of project cases and reduce manual errors. Influence.

Referring now to FIG. 10 , a schematic structural diagram of an electronic device 600 suitable for implementing embodiments of the present application is shown.

As shown in FIG. 10 , the electronic device 600 includes a central processing unit (CPU) 601 that can be configured according to a program stored in a read-only memory (ROM) 602 or loaded from a storage portion 608 into a random access memory (RAM) 603 program to perform various appropriate tasks and processes. In the RAM 603, various programs and data required for the operation of the system 600 are also stored. CPU601, ROM602, and RAM603 are connected to each other through bus 604. An input/output (I/O) interface 605 is also connected to bus 604.

The following components are connected to the I/O interface 605: an input section 606 including a keyboard, a mouse, etc.; an output section 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., speakers, etc.; and a storage section 608 including a hard disk, etc. ; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. Driver 610 is also connected to I/O interface 605 as needed. Removable media 611, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memories, etc., are installed on the drive 610 as needed, so that computer programs read therefrom are installed as needed in the storage portion 608.

In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present invention include a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned method for determining the distance between persons in a data computer room scenario are implemented. The steps include:

Step 100: Generate a listening class in the system based on the test logic corresponding to the test results to be collected;

Step 200: Configure monitoring parameters in the system according to the monitoring class;

Step 300: Collect system test results according to the listening class and the listening parameters.

In such embodiments, the computer program may be downloaded and installed from the network via communication portion 609, and/or installed from removable media 611.

Each embodiment in this specification is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the hardware + program embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment.

The foregoing describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desired results. Additionally, the processes depicted in the figures do not necessarily require the specific order shown, or sequential order, to achieve desirable results. Multitasking and parallel processing are also possible or may be advantageous in certain implementations.

For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing this application, the functions of each unit can be implemented in the same or multiple software and/or hardware.

The invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for realizing the functions specified in one process or multiple processes of the flowchart and/or one block or multiple blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

It should also be noted that the terms "comprises," "comprises," or any other variation thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements not only includes those elements, but also includes Other elements are not expressly listed or are inherent to the process, method, article or equipment. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of other identical elements in a process, method, good or device that includes that element.

Each embodiment in this specification is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the partial description of the method embodiment.

The above are only examples of the present application and are not used to limit the present application. To those skilled in the art, various modifications and variations may be made to this application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this application shall be included in the scope of the claims of this application.

Claims (4)

1. A test result collection method, comprising:

generating a monitoring class in the system according to the test logic corresponding to the test result to be collected;

configuring monitoring parameters in the system according to the monitoring class;

collecting test results of a system according to the monitoring class and the monitoring parameters;

establishing a mapping relation between the test result and the corresponding test case;

determining a test progress according to the test result and the mapping relation;

the generating a monitoring class in the system according to the test logic corresponding to the test result to be collected comprises the following steps:

generating a monitoring class according to the test logic by using a testng tool monitor;

setting the monitoring class in a GIT version library;

responding to a monitoring class pulling request of a distributed client, and transmitting the monitoring class to a plurality of distributed clients;

the test results according to the monitoring class and the monitoring parameter collecting system comprise:

and collecting the test result through the GIT version library.

2. A test result collection device, comprising:

the monitoring class generating module is used for generating a monitoring class in the system according to the test logic corresponding to the test result to be collected;

a monitoring parameter configuration module, configured to configure monitoring parameters in the system according to the monitoring class;

the test result collection module is used for collecting test results of the system according to the monitoring class and the monitoring parameters;

the mapping relation establishing module is used for establishing a mapping relation between the test result and the corresponding test case;

the test progress determining module is used for determining the test progress according to the test result and the mapping relation;

the monitoring class generating module comprises:

a monitoring class generating unit, configured to generate a monitoring class according to the test logic by using a testng tool monitor;

a monitoring class setting unit, configured to set the monitoring class in a GIT version library;

a monitoring class sending unit, configured to respond to a monitoring class pulling request of a distributed client, and send the monitoring class to a plurality of distributed clients;

the test result collection module is specifically configured to collect the test result through the GIT version library.

3. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the test result collection method of claim 1 when the program is executed by the processor.

4. A computer readable storage medium having stored thereon a computer program, characterized in that the computer program when executed by a processor implements the steps of the test result collection method of claim 1.