WO2017177783A1

WO2017177783A1 - Test system and method invoking third-party test tool

Info

Publication number: WO2017177783A1
Application number: PCT/CN2017/076694
Authority: WO
Inventors: 卫伟; 姬丽娜; 张家明
Original assignee: 中兴通讯股份有限公司
Priority date: 2016-04-11
Filing date: 2017-03-15
Publication date: 2017-10-19
Also published as: CN107291611A

Abstract

Disclosed is a test system invoking a third-party test tool, comprising: a task information acquisition module, configured to acquire test task information submitted by a user and save same in a preconfigured database; a task management module, configured to acquire the test task information saved in the database and send same to a client agent module; the client agent module, configured to send, after receiving the test task information, test parameters carried in the test task information to a corresponding invoking module according to information about a third-party test tool carried in the test task information; and the invoking module, configured to invoke, after receiving the test parameters, the third-party test tool to implement the test task based on the test parameters. Also disclosed is a test method invoking a third-party test tool. According to the present invention, various third-party tools can be invoked via a platform to implement tests, thereby realizing a convenient and efficient test approach.

Description

Test system and method for invoking third party testing tools

Technical field

The present disclosure relates to the field of cloud testing technologies, and in particular, to a testing system and method for invoking third party testing tools.

Background technique

With the development of testing technology, various testing tools emerge in an endless stream. During the software development process, various types of third-party testing tools are usually used for testing, such as functional testing tools, security testing tools, and performance testing tools. Or use a different third-party testing tool for a certain type of testing, such as using PageSpeed, Yslow for website performance testing. However, these tools have different operating modes and different usage methods. When testers need to test a software, they often need to master the installation and deployment methods of various test tools and the use of software test tools, which increases the time for completion of test tasks. And complexity, while several testers installed and deployed test tools on their respective devices, which also led to waste of device resources.

Summary of the invention

The main purpose of the present disclosure is to provide a test system and method for invoking a third-party test tool, which aims to provide a convenient and efficient test system.

To achieve the above object, the present disclosure provides a test system that invokes a third-party test tool, including:

The task information obtaining module is configured to obtain test task information submitted by the user, and save the test task information in a preset database;

a task management module, configured to acquire the test task information saved by the database, and send the test task information to a client agent module;

The client proxy module is configured to: after receiving the test task information, send, according to the information of the third-party testing tool included in the test task information, the test parameter included in the test task information to the corresponding calling module;

The calling module is configured to, after receiving the test parameter, invoke the third-party testing tool to perform a test task based on the test parameter.

Preferably, the task management module comprises:

An obtaining unit, configured to access the database, and obtain the test task information included in the database;

a query unit, configured to query a test execution state corresponding to the test task information after obtaining the test task information;

The query allocation unit is configured to: when the test execution state is a to-be-executed state, query a client proxy module whose state is idle in the system process, and send the test task information to the client proxy module.

Preferably, the calling module is further configured to obtain a test report that is feedback after the third-party testing tool performs the testing task, and process the test report into a preset text format and save the processed test report as a processed test report. Customer The end agent module feeds back the notification message that the test task is completed.

Preferably, the client proxy module is further configured to acquire and save the processed test report to the calling module when the notification message is received.

Preferably, the task management module is further configured to access the client proxy module, and when the notification message is obtained, mark the test execution status corresponding to the test task information in the database as a completed state, and The processed test report is downloaded and saved in the database.

Preferably, the task information obtaining module is further configured to access the database, and obtain the processed test from the database when the test execution state corresponding to the test task information in the database is obtained as being completed. The report is displayed on the user display interface.

The present disclosure further provides a test method for invoking a third-party testing tool, including the steps of:

The task information obtaining module acquires the test task information submitted by the user, and saves the test task information in a preset database;

The task management module acquires the test task information saved by the database, and sends the test task information to the client agent module;

After receiving the test task information, the client proxy module sends the test parameter included in the test task information to the corresponding calling module according to the information of the third-party testing tool included in the test task information;

