Test method, system and related device

Abstract

One or more embodiments of the invention disclose a test method, system and related device, and the method comprises the steps: building a universal test processing device and a plurality of test execution nodes which are connected with the test processing device and support different test services, and then obtaining to-be-processed test data through the test processing device, and generating a test task according to the to-be-processed test data, sending the test task to a test execution node corresponding to the test service determined based on the task type of the test task, so that the test execution node executes the test task according to the locally configured test service, and returns a test result to the test processing device. Therefore, while a test general function is provided based on the test processing device, different types of test services can be realized based on the test execution node, the cost is reduced, the development period is shortened, and the test flexibility, universality and test efficiency are improved.

Description

Technical Field

[0001] This document relates to the field of communication technology, and in particular to a testing method, system and related devices. Background Art

[0002] With the rapid increase of various application software, developers need to repeatedly test the software or the system composed of the software after developing it and before releasing it to ensure the normal operation of the software and meet the needs of users. Generally, developers will develop and design different test platforms according to the different software to be tested to meet the testing requirements of the software to be tested.

[0003] However, considering that the testing requirements of the software to be tested vary, the test platform has low reusability and is severely fragmented, making subsequent maintenance difficult. Moreover, the development cycle of the test platform is long, the cost is high, and it is unable to follow up on testing service needs in a timely manner.

[0004] It can be seen that the existing testing platforms have poor versatility, cannot flexibly match diverse testing service requirements, and have low testing efficiency. Summary of the invention

[0005] The purpose of one or more embodiments of this specification is to provide a testing method, system and related devices to build a universal testing platform that provides universal testing functions while supporting various types of testing services to improve the efficiency of automated testing.

[0006] To solve the above technical problems, one or more embodiments of this specification are implemented as follows:

[0007] In a first aspect, a testing method is proposed, which is applied to a testing system including a test processing device and a plurality of test execution nodes, wherein the plurality of test execution nodes are respectively configured with test services provided for the same or different categories of software; on the test processing device side, the testing method comprises:

[0008] Get the test data to be processed;

[0009] Generate a test task according to the test data to be processed, wherein the test task carries a task type;

[0010] Sending the test task to a test execution node corresponding to a test service determined based on a task type of the test task, so that the test execution node executes the test task according to a locally configured test service;

[0011] Receive the test result returned by the test execution node.

[0012] In a second aspect, a test method is proposed, which is applied to a test system including a test processing device and a plurality of test execution nodes, wherein the plurality of test execution nodes are respectively configured with test services provided for the same or different categories of software; the test method on the test execution node side includes:

[0013] Receiving a test task, wherein the test task is generated by the test processing device according to the acquired test data to be processed, and sent by the test processing device to a test execution node corresponding to a test service determined based on a task type of the test task;

[0014] Execute the test task according to the locally configured test service;

[0015] The test result is sent to the test processing device.

[0016] In a third aspect, a test processing device is proposed, which forms a test system with a plurality of test execution nodes, wherein the plurality of test execution nodes are respectively configured with test services provided for the same or different categories of software; the test processing device comprises:

[0017] An acquisition module is used to acquire the test data to be processed;

[0018] A generating module, used for generating a test task according to the test data to be processed, wherein the test task carries a task type;

[0019] A sending module, used for sending the test task to a test execution node corresponding to a test service determined based on a task type of the test task, so that the test execution node executes the test task according to a locally configured test service;

[0020] The receiving module is used to receive the test result returned by the test execution node.

[0021] In a fourth aspect, a test execution device is provided, wherein the test execution node is configured with test services provided for software of the same or different categories; the test execution device comprises:

[0022] A receiving module, configured to receive a test task, wherein the test task is generated by the test processing device according to the acquired test data to be processed, and is sent by the test processing device to a test execution node corresponding to a test service determined based on a task type of the test task;

[0023] An execution module, used to execute the test task according to the locally configured test service;

[0024] The sending module is used to send the test result to the test processing device.

[0025] In a fifth aspect, a test system is proposed, comprising: a test processing device and a plurality of test execution nodes connected to the test processing device, wherein the plurality of test execution nodes are respectively configured with test services provided for the same or different categories of software; wherein:

[0026] The test processing device is used to obtain the test data to be processed, and generate a test task according to the test data to be processed, wherein the test task carries a task type; and is used to send the test task to a test execution node corresponding to the test service determined based on the task type of the test task;