After receiving the test parameter, the calling module invokes the third-party testing tool to perform a test task based on the test parameter.

Preferably, the task management module acquires the test task information saved by the database, and the sending the test task information to the client agent module includes:

Accessing the database to obtain the test task information included in the database;

After obtaining the test task information, querying a test execution state corresponding to the test task information;

When the test execution state is a to-be-executed state, the client proxy module in the system process state is idle, and the test task information is sent to the client proxy module.

Preferably, after the calling module receives the test parameter, calling the third-party testing tool to perform the testing task based on the testing parameter includes:

The calling module acquires a test report fed back by the third-party testing tool after performing the testing task, and processes the test report into a preset text format and saves the processed test report as a processed test report, and provides feedback to the client agent module. The notification message that the test task is completed;

And when the client proxy module receives the notification message, displaying the processed test report on the user display interface in conjunction with the task management module and the task information acquisition module.

Preferably, when the client agent module receives the notification message, displaying the processed test report on the user display interface in combination with the task management module and the task information acquiring module includes:

When the client proxy module obtains the notification message, acquiring and saving the existing location to the calling module Test report

The task management module accesses the client proxy module, and when the notification message is obtained, marking the test execution status corresponding to the test task information in the database as a completed state, and downloading the processed test report and Saved in the database.

The task information obtaining module accesses the database, and when the test execution state corresponding to the test task information in the database is obtained, the processed test report is obtained from the database, and is displayed in the database. User display interface.

The test system and method for invoking a third-party testing tool proposed by the present disclosure acquires test task information submitted by a user through a task information acquiring module, and saves the test task information in a preset database; the task management module acquires the database saved The test task information is sent to the client agent module; after receiving the test task information, the client agent module according to the information of the third party test tool included in the test task information The corresponding calling module sends the test parameter included in the test task information; after receiving the test parameter, the calling module invokes the third-party testing tool to perform a test task based on the test parameter. The task information acquisition module acquires and saves the test task information, and the task management module sends the test task information to the client agent module, the client agent module calls the corresponding calling module, and the calling module calls the corresponding third-party testing tool to execute the test task. The user does not need to install various tools, and does not need to know in detail how to use each tool. As long as the platform can be used to execute various third-party tools to perform tests, a convenient and efficient test method is realized.

DRAWINGS

1 is a schematic structural diagram of a function module of a first embodiment of a test system for invoking a third-party test tool according to the present disclosure;

2 is a diagram showing an example of a system architecture of a test system that invokes a third-party test tool according to the present disclosure;

FIG. 3 is a diagram showing an example of a method for implementing a third-party tool call by a test system that invokes a third-party test tool;

4 is a schematic diagram of a refinement function module of the task management module 20 in the embodiment shown in FIG. 1;

5 is a schematic flowchart of a first embodiment of a test method for invoking a third-party test tool according to the present disclosure;

6 is a schematic flowchart of the refinement of step S20 in the embodiment shown in FIG. 5 of the present disclosure;

FIG. 7 is a schematic flowchart of steps added after step S40 in the embodiment shown in FIG. 5;

FIG. 8 is a schematic diagram showing the refinement of step S60 in the embodiment shown in FIG. 7 of the present disclosure.

The implementation, functional features and advantages of the present disclosure will be further described with reference to the accompanying drawings.

detailed description

It is understood that the specific embodiments described herein are merely illustrative of the disclosure and are not intended to limit the disclosure.

The present disclosure provides a test system that invokes a third-party test tool. Referring to FIG. 1, in the first embodiment, the system The system includes:

The task information obtaining module 10 is configured to acquire test task information submitted by the user, and save the test task information in a preset database;

The task management module 20 is configured to acquire the test task information saved by the database, and send the test task information to a client proxy module.

The client proxy module 30 is configured to send the test parameters included in the test task information to the corresponding calling module according to the information of the third-party testing tool included in the test task information after receiving the test task information;

The calling module 40 is configured to, after receiving the test parameter, invoke the third-party testing tool to perform a test task based on the test parameter.

The test system for invoking a third-party testing tool provided in the embodiment of the present disclosure includes a task information obtaining module 10, a task management module 20, a client agent module 30, and a calling module 40, wherein the calling module 20 includes at least two, each calling module 20 can call different third-party testing tools to perform testing, wherein the task information obtaining module 10 and the task management module 20 are connected through a preset database, and the system architecture diagram of the testing system of the third-party testing tool is invoked as shown in FIG. 2, and the third party The test tool is already deployed and is called only when needed. After the user inputs the test task in the task information obtaining module 10, the execution of the test task can be completed by calling a third-party testing tool.

In the embodiment, the task information acquiring module 10 is configured to acquire and save the test task information. After the task information obtaining module 10 obtains the test task information submitted by the user, the test task information is saved in a preset database. The task information obtaining module 10 may be in the form of a website, a windows client program, or an apk program in the Android system. The above test task information includes test parameters that need to be used when using a third-party test tool, such as including a third-party test tool name, indicating which third-party test tool is needed for testing, and may include a URL to be tested, indicating that the test is required. Which website can also include test strategies and so on. In the task information obtaining module 10, information of various third-party testing tools that can be called, such as the name of the third-party testing tool, and the test status after the test starts, can be displayed, so the user can select input as needed. .

The task management module 20 can query the test task information saved in the preset database, and the task information obtaining module 10 and the task management module 20 can be deployed on the same server. After the task management module 20 receives the test task information, the test task information can be assigned to the client agent module 30.

After the client agent module 30 receives the test task information, the corresponding call module 40 is invoked, and the test parameter included in the test task information is also transmitted to the calling module 40. Since there are multiple calling modules 40 in the system, the specific calling module can be determined according to the information of the third-party testing tools included in the testing task. For example, the calling module of the same name can be called by the name of the third-party tool test. . When the program is implemented, in the client proxy module 30, an abstract base class such as initialization, parameters, and results of the third-party test tool is specified, and the client proxy module 30 can manage the call module 40 in the form of a plug-in, that is, the client proxy module 30. A plurality of calling modules 40 are called.

The calling module 40 invokes a corresponding third-party testing tool, so that the corresponding third-party testing tool executes the testing task according to the testing parameters included in the test task information, and is called according to the feature calling manner of the corresponding third-party testing tool. Calling a module at program implementation can inherit initialization base classes such as initialization, parameters, and results, in the program. Write a function that defines how each third-party test tool is called. For example, you can use the test tool called by the command line to call the test tool using the process; the test tool that can only be interfaced, use the graphical user interface (GUI) to make calls, such as using selenium calls; test with message interface Tool, called through interface communication.

When the specific program is implemented, the feature dynamic link library may also be written. The feature dynamic link library defines an abstract base class such as initialization, parameters, and results of the third-party test tool, and the client proxy module 20 refers to the feature dynamic link library, that is, the reference feature dynamics. An abstract base class such as initialization, parameters, and results of a third-party test tool specified in the link library. Each call module 40 for calling a third-party test tool inherits a class in the feature dynamic link library, and instantiates the feature in the dynamic link library. class. Therefore, the client proxy module 20 can dynamically load the calling module 40 so that the calling module executes the calling function after being loaded, and invokes a third-party testing tool to perform the testing. The above method for invoking a third-party testing tool through a program is shown in FIG. 3.

For example, when users need to use WebInspect and NSFocus test tools for website security scanning. The main interaction parameters required by the two tools are the target URL to be scanned and the scanning policy. The target information URL is input in the task information obtaining module 10, and the scanning strategies of the two tools are selected according to the prompts, and the test task information is submitted and saved to the database. . At this time, the task management module 20 scans the database to obtain the test task and transmits the test task information to the client proxy module 30. The client proxy module 30 obtains the test tool names WebInspect and NSFocus included in the test task, and the test parameters corresponding to WebInspect and NSFoucus respectively. Then, the calling module 40 corresponding to WebInspect and NSFocus is called, and the WebInspect and NSFocus testing tools are called by the calling module 40 to perform specific testing tasks.