[0027] The test execution node is used to receive a test task and execute the test task according to a locally configured test service; and to send a test result to the test processing device.

[0028] In a sixth aspect, an electronic device is provided, comprising:

[0029] Processor; and

[0030] A memory arranged to store computer executable instructions, wherein when the executable instructions are executed, the processor executes the test method of the first aspect or the test method of the second aspect.

[0031] In the seventh aspect, a computer-readable storage medium is proposed, which stores one or more programs. When the one or more programs are executed by an electronic device including multiple applications, the electronic device executes the test method described in the first aspect or the test method described in the second aspect.

[0032] It can be seen from the technical solutions provided by one or more embodiments of the above specification that by building a universal test processing device and multiple test execution nodes supporting different test services connected to the test processing device, the test data to be processed is obtained through the test processing device, a test task is generated according to the test data to be processed, and the test task is sent to the test execution node corresponding to the test service determined based on the task type of the test task, so that the test execution node executes the test task according to the locally configured test service and returns the test result to the test processing device. Therefore, while providing universal test functions based on the test processing device, it can also support the implementation of different types of test services based on the test execution node, reduce costs and development cycles, and improve test flexibility, universality and test efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate one or more embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the description of one or more embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments recorded in this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0034] Figure 1 It is a schematic diagram of the system architecture applicable to the test solution provided in the embodiments of this specification.

[0035] Figure 2 This is one of the step diagrams of the testing method provided in the embodiments of this specification.

[0036] Figure 3 This is the second schematic diagram of the steps of the testing method provided in the embodiment of this specification.

[0037] Figure 4 This is the third step schematic diagram of a testing method provided in the embodiment of this specification.

[0038] Figure 5 It is a flowchart of a test solution provided in an embodiment of this specification.

[0039] Figure 6 It is one of the structural schematic diagrams of a testing device provided by an embodiment of this specification.

[0040] Figure 7 This is the second structural schematic diagram of a testing device provided in an embodiment of this specification.

[0041] Figure 8a This is one of the structural schematic diagrams of an electronic device provided by an embodiment of this specification.

[0042] Figure 8b This is the second structural diagram of an electronic device provided by an embodiment of this specification. DETAILED DESCRIPTION

[0043] In order to enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the one or more embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on one or more embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0044] Faced with the growing demand for testing, developers will develop and design different test platforms according to the different software to be tested to ensure more efficient completion of the testing work of the software to be tested. However, the current construction of the test platform has the following problems: First, the different test software leads to different test plans, which results in low reusability of the development and construction methods and the test platform, scattered test services, high fragmentation, and difficult later maintenance. Secondly, due to the lack of reusability, each time a new requirement is added or the test service is modified, it must be built from 0 to 1, which is a large workload, high cost investment, long development cycle, and unable to follow up on the demand for test services in a timely manner.

[0045] In order to solve the above problems, the embodiments of this specification provide a new test solution, which is to build a universal test processing device and multiple test execution nodes supporting different test services connected to the test processing device, and then obtain the test data to be processed through the test processing device, generate a test task according to the test data to be processed, and send the test task to the test execution node corresponding to the test service determined based on the task type of the test task, so that the test execution node can execute the test task according to the locally configured test service and return the test result to the test processing device. Therefore, while providing general test functions based on the test processing device, it can also support the implementation of different types of test services based on the test execution node, reduce costs and development cycles, and improve test flexibility, universality and test efficiency.

[0046] Reference Figure 1 As shown, it is a schematic diagram of the system architecture applicable to the test scheme provided in the embodiment of this specification. In this system architecture, it can include: a test processing device 102 and multiple test execution nodes 104 connected to the test processing device 102, wherein the multiple test execution nodes 104 are respectively configured with multiple test services provided for the same or different categories of software; the test execution node 104 can provide one test service or multiple test services, and one test task can request one test service to execute, so, generally speaking, the test execution node 104 can provide a test service for one test task; in fact, when the test task can be split, the test execution node 104 can also provide multiple test services for one test task at the same time, or provide the same test service for multiple test tasks at the same time, and this specification does not limit this.