In this embodiment, the task information acquiring module 10 obtains the test task information submitted by the user, and saves the test task information in a preset database; the task management module 20 acquires the test task information saved in the database, and the The test task information is sent to the client proxy module 30. After receiving the test task information, the client proxy module 30 sends the information to the corresponding calling module 40 according to the information of the third-party testing tool included in the test task information. The test parameter included in the test task information; after receiving the test parameter, the calling module 40 invokes the third-party test tool to execute a test task based on the test parameter. The task information obtaining module 10 acquires and saves the test task information, and the task management module 20 sends the test task information to the client agent module 30. The client agent module 30 calls the corresponding calling module 40, and the calling module 40 calls the corresponding third party test. The tool performs the test task, so that the user does not need to install various tools, and does not need to know the usage of each tool in detail. As long as the platform can call various third-party tools to perform the test, the convenient and efficient test method is realized.

Preferably, referring to FIG. 4, it is a schematic diagram of a refinement function module of the task management module 20 in the first embodiment of the test system for invoking a third-party test tool according to the present disclosure. The task management module 20 includes:

An obtaining unit 21, configured to access the database, and obtain the test task information included in the database;

The query unit 22 is configured to query a test execution state corresponding to the test task information after acquiring the test task;

The query allocation unit 23 is configured to query a client proxy module whose state is idle in the system process when the test execution state is a to-be-executed state, and send the test task information to the client proxy module.

In the embodiment, the database is a database in which the task information acquiring module 10 saves the test task information, and the second obtaining module 21 accesses the database. After obtaining the test task information in the database, the test execution state corresponding to the test task information is queried, because the database There are a lot of test task information stored in the test task. The test execution status of each test task information may be different. Therefore, when the test execution status corresponding to the test task information is in the pending execution state, it indicates that the test task information has been obtained but the test task information. The representative test task is not executed. At this time, the idle client proxy module 30 in the query system process allocates a test task to the client proxy module 30 according to the address of the client proxy module 30.

In this embodiment, the task management module 20 queries the database to obtain test task information, queries the idle client agent module 30, and allocates test task information to the idle client agent 30 module, so that the test task represented by the test task information can be quickly detected. carried out.

Preferably, the invoking module 40 is further configured to obtain a test report that is feedback after the third-party test tool executes the test task, and process the test report into a preset text format and save the report as a processed test report. The client agent module feeds back a notification message that the test task is completed.

In this embodiment, after the third-party testing tool performs the test, the calling module 40 obtains the test report after the third-party testing tool executes the test, and feeds back the notification of the completion of the testing task to the client-side proxy module 30 that invokes the calling module 40. Message.

After the calling module 40 obtains the test report, the format of the test report is processed and saved as a processed test report, so that various third-party test tools can present the test report in the same format after performing the test. It can be understood that the test report in a unified format can be provided to the user, and the automatically generated original test report after the third party test tool performs the test task can also be provided.

For example, when a third-party testing tool performs a test, the test report is a text file in Word format. At this time, the text information in Word and format is obtained, and the text information is processed into a PDF format for saving. At the same time, the test report can also be sorted according to the hazard level of the test results, and the test report is classified and stored according to high risk, intermediate risk and low risk.

In this embodiment, the calling module 40 receives the test report fed back by the corresponding third-party testing tool after performing the testing task, and processes the test report, so that the user can see the test result after the third-party testing tool is executed. The format of the test results is uniform and easy to view and analyze.

Preferably, the client proxy module 30 is further configured to: when the notification message is received, acquire and save the processed test report to the calling module.

In the embodiment, after receiving the notification message of the completion of the test task, the client proxy module 30 obtains the processed test report from the calling module 40, and saves the processed test report in the server where the client proxy module 30 is located.

In this embodiment, the client agent module 30 receives the notification message, and obtains and saves the test report of the calling module 40, so that the task management module 20 can obtain the test task execution status and the test report from the client proxy module 30, thereby enabling the combination. The task information obtaining module 10 enables the user to see the test report after the third party test tool is called to perform the test.

Preferably, the task management module 20 is further configured to access the client proxy module, and when the notification message is obtained, mark the test execution status corresponding to the test task information in the database as a completed state, and The processed test report is downloaded and saved in the database.

In this embodiment, the task management module 20 accesses the client proxy module. When the notification message of the completion of the test task is obtained, it indicates that the test task has been completed at this time, and the task management module 20 marks the test execution state corresponding to the test task information in the database as The status is completed and the processed test report downloaded from the client agent module 30 is saved in the database. The time for accessing the client proxy module 30 can be set for the task management module 20, for example, setting the task management module to periodically obtain the execution status of the test task.

In this embodiment, the client management module 30 is accessed by the task management module 20, and when the notification message of the completion of the test task is obtained, the test execution status corresponding to the test task information in the database is marked as completed, and the task information acquisition module is obtained. 10 can obtain the execution status of the test task from the database, and obtain the test report of the completed test task in time.

Preferably, the task information obtaining module 10 is further configured to access the database, and obtain the processed test from the database when the test execution state corresponding to the test task information in the database is obtained as being completed. The report is displayed on the user display interface.

In the embodiment, when the task information acquiring module 10 obtains the test execution state corresponding to the test task information in the database as the completed state, it indicates that the test task has been completed, and the test report has been generated. At this time, the processed test report is obtained from the database, and the processed test report is displayed on the user display interface, and the user can view and save the processed test report. You can also display the detailed information of the processed test report and the download link of the processed test report on the user display interface. The way to display the test report after the specific test can be selected as needed.

In this embodiment, the task information acquisition module obtains the test report and displays it on the user display interface, so that the user can view, analyze, and manage the test report of the test task after the test task is completed.

The present disclosure also provides a test method for invoking a third-party test tool. Referring to FIG. 5, a first embodiment of a test method for calling a third-party test tool according to the present disclosure is provided. In this embodiment, a test method for calling a third-party test tool includes :

Step S10: The task information obtaining module acquires test task information submitted by the user, and saves the test task information in a preset database.

Step S20, the task management module acquires the test task information saved by the database, and the test task is The information is sent to the client agent module;

Step S30, after receiving the test task information, the client proxy module sends the test parameter included in the test task information to the corresponding calling module according to the information of the third-party tool included in the test task information;

Step S40: After receiving the test parameter, the calling module invokes the third-party testing tool to perform a test task based on the test parameter.

The test method for invoking a third-party testing tool provided in the embodiment of the present disclosure implements a layer call of the task management module, the client proxy module, and the calling module after the user inputs the test task in the task information obtaining module, and finally calls the corresponding call. The third-party testing tool completes the execution of the test task.

In the embodiment, the task information acquiring module is configured to acquire and save the test task information. After the task information acquiring module obtains the test task information submitted by the user, the test task information is saved in a preset database. The task information acquisition module may be a website form, a windows client program, or an apk program in the Android system. The above test task information includes test parameters that need to be used when using a third-party test tool, such as including a third-party test tool name, indicating which third-party test tool is needed for testing, and may include a URL to be tested, indicating that the test is required. Which website can also include test strategies and so on. In the task information acquisition module, information of various third-party test tools that can be called, such as the name of the third-party test tool, and the test status after the test is started, can be displayed, so the user can select input as needed.

The task management module can query the test task information saved in the preset database, and the task information obtaining module and the task management module can be deployed on the same server. After the task management module receives the test task information, the test task information can be assigned to the client agent module.