[0047] The test processing device 102 can be used as a general processing module of the test system to provide other general services in addition to the execution of test tasks, such as the acquisition of test data, the generation of test tasks, and the generation and viewing of test reports; the test processing device 102 can also allocate one or more test execution nodes 104 capable of executing the test task to the test task by configuring some task information when the test task is generated, and then, the test processing device 102 sends the test task to the corresponding test execution node 104 for execution under the trigger condition, wherein the specific execution method can be based on the test service configured locally on the test execution node 104 and executed according to the corresponding test steps in the test task. In the embodiments of this specification, the specific execution process is not limited, and it can be executed according to the existing implementation scheme of the test function.

[0048] It should be understood that the test execution node 104 in the embodiment of this specification is different from the existing test platform. It is a test execution module that is completely decoupled from the test processing device 102, and can flexibly add or delete the number of test execution nodes and the test services of the test execution nodes according to the increase or modification of test requirements. Among them, when the test execution node 104 is initialized, it is necessary to interact with the test processing device 102 to complete the node registration of the test execution node 104 on the test processing device 102. The registration content may include: the node identification of the test execution node 104, the supported test service type, etc.; after the registration is successful, the test processing device 102 and the test execution node 104 can synchronize information, that is, the test processing device 102 can obtain the task execution status of the test execution node 104 through the corresponding interface, so as to understand the resource occupancy of the test execution node 104 and reasonably allocate test tasks to the test execution node 104.

[0049] The test scheme involved in this specification is described in detail through the following examples.

[0050] Embodiment 1

[0051] Reference Figure 2 As shown, it is a schematic diagram of the steps of a test method provided in the embodiment of this specification. It should be understood that this method can be applied to the above Figure 1 In the test system, the execution subject may be a test processing device, which may be a test platform for test users, which may be a hardware device or software module with computer processing and storage capabilities, such as computers, mobile phones, computers and other electronic devices, or software modules such as applications and applets integrated in hardware devices.

[0052] The test method may include the following steps:

[0053] Step 202: Obtain test data to be processed.

[0054] In the embodiments of this specification, test data is data generated for functional testing of the software to be tested. These test data can be input into the test processing device in a variety of ways. Specifically, it can be through manual input, recording generation or log capture. Among them, manual input can be the test user in the interactive interface of the test processing device, and the test data of the software to be tested is entered into the test processing device according to the test requirements. Recording generation can be recording the test data published in the local or other devices, and generating the required test data according to the recording rules. Log capture can be the capture of the operation data, logs, etc. of the corresponding software to be tested running in the local or other devices. It can be seen that there are many ways to enter the test data in this specification, and the way of entry is not limited. It can be selected from one or more combinations.

[0055] After entering the test data, you can also generate a test data set based on the test data, that is, create a new test data set; wherein the test data set can contain one or more test data. When creating a new test data set, you can configure and supplement: data set name, related data description, test data type and other information.

[0056] In one achievable manner, when obtaining the test data to be processed, one or more test data may be selected from the test data produced by the target software as the test data to be processed; or, new test data may be created for the target software and the new test data may be used as the test data to be processed; or, one or more test data may be selected from the test data produced by the target software and new test data may be created for the target software; and the selected one or more test data and the new test data may be used as the test data to be processed. In other words, there may be multiple test data and test data sets, and the required test data may be selected from the existing test data as the test data to be processed, or a new test data set may be created as the test data to be processed, or the new test data set and the selected test data may be used together as the test data to be processed.

[0057] Step 204: Generate a test task according to the test data to be processed, wherein the test task carries a task type.

[0058] It should be understood that the test task can be established at any time according to the needs of the test user, or established when there is a test demand triggered. Therefore, when a test demand occurs, the test processing device can generate a test task according to the test needs of the test user, according to the selected test data to be processed, and the configured basic configuration information such as the module to be tested, task type, sending strategy, and notification strategy. In specific implementation, it can be in response to the test user's test task creation operation in the interactive interface, and a new test task bar pops up in the interactive interface. The new test task bar contains multiple configuration information setting boxes. By responding to the test user's input operation or click operation on different configuration information setting boxes, the information configuration of the test task is realized. Then, the test processing device generates the required test task according to the test data to be processed and the configured basic configuration information.