When the client agent module receives the test task information, the corresponding calling module is called, and the test parameter included in the test task information is also transmitted to the calling module. Since there are multiple calling modules in the system, the specific calling module can be determined according to the information of the third-party testing tools included in the testing task. For example, the calling module of the same name can be called by the name of the third-party tool test. In the program implementation, in the client proxy module, an abstract base class such as initialization, parameters, and results of the third-party test tool is specified, and the client proxy module can manage the calling module in the form of a plug-in, that is, the client proxy module invokes multiple calls. Module.

The calling module calls the corresponding third-party testing tool, so that the corresponding third-party testing tool executes the testing task according to the test parameters included in the test task information, and is called according to the feature calling manner of the corresponding third-party testing tool. The calling module can inherit the abstract base class such as initialization, parameters, and results when the program is implemented. The function is written in the program to define the calling method of each third-party testing tool. For example, you can use the test tool called by the command line to call the test tool using the process; the test tool that can only be interfaced, use the graphical user interface (GUI) to make calls, such as using selenium calls; test with message interface Tool, called through interface communication.

When the specific program is implemented, the feature dynamic link library may also be written. The feature dynamic link library defines an abstract base class such as initialization, parameters, and results of the third-party test tool, and the client proxy module refers to the feature dynamic link library, that is, the reference feature dynamic link. Abstract base classes for initialization, parameters, and results of third-party test tools specified in the library, each for tuning The class in the feature dynamic link library is inherited by the calling module of the third-party test tool, and the class in the feature dynamic link library is instantiated. Therefore, the client proxy module can dynamically load the calling module, so that the calling module executes the calling function after being loaded, and calls a third-party testing tool to execute the test. The above method for invoking a third-party testing tool through a program is shown in FIG. 3.

For example, when users need to use WebInspect and NSFocus test tools for website security scanning. The main interaction parameters required by these two tools are the target URL to be scanned and the scanning policy. Enter the destination URL in the task information acquisition module, and select the scanning strategy of the two tools as prompted, submit the test task information and save it to the database. At this time, the task management module scans the database to obtain the test task and transmits the test task information to the client agent module. The client agent module obtains the test tool names WebInspect and NSFocus included in the test task, and the test parameters corresponding to WebInspect and NSFoucus respectively, and then invokes The calling module corresponding to WebInspect and NSFocus uses the calling module to call WebInspect and NSFocus test tools to perform specific test tasks.

In this embodiment, the task information acquisition module acquires the test task information submitted by the user, and saves the test task information in a preset database; the task management module acquires the test task information saved by the database, and the test task is The information is sent to the client proxy module. After receiving the test task information, the client proxy module sends the test task information to the corresponding calling module according to the information of the third-party testing tool included in the test task information. Test module; after receiving the test parameter, the calling module invokes the third-party test tool to perform a test task based on the test parameter. The task information acquisition module acquires and saves the test task information, and the task management module sends the test task information to the client agent module, the client agent module calls the corresponding calling module, and the calling module calls the corresponding third-party testing tool to execute the test task. The user does not need to install various tools, and does not need to know in detail how to use each tool. As long as the platform can be used to execute various third-party tools to perform tests, a convenient and efficient test method is realized.

Preferably, referring to FIG. 6, a refinement flow diagram of step S20 in the first embodiment of the test method for invoking a third-party test tool according to the present disclosure, the refinement step of the foregoing step S20 includes:

Step S21, accessing the database, and acquiring the test task information included in the database;

Step S22, after obtaining the test task information, querying a test execution state corresponding to the test task information;

Step S23: When the test execution state is a to-be-executed state, query a client proxy module whose state is idle in the system process, and send the test task information to the client proxy module.

In the embodiment, the database is a database in which the task information acquiring module saves the test task information, and the second obtaining module accesses the database. After obtaining the test task information in the database, the test execution state corresponding to the test task information is queried, because the database will A plurality of test task information is stored, and the test execution state corresponding to each test task information may be different. Therefore, when the test execution state corresponding to the test task information is a pending execution state, it indicates that the test task information has been acquired but the test task information represents The test task is not executed. At this time, the idle client agent module in the system process is queried, and the test task is assigned to the client agent module according to the address of the client agent module.