[0059] The task type carried in the test task can have a one-to-one mapping relationship with the test service. In this way, in the test processing device, a corresponding relationship between the task type and the test service can be established based on experience or data analysis and estimation, so as to allocate a suitable test execution node to the test task later.

[0060] In the embodiments of the present specification, the module to be tested may be a module that needs to be tested in the target software. The task type may be a task such as creating a new model, reprocessing a model, and viewing model results. The sending strategy may be a trigger sending method set according to the test requirements, for example, continuous delivery execution, which may be the continuous sending and execution of the test task; that is, after sending, the next one is sent, and the processing is continued; scheduled execution, which may be setting a timer, and when the set time is reached, triggering the test task to be sent to the corresponding test execution node; manual execution, which may be the test user manually triggering the test task to be sent to the peer test execution node at any time according to the test requirements. The notification strategy may be that the test user selects a suitable email or instant messaging tool for timely feedback of the test data according to the test requirements and the hardware and software configuration of the test processing device, so that the test user can know the test results in time.

[0061] Step 206: Send the test task to a test execution node corresponding to a test service determined based on the task type of the test task, so that the test execution node executes the test task according to the locally configured test service.

[0062] Since a sending strategy is configured when the test task is generated in step 204, when the set sending strategy is hit, the test processing device will be triggered to send the test task to the test execution node corresponding to the test service determined based on the task type of the test task. In specific implementation, the following triggering methods can be used according to different sending strategies:

[0063] Trigger method 1

[0064] The sending strategy is scheduled sending, and then at the set sending timing of the test task, the test task is sent to the test execution node corresponding to the test service determined based on the task type of the test task.

[0065] Trigger method 2

[0066] The sending strategy is continuous sending, and when the sending of the last test task is completed, the test task is sent to a test execution node corresponding to the test service determined based on the task type of the test task.

[0067] Trigger method three

[0068] The sending strategy is manual sending, then in response to a triggering operation of a user on an interactive interface, the test task is sent to a test execution node corresponding to a test service determined based on a task type of the test task.

[0069] As described above, the test processing device maintains node registration information of multiple test execution nodes generated after the test processing device is registered; therefore, when the test task is sent to the test execution node corresponding to the test service determined based on the task type of the test task, the test execution node whose test service matches the task type and is in an idle state can be determined based on the task type of the test task and the node registration information; the test task is sent to the found test execution node. In specific implementation, the test execution node whose test service matches the task type and is in an idle state can be found from the node registration information based on the task type of the test task.

[0070] When the test processing device sends a test task, the task type of the test task can be read from the test task, and then based on the task type, the test execution node corresponding to the test service matching the task type can be found from the pre-registered node registration information, and the test service of the test execution node is determined to be in an idle state or the test execution node is in an idle state, and the test task is sent to the test execution node. After receiving the test task, the test execution node processes the test task according to the locally configured test service, executes the specific task content in the test task, so as to implement the test processing of the module to be tested and obtain the test result. Then the test result is returned to the test execution node.

[0071] Step 208: Receive the test result returned by the test execution node.

[0072] The test processing device receives the test results returned by the test execution node and saves the test results, which can be stored locally in the test processing device or in the cloud server of the test processing device for subsequent query and call.

[0073] A feasible solution is that the test processing device interacts with the multiple test execution nodes through an open application programming interface; when the test service of the test execution node changes, it can also receive the change information returned by the test execution node whose test service has changed through the open application programming interface API, and update the node registration information corresponding to the test execution node based on the change information.

[0074] In specific implementation, when the test service of the test execution node changes, the registration request returned by the test node whose test service has changed can be received through the open API, so as to re-apply to the test processing device for registering a new test service, or the idle state information returned by the test node whose test service has changed can be received through the open API, so as to update the idle state information contained in the node registration information in the test processing device. Furthermore, when a new test execution node is added, the registration request returned by the test node can be received through the open API, so as to re-apply to the test processing device for registering a new test execution node; or, when a test execution node is deleted, the registration request returned by the test node can be received through the open API, so as to re-apply to the test processing device for a cancellation request, so as to apply to the test processing device to delete the registration information of the test execution node.

[0075] It can be seen that the test execution nodes bound to the test processing device by interface registration can be flexibly increased or decreased according to demand, rather than being fixed after development. When there are many test requirements, test execution nodes can be added, and the required test services can be developed on the test execution nodes. After that, the binding with the test processing device is completed through registration, thereby assisting the test processing device to implement the execution operation of the corresponding test task. Moreover, when new test requirements arise, the automated development of the test execution nodes that execute the test tasks can be considered, without having to pay attention to the development of general functions on the test processing device, and the test processing device can be directly reused.

[0076] It should be understood that in the embodiments of this specification, the test execution node can automate the execution process of the test task through any language and any method. This specification does not impose any restrictions or requirements on this, thereby shielding the differences in technical capabilities of different test developers and reducing the technical requirements for test platform development.

[0077] It can be seen that by setting the test execution node, the execution function of the test task is decoupled from the test processing device, and the update of service automation only needs to update the test execution node, avoiding frequent deployment and causing platform stability problems.

[0078] Further, refer to Figure 3 As shown, after the test processing device obtains the test result returned by the test execution node, the following steps are also included:

[0079] Step 210: Summarize and analyze at least one test result and generate a test report.

[0080] The test report here can be a combination of pictures, texts, characters, etc. that can reflect the test execution details obtained by summarizing and analyzing one or more test results obtained. In specific implementation, after one or more required test results are successfully obtained, these test results can be automatically summarized and analyzed according to the generation conditions preset by the test user to generate a test report. Alternatively, in response to the trigger operation of the test user, one or more test results selected by the test user can be summarized and analyzed to generate a test report.

[0081] In fact, at any stage of the entire test, the test processing device can query the test results and / or test reports matching the query request based on the query request triggered by the user, and display them on the interactive interface.

[0082] Reference Figure 4 As shown, it is a schematic diagram of the third step of a test method provided in the embodiment of this specification. It should be understood that this method can be applied to the above Figure 1 In the test system, the execution subject may be a test execution node, which may be a valid execution node registered in the test processing device; the test execution node may be a hardware device or software module with computer processing and storage capabilities, such as a computer, a mobile phone, a computer and other electronic devices, or an application, a small program and other software modules integrated in the hardware device.

[0083] The testing method may include the following steps:

[0084] Step 402: receiving a test task, wherein the test task is generated by the test processing device according to the acquired test data to be processed, and sent by the test processing device to a test execution node corresponding to a test service determined based on a task type of the test task.

[0085] In this step, for details about the test task generation scheme and test data acquisition, please refer to Figure 2 The technical content covered by the test method shown will not be elaborated here.

[0086] Step 404: Execute the test task according to the locally configured test service.

[0087] As mentioned above, the test service configured by the test execution node can be updated according to the change of test requirements. The test execution node can realize the automation of the execution process of the test task in any language and in any way. This specification does not restrict or require this, shielding the differences in technical capabilities of different test developers and reducing the technical requirements for the development of the test platform. It can be seen that by setting the test execution node, the execution function of the test task is decoupled from the test processing device, and the update of service automation only needs to update the test execution node, avoiding frequent deployment and causing platform stability problems.

[0088] Step 406: Send the test result to the test processing device.

[0089] In addition, other operations performed on the test execution node side can refer to Figure 2 The technical content covered by the test method shown will not be elaborated here.

[0090] Next, through Figure 5 The information exchange process between the test processing device and the test execution node is briefly introduced. Here, the test processing device can be defined as a test device, and the test execution node is defined as an execution device. In fact, the test device can be connected to multiple distributed execution devices. Here, two execution devices A and B are taken as an example.

[0091] Step 502: Device A registers the test service on the test device.

[0092] Step 504: Device B registers the test service on the test device.

[0093] In this way, the test device maintains the registration information of the execution device A and the registration information of the execution device B, which is convenient for the subsequent matching and searching of the test service. The order of step 502 and step 504 is not limited, and they can also be executed simultaneously.

[0094] When a test requirement is triggered, the following steps 506 may be performed;

[0095] Step 506: The testing device obtains the test data to be processed.

[0096] Step 508: The test device creates a new test task according to the test data.

[0097] The newly created test task here assumes that its task type matches the test service deployed by execution device A.

[0098] Step 510: The test device sends the test task to the execution device A based on the test service matched by the test task.

[0099] Step 512: Execute device A to execute the test task.

[0100] Step 514: Execute device A to return the test result.

[0101] Step 516: The testing device generates a test report based on the test results.