In this embodiment, the task management module queries the database to obtain test task information, queries the idle client agent module, and allocates test task information to the idle client agent module, so that the test task represented by the test task information can be executed as soon as possible.

Preferably, referring to FIG. 7, a schematic flowchart of an additional step after step S40 in the first embodiment of the test method for invoking a third-party test tool according to the present disclosure, after the step S40, the method further includes:

Step S50, the calling module acquires a test report that is feedback after the third-party test tool executes the test task, and processes the test report into a preset text format and saves the processed test report as a processed test report to the client. The proxy module feeds back the notification message that the test task is completed;

Step S60, when the client proxy module receives the notification message, display the processed test report on the user display interface in combination with the task management module and the task information obtaining module.

In this embodiment, after the third-party testing tool performs the test, the calling module obtains the test report after the third-party testing tool executes the test, and feeds back the notification message of the completion of the testing task to the client agent module that invokes the calling module.

After the calling module obtains the test report, the format of the test report is processed and saved as a processed test report, so that various third-party test tools can present the test report in the same format after performing the test. It can be understood that the test report in a unified format can be provided to the user, and the automatically generated original test report after the third party test tool performs the test task can also be provided.

In this embodiment, the test report after the task is completed is obtained by calling the module, and the test report is processed into the processed test report, and then the task management module and the task information obtaining module are combined to display the processed test report feedback on the user interface, so that the user passes the After the task information acquisition module inputs the test task, the task information acquisition module can obtain the test report.

Preferably, referring to FIG. 8 , it is a schematic flowchart of the refinement of step S60 in the embodiment in FIG. 7 , where the foregoing step S60 includes:

Step S610, when the client proxy module obtains the notification message, acquiring and saving the processed test report to the calling module;

Step S620: The task management module accesses the client proxy module, and when the notification message is obtained, marking the test execution status corresponding to the test task information in the database as a completed state, and the processed test is performed. The report is downloaded and saved in the database.

Step S630, when the task information obtaining module acquires the corresponding test task information in the database. When the test execution state is the completed state, the processed test report is obtained from the database and displayed on the user display interface.

In the embodiment, the notification message is a message sent by the calling module to the client proxy module, and the notification message is used to notify the client proxy module that the test task has been executed. After receiving the notification message of the completion of the test task, the client agent module obtains the processed test report from the task management module, and saves the processed test report in the server where the client agent module is located.

When the task management module accesses the client proxy module and obtains the notification message of the completion of the test task, it indicates that the test task has been completed at this time, and the task management module marks the test execution state corresponding to the test task information in the database as the completed state, and simultaneously The client agent module downloads the processed test report and saves it in the database. The time for accessing the client proxy module can be set for the task management module, for example, setting the task management module to periodically obtain the execution status of the test task.

When the task information obtaining module obtains the test execution state corresponding to the test task information in the database as the completed state, it indicates that the task information obtaining module obtains the test task submitted for testing has been completed, and the test report has been generated. At this time, the processed test report is obtained from the database, and the processed test report is displayed on the user display interface, and the user can view and save the processed test report. You can also display the detailed information of the processed test report and the download link of the processed test report on the user display interface. The way to display the test report after the specific test can be selected as needed.

In this embodiment, after the client agent module obtains the notification message of the completion of the test task, the client module acquires and saves the processed test report, and the task management module accesses the client agent and obtains the notification message of the completion of the test task, and then the database The test execution status corresponding to the test task information is marked as completed, so that the task information acquisition module can obtain the execution status of the test, and download the processed test report after the test task is executed in time to feedback to the user, so that the user invokes the third-party test. The tool can get the test results in time after the test is executed.

Industrial applicability