[0102] This makes it easy for test users to view test reports, analyze test results, compare differences between test results and expected results, and summarize and analyze test results.

[0103] Through the above-mentioned test equipment and multiple execution equipment, the test service can be automated, and the configuration, execution, viewing, and other operations of the integrated tasks can be improved in one stop, which improves the test efficiency, shortens the test cycle, and improves the test quality. Moreover, the test system has strong versatility: through the distributed solution, the platform is more versatile and can adapt to various types of automated access platforms. In addition, the development cost is low: new requirements only need to focus on the automation implementation itself, and functions such as data configuration, task notification, and test results can directly reuse the platform capabilities without repeated development, which reduces the development cost. At the same time, the development threshold is lowered: automation can be achieved in any programming language and any framework, and there are no restrictions. The development threshold is lowered, allowing more development users to participate in development. Furthermore, the development cycle is shortened: because of the high reusability and low development threshold, more developers become more, which can greatly shorten the automation development cycle, let automation keep up with the service, and let the test use automation faster, so as to better complete the test.

[0104] It should be noted that the user information (including but not limited to user device information, user personal information, and test data generated by the target software, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0105] Embodiment 2

[0106] Reference Figure 6 As shown, a test processing device 600 provided in an embodiment of this specification is provided. The test processing device 600 and a plurality of test execution nodes form a test system. The plurality of test execution nodes are respectively configured with test services provided for the same or different categories of software. The device 600 may include:

[0107] The acquisition module 602 is used to acquire the test data to be processed.

[0108] The generating module 604 is used to generate a test task according to the test data to be processed, wherein the test task carries a task type.

[0109] The sending module 606 is used to send the test task to the test execution node corresponding to the test service determined based on the task type of the test task, so that the test execution node executes the test task according to the locally configured test service.

[0110] The receiving module 608 is used to receive the test result returned by the test execution node.

[0111] Optionally, as an embodiment, when acquiring the test data to be processed, the acquisition module 602 is specifically used to select one or more test data from the test data produced by the target software as the test data to be processed; or, to create new test data for the target software and use the newly created test data as the test data to be processed.

[0112] In a specific implementation of an embodiment of the present specification, when the generation module 604 generates a test task based on the test data to be processed, it is specifically used to: generate a test task based on the test data to be processed and basic configuration information, wherein the basic configuration information at least includes: one or more combinations of the module to be tested in the target software, the task type, the sending strategy and the notification strategy.

[0113] In another specific implementation of the embodiment of this specification, the test task also carries a sending strategy; when the sending module 606 sends the test task to the test execution node corresponding to the test service determined based on the task type of the test task, it is specifically used to:

[0114] The sending strategy is scheduled sending, then at the set sending timing of the test task, the test task is sent to the test execution node corresponding to the test service determined based on the task type of the test task; or,

[0115] The sending strategy is continuous sending, then when the sending of the previous test task is completed, the test task is sent to the test execution node corresponding to the test service determined based on the task type of the test task; or,

[0116] The sending strategy is manual sending, then in response to a triggering operation of a user on an interactive interface, the test task is sent to a test execution node corresponding to a test service determined based on a task type of the test task.

[0117] In another specific implementation of the embodiments of this specification, the test processing device maintains node registration information of multiple test execution nodes generated after the test processing device is registered; when the sending module 606 sends the test task to the test execution node corresponding to the test service determined based on the task type of the test task, it is specifically used to: based on the task type of the test task, search from the node registration information for a test execution node whose test task matches the task type and is in an idle state; and send the test task to the found test execution node.

[0118] In another specific implementation of the embodiments of the present specification, the test processing device interacts with the multiple test execution nodes through an open application programming interface; when the test service of the test execution node changes, the receiving module 608 is also used to receive the change information returned by the test execution node whose test service has changed through the open application programming interface, and update the node registration information corresponding to the test execution node based on the change information.

[0119] In another specific implementation of the embodiment of the present specification, after the receiving module 608 receives the test result returned by the test execution node, the generating module 604 is further used to summarize and analyze at least one test result and generate a test report.

[0120] In another specific implementation of the embodiments of the present specification, the device 600 also includes: a query module; the query module is used to query the test results and / or test reports matching the query request based on the query request triggered by the user, and display them on the interactive interface.

[0121] Reference Figure 7 As shown, a test execution node 700 provided in an embodiment of this specification is configured with test services provided for the same or different categories of software; the test execution node 700 may include:

[0122] A receiving module 702 is used to receive a test task, wherein the test task is generated by the test processing device according to the acquired test data to be processed, and sent by the test processing device to a test execution node corresponding to a test service determined based on a task type of the test task;

[0123] An execution module 704, configured to execute the test task according to the locally configured test service;

[0124] The sending module 706 is used to send the test result to the test processing device.

[0125] Among them, the test execution node 700 can be a distributed node, which can bind multiple nodes to the test processing device through registration through a distributed design, and build a test system that can not only ensure general functions but also support various test service requirements, thereby helping to improve test quality and test efficiency.

[0126] By building a universal test processing device and multiple test execution nodes supporting different test services connected to the test processing device, the test data to be processed is obtained through the test processing device, a test task is generated according to the test data to be processed, and the test task is sent to the test execution node corresponding to the test service determined based on the task type of the test task, so that the test execution node executes the test task according to the locally configured test service and returns the test result to the test processing device. Thus, while providing universal test functions based on the test processing device, it can also support the implementation of different types of test services based on the test execution node, reduce costs and development cycles, and improve test flexibility, universality and test efficiency.

[0127] Embodiment 3

[0128] Figure 8a and Figure 8b This is a schematic diagram of the structure of an electronic device according to an embodiment of this specification. Figure 8a and Figure 8b At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0129] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8a and Figure 8b Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0130] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0131] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a test processing device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0132] Acquire the test data to be processed; generate a test task based on the test data to be processed, wherein the test task carries a task type; send the test task to a test execution node corresponding to a test service determined based on the task type of the test task, so that the test execution node executes the test task according to the locally configured test service; and receive the test result returned by the test execution node.

[0133] or,

[0134] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a test execution node at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0135] Receive a test task, wherein the test task is generated by the test processing device based on the acquired test data to be processed, and sent by the test processing device to a test execution node corresponding to a test service determined based on a task type of the test task; execute the test task according to a locally configured test service; and send the test result to the test processing device.

[0136] The above is as in this manual Figure 2-Figure 4The method performed by the device or node disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in one or more embodiments of this specification may be implemented or executed. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in conjunction with one or more embodiments of this specification may be directly embodied as being executed by a hardware decoding processor, or may be executed by a combination of hardware and software modules in a decoding processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0137] The electronic device may also perform Figure 2-Figure 4 method, and implement the corresponding device or node in Figure 2-Figure 4 The functions of the illustrated embodiments will not be described in detail in the embodiments of this specification.

[0138] Of course, in addition to software implementation, the electronic device of the embodiments of this specification does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc., that is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0139] Embodiment 4

[0140] The embodiment of the present specification also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to execute Figure 2-Figure 4 The method of the embodiment shown is specifically used to perform the following method:

[0141] Acquire the test data to be processed; generate a test task based on the test data to be processed, wherein the test task carries a task type; send the test task to a test execution node corresponding to a test service determined based on the task type of the test task, so that the test execution node executes the test task according to the locally configured test service; and receive the test result returned by the test execution node.

[0142] or,

[0143] Receive a test task, wherein the test task is generated by the test processing device based on the acquired test data to be processed, and sent by the test processing device to a test execution node corresponding to a test service determined based on a task type of the test task; execute the test task according to a locally configured test service; and send the test result to the test processing device.

[0144] In short, the above description is only a preferred embodiment of this specification and is not intended to limit the protection scope of this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in the protection scope of this specification.

[0145] The systems, devices, modules or units described in one or more of the above embodiments may be implemented by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0146] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0147] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0148] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0149] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

Claims

1. A testing method, applied to a testing system comprising a testing processing device and a plurality of test execution nodes, wherein the plurality of test execution nodes are respectively configured with testing services provided for the same or different categories of software; The test method on the test processing device side includes: Get the test data to be processed; Generate a test task according to the test data to be processed, wherein the test task carries a task type; Sending the test task to a test execution node corresponding to a test service determined based on a task type of the test task, so that the test execution node executes the test task according to a locally configured test service; Receive the test result returned by the test execution node.