The present disclosure relates to the field of cloud testing technology, and realizes that various third-party tools can be used to execute tests through the platform, thereby implementing a convenient and efficient testing method.

The above is only a preferred embodiment of the present disclosure, and is not intended to limit the scope of the patents of the present disclosure, and the equivalent structure or equivalent process transformations made by the present disclosure and the contents of the drawings may be directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of the present disclosure.

Claims

A test system that invokes third-party testing tools, including:

The task information obtaining module is configured to obtain test task information submitted by the user, and save the test task information in a preset database;

a task management module, configured to acquire the test task information saved by the database, and send the test task information to a client agent module;

The client proxy module is configured to: after receiving the test task information, send, according to the information of the third-party testing tool included in the test task information, the test parameter included in the test task information to the corresponding calling module;

The calling module is configured to, after receiving the test parameter, invoke the third-party testing tool to perform a test task based on the test parameter.
The system of claim 1 wherein said task management module comprises:

An obtaining unit, configured to access the database, and obtain the test task information included in the database;

a query unit, configured to query a test execution state corresponding to the test task information after obtaining the test task information;

The query allocation unit is configured to: when the test execution state is a to-be-executed state, query a client proxy module whose state is idle in the system process, and send the test task information to the client proxy module.
The system of claim 1, wherein the invoking module is further configured to obtain a test report that is feedback after the third-party testing tool performs the testing task, and process the test report into a preset text format. For the processed test report, the notification message of the completion of the test task is fed back to the client agent module.
The system of claim 3 wherein said client agent module is further configured to retrieve and save said processed test report to said calling module upon receipt of said notification message.
The system of claim 4, wherein the task management module is further configured to access the client proxy module, and when the notification message is obtained, perform test execution corresponding to the test task information in the database The status is marked as completed and the processed test report is downloaded and saved in the database.
The system of claim 5, wherein the task information obtaining module is further configured to access the database, and when the test execution state corresponding to the test task information in the database is obtained as a completed state, The database obtains the processed test report and displays it on the user display interface.
A test method that invokes a third-party test tool, including the following steps:

The task information obtaining module acquires test task information submitted by the user, and saves the test task information in a preset In the database;

The task management module acquires the test task information saved by the database, and sends the test task information to the client agent module;

After receiving the test task information, the client proxy module sends the test parameter included in the test task information to the corresponding calling module according to the information of the third-party testing tool included in the test task information;

After receiving the test parameter, the calling module invokes the third-party testing tool to perform a test task based on the test parameter.
The method of claim 7, wherein the task management module acquires the test task information saved by the database, and the sending the test task information to the client agent module comprises:

Accessing the database to obtain the test task information included in the database;

After obtaining the test task information, querying a test execution state corresponding to the test task information;

When the test execution state is a to-be-executed state, the client proxy module in the system process state is idle, and the test task information is sent to the client proxy module.
The method according to claim 7 or 8, wherein the calling module, after receiving the test parameter, after calling the third-party test tool to perform a test task based on the test parameter, comprises:

The calling module acquires a test report fed back by the third-party testing tool after performing the testing task, and processes the test report into a preset text format and saves the processed test report as a processed test report, and provides feedback to the client agent module. The notification message that the test task is completed;

And when the client proxy module receives the notification message, displaying the processed test report on the user display interface in conjunction with the task management module and the task information acquisition module.
The method of claim 9, wherein said said client agent module displays said processed test report in conjunction with said task management module and said task information acquisition module when said client agent module receives said notification message The user display interface includes:

When the client proxy module obtains the notification message, acquiring and saving the processed test report to the calling module;

The task management module accesses the client proxy module, and when the notification message is obtained, marking the test execution status corresponding to the test task information in the database as a completed state, and downloading the processed test report and Saved in the database.

The task information obtaining module accesses the database, and when the test execution state corresponding to the test task information in the database is obtained, the processed test report is obtained from the database, and is displayed in the database. User display interface.