2. The test method according to claim 1, wherein obtaining the test data to be processed comprises: Select one or more test data from the test data generated by the target software as the test data to be processed; or, Create new test data for the target software and use the newly created test data as the test data to be processed; or, Select one or more test data from the test data generated by the target software, and create new test data for the target software; The selected one or more test data and the newly created test data are used as the test data to be processed.

3. The test method according to claim 2, generating a test task according to the test data to be processed, specifically comprising: A test task is generated according to the test data to be processed and basic configuration information, wherein the basic configuration information at least includes: one or more combinations of a module to be tested in the target software, a task type, a sending strategy, and a notification strategy.

4. The test method according to claim 1, wherein the test task also carries a sending strategy; sending the test task to a test execution node corresponding to a test service determined based on a task type of the test task, specifically comprising: The sending strategy is scheduled sending, then at the set sending timing of the test task, the test task is sent to the test execution node corresponding to the test service determined based on the task type of the test task; or, The sending strategy is continuous sending, then when the sending of the previous test task is completed, the test task is sent to the test execution node corresponding to the test service determined based on the task type of the test task; or, The sending strategy is manual sending, then in response to a triggering operation of a user on an interactive interface, the test task is sent to a test execution node corresponding to a test service determined based on a task type of the test task.

5. The test method according to claim 4, wherein the test processing device maintains node registration information of multiple test execution nodes generated after the test processing device is registered; Sending the test task to a test execution node corresponding to a test service determined based on a task type of the test task specifically includes: Based on the task type of the test task and the node registration information, determine a test execution node whose test service matches the task type and is in an idle state; The test task is sent to the found test execution node.

6. The test method according to claim 5, wherein the test processing device interacts with the plurality of test execution nodes through an open application programming interface; when the test service of the test execution node changes, the method further comprises: The change information returned by the test execution node whose test service has changed is received through the open application programming interface, and the node registration information corresponding to the test execution node is updated based on the change information.

7. The test method according to any one of claims 1 to 6, after receiving the test result returned by the test execution node, the method further comprises: Summarize and analyze at least one test result and generate a test report.

8. The testing method according to claim 7, further comprising: Based on the query request triggered by the user, the test results and / or test reports matching the query request are queried and displayed on the interactive interface.

9. A testing method, applied to a testing system comprising a test processing device and a plurality of test execution nodes, wherein the plurality of test execution nodes are respectively configured with test services provided for the same or different categories of software; The test method on the test execution node side includes: Receiving a test task, wherein the test task is generated by the test processing device according to the acquired test data to be processed, and sent by the test processing device to a test execution node corresponding to a test service determined based on a task type of the test task; Execute the test task according to the locally configured test service; The test result is sent to the test processing device.

10. A test processing device, the test processing device and a plurality of test execution nodes forming a test system, wherein the plurality of test execution nodes are respectively configured with test services provided for the same or different categories of software; The test processing device comprises: An acquisition module is used to acquire the test data to be processed; A generating module, used for generating a test task according to the test data to be processed, wherein the test task carries a task type; A sending module, used for sending the test task to a test execution node corresponding to a test service determined based on a task type of the test task, so that the test execution node executes the test task according to a locally configured test service; The receiving module is used to receive the test result returned by the test execution node.

11. A test execution node, the test execution node being configured with test services provided for software of the same or different categories; The test execution node includes: A receiving module, configured to receive a test task, wherein the test task is generated by the test processing device according to the acquired test data to be processed, and is sent by the test processing device to a test execution node corresponding to a test service determined based on a task type of the test task; An execution module, used to execute the test task according to the locally configured test service; The sending module is used to send the test result to the test processing device.

12. A testing system comprising: A test processing device and a plurality of test execution nodes connected to the test processing device, wherein the plurality of test execution nodes are respectively configured with test services provided for the same or different categories of software; wherein, The test processing device is used to obtain the test data to be processed, and generate a test task according to the test data to be processed, wherein the test task carries a task type; and is used to send the test task to a test execution node corresponding to the test service determined based on the task type of the test task; The test execution node is used to receive a test task and execute the test task according to a locally configured test service; and to send a test result to the test processing device.

13. An electronic device, comprising: processor; as well as A memory arranged to store computer executable instructions, which when executed cause the processor to perform the testing method according to any one of claims 1 to 9.

14. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of application programs, enable the electronic device to execute the testing method according to any one of claims 1 to 9.

Images