WO2020233034A1 - Page function testing method and related device - Google Patents

Abstract

Disclosed are a page function testing method and a related device. The method is applicable to H5 application performance testing. The method comprises: receiving voice information of a user feeding back a page function, and performing semantic analysis on the voice information to convert the voice information into text information; performing information processing on the text information to obtain a plurality of test keywords, and determining a function node to be tested on a target page according to operation steps described by the plurality of test keywords; determining a plurality of sub-test cases matching the plurality of test keywords from a test case feature library; and generating a target test case according to the plurality of sub-test cases, and testing said function node on the target page on the basis of the target test case. By adopting the embodiments of the present application, said functional node can be quickly positioned on the basis of the voice information content, the corresponding testing can be implemented, the response speed is high, and the applicability is high.

Description

A page function test method and related device

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on May 21, 2019, the application number is 201910421957.6, and the invention title is "a page function testing method and related device", the entire content of which is incorporated herein by reference Applying.

Technical field

This application relates to the field of computer technology, and in particular to a page function testing method and related devices.

Background technique

With the rapid development of science and technology and the progress of industry, various electronic consumer products such as personal computers, mobile phones, tablet computers, etc. have emerged that enhance people's quality of life and change people's life patterns. People's dependence on these devices is also increasing. More and more manufacturers are committed to producing more related products. Therefore, manufacturers are all committed to improving product performance. Before a product or a mobile device-based software manufactured by a mobile device manufacturer goes on the market, it is usually necessary to perform a page function test on the pages of the software to test whether the functions of each page on the computer platform product or software version are normal.

In recent years, computer platform products or software versions have been updated more and more frequently, and each version release requires testing of various page functions on the software. After receiving user feedback and/or complaints, it is necessary to write test cases for specific issues to perform related functional tests. The processing cycle is long and the test efficiency is not high.

Summary of the invention

The embodiments of the present application provide a page function testing method and related devices, which can save server resources and improve the execution efficiency of dependency analysis.

In the first aspect, an embodiment of the present application provides a page function testing method, which includes:

Receive the voice information of the user feedback page function, and perform semantic analysis on the voice information to convert the voice information into text information;

Perform information processing on the above text information to obtain multiple test keywords, and determine the functional node to be tested on the target page according to the operation steps described by the multiple test keywords, where one test keyword is used to describe the above user feedback An operation step of the page function;

Determine multiple sub-test cases matching the above multiple test keywords from the test case feature database, where one sub-test case is used to test an operation step of the above-mentioned functional node to be tested;

A target test case is generated based on the multiple sub-test cases, and the functional node to be tested on the target page is tested based on the target test case.

In the second aspect, an embodiment of the present application provides a page function testing device, which includes:

The receiving unit is configured to receive the voice information of the user feedback page function, and perform semantic analysis on the voice information to convert the voice information into text information;

The processing unit is configured to perform information processing on the text information obtained by the receiving unit to obtain multiple test keywords, and determine the functional node to be tested on the target page according to the operation steps described by the multiple test keywords, wherein, A test keyword is used to describe an operation step of the page function reported by the user;

The determining unit is used to determine, from the test case feature database, multiple sub-test cases matching the multiple test keywords obtained by the processing unit, wherein one sub-test case is used to test an operation step of the above-mentioned functional node to be tested;

The test unit is configured to generate a target test case based on the multiple sub-test cases determined by the determination unit, and test the functional node to be tested on the target page based on the target test case.

In a third aspect, an embodiment of the present application provides a terminal device. The terminal device includes a processor and a memory, and the processor and the memory are connected to each other. The memory is used to store a computer program that supports the terminal device to execute the method provided in the first aspect and/or any one of the possible implementations of the first aspect, the computer program includes program instructions, and the processor is configured to call the foregoing The program instructions execute the method provided in the first aspect and/or any possible implementation manner of the first aspect.

In a fourth aspect, embodiments of the present application provide a computer non-volatile readable storage medium, the computer non-volatile readable storage medium stores a computer program, and the above computer program is executed by a processor to implement the above first aspect The method provided by any possible implementation.

In the page function test, storing the test reports of different function nodes to be tested can avoid repeated tests when the same and/or similar page function problems occur, or adjust the target test cases and/or target test scenarios appropriately to achieve rapid The purpose of solving the problem.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only These are some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative work.

FIG. 1 is a schematic flowchart of a method for constructing a test case feature library provided by an embodiment of the present application;

2 is a schematic flowchart of a page function testing method provided by an embodiment of the present application;

FIG. 3 is a schematic structural diagram of a page function test device provided by an embodiment of the present application;

Fig. 4 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of this application.

The page function test method provided by the embodiment of the application (for convenience of description, the method provided in the embodiment of the application may be referred to as the method provided in the embodiment of the application) is applicable to various page function test systems in various fields and industries, and is not limited herein. The method provided by the embodiments of the present application may be based on a function sample library in an existing page function test system, or a function sample used to describe the page function is obtained based on an existing test sample to construct a test case feature library. Based on the test case feature library, it can test the function nodes to be tested on the target page contained in the user's voice information, so that the voice information input by the user can be tested correspondingly, and corresponding countermeasures can be proposed in time , Reduce the risk of major losses caused by page function errors. The page function testing method provided by the embodiments of the present application can construct different use case feature libraries based on different fields and/or different industries to be applicable to page function test systems of various fields or industries, with high flexibility and wide application range. For the convenience of description, the method provided in the embodiments of the present application will be described below by taking a page function test system in a certain field and/or a certain industry as an example.

The methods and related devices provided by the embodiments of the present application will be described below with reference to FIGS. 1 to 4 respectively. The method provided by the embodiment of the present application may include the construction of a test case feature library and the execution of tests based on the test case feature library and voice information input by the user.

Before receiving the voice information input by the user, a test case feature library can be constructed first. Refer to Fig. 1, which is a schematic flowchart of a method for constructing a test case feature library provided by an embodiment of the present application. The method for constructing the test case feature library provided by the embodiment of the present application can be described by the implementation manner provided in the following steps S11-S14.

S11. Obtain multiple functional samples for describing page functions.

In some feasible implementations, in the stage of obtaining multiple functional samples for describing page functions, multiple functional samples for describing page functions can be obtained from the functional sample library of the existing page function test system, or Obtain multiple functional samples used to describe page functions from the historical test records in the existing page function test system. It is also possible to establish multiple functional samples used to describe page functions based on the existing test environment and industry characteristics. The method of obtaining is not restricted here. It is important to note that the above function sample is only used to describe a page function. For example, the above functional sample can be the function of "click the select button, select the picture and upload", or it can be the function of "select the video and download", which is not limited here.

S12. Split the above-mentioned multiple function samples for describing page functions according to the operation steps of the page function to obtain multiple sub-function samples.

In some feasible implementation manners, in order to make the test cases in the finally constructed test case feature library more simple and specific, the test cases in the finally constructed test case feature library can be modularized as small as possible according to functions. That is, before generating test cases based on the multiple function samples used to describe the page function, the multiple function samples used to describe the page function are divided according to the operation steps of the page function to obtain multiple sub-function samples. Among them, a sub-function sample is used to describe an operation step of the function sample corresponding to the above-mentioned one sub-function sample. For example, for a functional sample of "click the select button, select a picture and upload", the sample can be split according to the three steps of "click the select button", "select picture" and "upload" to split the functional sample Into the simplest three sub-function samples.

S13. Generate multiple sub-test cases according to the operation steps described in the multiple sub-function samples.

In some feasible implementations, the function sample can be split to obtain multiple sub-function samples, and then multiple sub-test cases can be generated according to the operation steps described by the sub-function samples. Among them, the sub-test cases can be automatically generated by the page function test system. Generation, or the technical staff can write sub-test cases for different operation steps, which is not limited here. For example, before generating a test case for the "click the select button, select the picture and upload" functional sample, you can split the "click the select button, select the picture and upload" function sample into "click the select button" and "select the picture" After the three smaller sub-function samples of "" and "upload image", corresponding sub-test cases are generated for the three sub-function samples of "click to select", "select image" and "upload image". When it is necessary to generate a test case from the functional sample of "click the select button, select the document and upload", after splitting the functional sample, only the sub-function sample of "select document" can be generated into the corresponding sub-test case. The situation of repeatedly generating test cases for repeated functional samples is avoided, and the time waste caused by generating a large number of test cases is saved, and the applicability is higher.

In some feasible implementations, after splitting a function sample to obtain multiple sub-function samples and writing corresponding test cases for the multiple sub-function samples, the sub-tests with constraints can be generated according to actual test requirements Example. For example, after splitting "click the select button, select a picture and upload", you will get three sub-test cases of "click the select button", "select a picture" and "upload a picture". At this time, if there are certain requirements for the format and size of the picture in the actual test environment, you can generate sub-test cases that restrict the picture such as "gif format" and "not larger than 5M" according to the actual situation, with specific constraints The constraint conditions of the sub-test cases can be selected according to the actual test scenario, etc., and there is no restriction here. It should be particularly noted that when generating corresponding sub-test cases based on the above multiple sub-function samples, the operation steps and specific test methods described in each sub-function sample can be used, including but not limited to "equivalent class method", " Boundary value method, “decision table method”, “orthogonal experiment method”, “process analysis method” and “state transition method” and other commonly used methods for test cases are not limited here.

S14. Construct the above-mentioned test case feature library based on the above-mentioned multiple sub-test cases.

In some feasible implementations, in order to quickly find the sub-test case corresponding to a certain operation step from the finally constructed test case feature library, after generating the corresponding sub-test case according to the above-mentioned sub-function samples to obtain multiple sub-test cases, It can automatically summarize the characteristic words of the operation steps described in the corresponding sub-function sample used by each sub-test case for testing, such as "login", "upload" and "download" and other characteristic words, which are not limited here. Among them, when summarizing each sub-test case to test the characteristic words of a certain operation step, function tags can be automatically added to each sub-test case to mark the operation steps tested by each sub-test case, or it can be based on a certain sub-test case. Add the corresponding feature word to the parameter. In addition, the use case feature word configuration interface can also be established through the existing feature word tags and custom feature word tags. Based on the use case feature word configuration interface, you can add functional tags to each of the above sub-test cases or add feature words and store them in the specified The final test case feature library has been obtained in the storage space, and the above-mentioned designated storage space can be a certain database, or it can be in the cloud and/or storage device, which is not limited here. It should be specially noted that by customizing the feature word label, the range of feature words of each sub-test case in the test case feature library can be expanded, and at the same time, it can also be used to adjust features such as "swipe from left to right on the touch screen", "double tap Uncommon or more special sub-function samples in functional samples such as “Control Screen”, such as “swipe from left to right”, “touch screen”, etc., provide the function of customizing and summarizing feature words and/or adding function tags, which is more flexible High, wider application range.

After the test case feature library is obtained, the page function can be tested based on the voice information input by the user. Please refer to FIG. 2, which is a schematic flowchart of a page function testing method provided by an embodiment of the present application. The method provided by the embodiment of the present application may include the following steps S21-S24:

S21: Receive the voice information of the user feedback page function, and perform semantic analysis on the voice information to convert the voice information into text information.

Optionally, when the voice information input by the user is received, the voice information input by the user can be semantically analyzed to directly obtain the text information corresponding to all the voice information, and then extract the target page and the target page to be tested from the text information Text information related to functional information; semantic analysis can also be performed on the voice information input by the user to obtain the target voice information related to the target page and the functional node to be tested on the target page, and then the target voice information is converted into text information for specific implementation The method is not limited here. For example, when the user complains and/or feedbacks the problem of uploading pictures on the service submission page through voice, the semantic analysis of all voice input by the user (here, voice M is taken as an example) is performed to obtain the text m corresponding to voice M, and then from Extract the text n of "On the business submission page, after clicking the select button, the selected picture cannot be uploaded"; you can also perform semantic analysis on all the voice M input by the user to obtain the description "On the business submission page, click to select After pressing the button, select the voice N that says "The picture cannot be uploaded", and then convert the voice N to the text n of "On the service submission page, after clicking the select button, select the picture that cannot be uploaded", according to different application scenarios and device performance requirements , It can adopt different implementation methods, with high flexibility.

S22: Perform information processing on the text information to obtain multiple test keywords, and determine the functional node to be tested on the target page according to the operation steps described by the multiple test keywords.

In some feasible implementation manners, since the voice information input by the user is complicated and the amount of information is large, only the voice information of the user feedback page function can be received, and then semantic analysis of the voice information is performed to convert the voice information into text information. . It is also possible to perform semantic analysis on all the above-mentioned voice information to obtain text information after receiving all the voice information of the user, and then perform information content filtering on the text information to obtain text information related to page functions. It is also possible to obtain text information related to the page function directly from the voice content of the user feedback page function through semantic analysis in the stage of receiving the voice information input by the user.

In some feasible implementation manners, after obtaining the text information corresponding to the voice information of the user feedback page function, information processing is performed on the above text information (including but not limited to text recognition, information matching, etc., which are not limited here) To identify the content described in the above text information. At the same time, in the process of information processing on the text information, multiple test keywords used to describe the operation steps of the page function fed back by the user can be extracted from the text information. The above text information can also be matched with each test keyword in the existing test keyword library to obtain multiple test keywords used to describe the operation steps of the page function feedback from the user. The specific implementation is not done here. limit. It should be particularly noted that the above test keyword is used to describe an operation step of the page function reported by the user. According to the operation steps described by the multiple test keywords obtained above, the target page to be tested and the function node to be tested on the target page can be determined, where the function node to be tested is a certain page on the specific page feedback by the user Functional issues. For example, when the user submits the page through the voice feedback service, there is a functional problem, and after semantic analysis, the text information "on the service submission page, after clicking the select button, the selected picture cannot be uploaded" is obtained, and the text information is processed after information processing Three test keywords of "click to select", "select picture" and "upload picture" can be obtained. At the same time, based on the operation steps described in the above three test keywords, the target page can be determined as the business submission page and the business submission page The function node to be tested is "The selected picture cannot be uploaded after clicking the select button".

S23. Determine multiple sub-test cases matching the multiple test keywords from the test case feature database.

In some feasible implementations, after multiple test keywords are obtained, the function tags of each sub-test case in the above-mentioned test case feature library can be matched with each test keyword in the above-mentioned multiple test keywords. After the function label of any sub-test case matches any test keyword successfully, any sub-test case marked by any function label that matches any test keyword can be determined to correspond to any of the above-mentioned test keywords Until the sub-test case corresponding to each test keyword among the above-mentioned multiple test keywords is obtained, wherein the sub-test case corresponding to any one of the above-mentioned test keywords is used to test the above-mentioned An operation step in the function node to be tested. For example, after the three test keywords of "click to select", "select picture", and "upload picture" are obtained, the function label of each sub-test case in the test case feature library can be combined with the "click to select button". , "Select a picture" and "Upload a picture" three test keywords are matched to obtain sub-test cases for testing the three operation steps of "click the selection button", "select a picture" and "upload a picture".

In some feasible implementation manners, after the target page is determined based on the above text information, the specific scenario, model, communication method, etc. of the page function problem that the user complains and/or feedback can be determined based on the above text information. Do restrictions. For example, based on the above text information, it can be obtained that the model of the mobile phone device that caused the problem is A, the mobile phone device adopts the mobile 4G communication method when the problem occurs, and the problem occurs when the APP is logged in. It can accurately locate the user's voice complaints and/or feedback problems in an unsupported environment, which improves the accuracy of the description and avoids unnecessary consumption of labor costs. In some feasible implementations, since some users may complain and/or feedback page function problems through voice, the problem may be unclear. Therefore, preset smart sentences are used in the process of users complaining and/or feedback through voice. Guide the user to describe the problem in more detail and accurately, so as to obtain the user's complete voice information describing the problem. At the same time, before the user complains and/or suggests through the voice, the user can choose the necessary features of the problem by the user through the preset options. For example, after the user dials the phone, the user first selects the device model, problem type and other options to reduce the voice The system loss caused by the excessive amount of information has better flexibility and higher accuracy.

S24. Generate a target test case based on the multiple sub-test cases, and test the functional node to be tested on the target page based on the target test case.

In some feasible implementation manners, after the sub-test cases corresponding to the multiple test keywords are obtained, the sub-test cases corresponding to the multiple test keywords may be arranged in the order of the function expression of the function node to be tested to obtain A test case group, and based on the above test case group to generate target test cases. Among them, when generating a target test case based on the above test case group, the Pairwise Independent Combinatorial Testing Tool (PICT), Allpairs tool, and other test case combination tools can be used, and there is no restriction here. For example, after getting the sub-test cases used to test the three operation steps of "select image", "click to select button" and "upload image", you can base on the function of the function node to be tested "selected image cannot be uploaded after clicking the select button" The order of presentation Arrange the sub-test cases of the three operation steps of "select image", "click to select button" and "upload image" in the order of "click to select button", "select image" and "upload image" to get a test case group. At the same time, based on the above-mentioned test case combination tool, the test case group is subjected to test case combination processing to obtain the target test case of "click the select button, select the picture and upload".

In some feasible implementations, after the target test cases are obtained, the specific scenarios, models, communication methods and other information of the user complaints and/or feedback page function problems determined based on the text information can be used to construct the target page. The target test scenario corresponding to the operating environment of the operating environment, and the functional node to be tested on the target page is tested based on the target test case in the target test scenario. For example, based on the above text information, it is determined that the user complaint and/or feedback page function problem is "Under the mobile 4G network environment, the picture cannot be uploaded after the selection button is clicked on the service submission page of the mobile phone with the device model A", and you get " After clicking the select button, select the picture and upload the target test case, you can build a test case for testing the function node to be tested of "click the select button, select the picture and upload" in the mobile 4G network environment, in the device model A The business submission page in the mobile phone" target test scenario, and in the target test scenario, the page function of "In the mobile 4G network environment, the image cannot be uploaded after the selection button is clicked on the business submission page in the mobile phone with device model A" Questions are tested.

In some feasible implementation manners, when constructing the above-mentioned test case feature library, the sub-scenario keyword set can be pre-placed in the above-mentioned test case feature library to obtain multiple test scenario keys while obtaining the above multiple test keywords. word. When matching the feature tags of each sub-test case in the above-mentioned test case feature library with the above multiple test keywords, the key to the above multiple test scenarios can be extracted from the sub-scenario keyword set in the above-mentioned test case feature library. Multiple sub-scenario keywords with the same words are used to construct a target test scenario based on the multiple sub-scenario keywords and the target page when the target test case is generated. For example, after obtaining the sub-scenario keywords of “mobile 4G” and “A mobile phone”, based on the target page of the “business submission page” mentioned above, the “business in the mobile phone of device model A under the mobile 4G network environment can be constructed The target test scenario of "Submit Page". It is important to note that when only "mobile 4G" and "mobile" sub-scenario keywords can be extracted from the above use case feature library, and the specific model of the mobile phone cannot be known, then it is necessary to extract the sub-scenario key from the above use case feature library Get sub-scenario keywords related to the "mobile phone" keywords, such as "A model phone", "B model phone" and other sub-scenario keywords from the word, respectively, and get "Business submission in a mobile phone with device model A in a mobile 4G network environment Multiple target test scenarios such as "page" and "business submission page in a mobile phone with device model B under the mobile 4G network environment". And in multiple target test scenarios, the function nodes to be tested of "click the selection button, select the picture and upload" are tested to test out user complaints and/or feedback voice information of the same or similar page function problems, which improves the reliability. Speed and accuracy of page function test without support.

In some feasible implementation manners, the number of tests may also be defined according to the importance of different functional nodes to be tested, so as to improve the accuracy of the page function test. For example, if it is a login function, 10 tests can be performed, and if it is a more serious crash function, 20 tests can be performed. The definition of the specific number of tests and the division of importance of the function can be defined according to the actual situation, and there is no restriction here. . After the page function test is completed, the test data after testing the function node to be tested on the target page can be obtained, and the target test report corresponding to the function node to be tested on the target page is generated based on the test data. At the same time, the target test report is stored in the designated storage space to obtain a backup test report. When displaying and/or querying the test report corresponding to any one of the above-mentioned functional nodes to be tested based on the display device, obtain the test report corresponding to any one of the above-mentioned functional nodes to be tested from the above-mentioned standby test report and correspond to any one of the above-mentioned functional nodes to be tested The test report is output to the above-mentioned display device, so that when users complain and/or report the same page function problem again, they can avoid repeated tests or make appropriate adjustments to the target test cases and/or target test scenarios, so as to achieve the purpose of quickly solving the problem. At the same time, based on the test report, the corresponding solutions to the page function problems can be put forward with higher applicability.

The embodiment of this application can directly determine the target page and the functional node to be tested based on the voice information input by the user, and quickly generate the target test case and target test scenario to perform the functional test on the functional node to be tested on the target page. Under the circumstances, the page function is quickly tested.

Refer to FIG. 3, which is a schematic structural diagram of a page function testing device provided by an embodiment of the present application. The page function test device provided by the embodiment of the application includes:

The receiving unit is configured to receive the voice information of the user feedback page function, and perform semantic analysis on the voice information to convert the voice information into text information;

The processing unit is configured to perform information processing on the text information obtained by the receiving unit to obtain multiple test keywords, and determine the functional node to be tested on the target page according to the operation steps described by the multiple test keywords, wherein, A test keyword is used to describe an operation step of the page function reported by the user;

The determining unit is used to determine, from the test case feature database, multiple sub-test cases matching the multiple test keywords obtained by the processing unit, wherein one sub-test case is used to test an operation step of the above-mentioned functional node to be tested;

The test unit is configured to generate a target test case based on the multiple sub-test cases determined by the determination unit, and test the functional node to be tested on the target page based on the target test case.

In some feasible implementation manners, the foregoing device further includes:

The obtaining unit is also used to obtain multiple function samples for describing page functions from the function sample library of the page function test system, and/or obtain multiple description pages from the historical test records in the above page function test system Function samples of functions, where a function sample is used to describe a page function;

The generating unit is also used to construct the above-mentioned test case feature library based on the above-mentioned multiple functional samples for describing page functions.

In some feasible implementation manners, the aforementioned generating unit is used to:

The above multiple function samples used to describe the page function are split according to the operation steps of the page function to obtain multiple sub-function samples, wherein one sub-function sample is used to describe an operation step of the function sample corresponding to the above-mentioned one sub-function sample ；

Generate multiple sub-test cases according to the operation steps described in the above multiple sub-function samples, where one sub-test case is used to test an operation step described in the sub-function sample corresponding to the above-mentioned one sub-test case, and the above-mentioned sub-test case corresponds to one function Label, the above-mentioned function label is used to mark the operation step tested by the above-mentioned one sub-test case;

Construct the above-mentioned test case feature library based on the above-mentioned multiple sub-test cases.

In some feasible implementation manners, the aforementioned generating unit is used to:

Determine the characteristic words of the operation steps corresponding to each sub-test case;

Store each of the above sub-test cases and corresponding feature words to obtain a test case feature library.

In some feasible implementation manners, the above-mentioned test device further includes:

The matching unit is used to match the function label of each sub-test case in the above-mentioned test case feature library with each of the above-mentioned multiple test keywords;

The above-mentioned generating unit is used to determine any sub-test case marked by any function tag that matches any test keyword as the sub-test case corresponding to any one of the above-mentioned test keywords, so as to determine the above-mentioned multiple test keys Multiple sub-test cases corresponding to the word.

In some feasible implementation manners, the aforementioned generating unit is used to:

Arrange the above multiple sub-test cases according to the function expression order of the above-mentioned functional nodes to be tested to obtain a test case group, and generate a target test case based on the above-mentioned test case group;

A target test scenario corresponding to the operating environment of the target page is constructed, and the functional node to be tested on the target page is tested based on the target test case in the target test scenario.

In some feasible implementation manners, the above-mentioned test unit is also used for:

Obtain test data after testing the functional node to be tested on the target page, and generate a target test report corresponding to the functional node to be tested on the target page based on the test data;

Store the target test report in a designated storage space to obtain a backup test report, and the designated storage space also includes test reports of one or more other functional nodes to be tested except for the functional node to be tested;

When displaying and/or querying the test report corresponding to any one of the above-mentioned functional nodes to be tested based on the display device, obtain the test report corresponding to any one of the above-mentioned functional nodes to be tested from the above-mentioned standby test report and correspond to any one of the above-mentioned functional nodes to be tested The test report is output to the above display device.

In some feasible implementation manners, the foregoing receiving unit is used to:

Analyze the above voice information to obtain target voice information related to the functional node to be tested on the target page;

Convert the above target voice information into text information.

In some feasible implementation manners, the above-mentioned test case feature library includes a set of sub-scenario keywords; the above-mentioned generating unit is used for:

Match the above-mentioned sub-scene keyword set with each of the above-mentioned test keywords to obtain multiple sub-scene keywords;

A target test scenario is constructed based on the multiple sub-scene keywords and the target page.

In a specific implementation, the above-mentioned device can execute the implementation manners provided in the steps in Figures 1 to 2 through the built-in modules.

The page function device provided by the embodiment of the present application can directly determine the target page and the function node to be tested based on the voice information input by the user, and quickly generate target test cases and target test scenarios to perform functional tests on the function nodes to be tested on the target page. Quickly test the page function without the support of no one, with good flexibility and high applicability.

Fig. 4 is a schematic structural diagram of a terminal device provided by an embodiment of the present application. As shown in FIG. 4, the terminal device in this embodiment may include: one or more processors 41 and memory 42. The aforementioned processor 41 and memory 42 are connected by a bus 43. The memory 42 is used to store a computer program, and the computer program includes program instructions, and the processor 41 is used to execute the program instructions stored in the memory 42 to perform the following operations:

Receive the voice information of the user feedback page function, and perform semantic analysis on the voice information to convert the voice information into text information;

Perform information processing on the above text information to obtain multiple test keywords, and determine the functional node to be tested on the target page according to the operation steps described by the multiple test keywords, where one test keyword is used to describe the above user feedback An operation step of the page function;

Determine multiple sub-test cases matching the above-mentioned multiple test keywords from the test-case feature library, where one sub-test case is used to test an operation step of the above-mentioned functional node to be tested;

A target test case is generated based on the multiple sub-test cases, and the functional node to be tested on the target page is tested based on the target test case.

In some feasible implementation manners, the foregoing processor 41 is further configured to:

Obtain multiple functional samples used to describe page functions from the functional sample library of the page function test system, and/or obtain multiple functional samples used to describe page functions from the historical test records in the above-mentioned page function test system, where , A function sample is used to describe a page function;

Construct the above-mentioned test case feature library based on the above-mentioned multiple functional samples used to describe page functions.

In some feasible implementation manners, the aforementioned processor 41 is used to:

The above multiple function samples used to describe the page function are split according to the operation steps of the page function to obtain multiple sub-function samples, wherein one sub-function sample is used to describe an operation step of the function sample corresponding to the above-mentioned one sub-function sample ；

Generate multiple sub-test cases according to the operation steps described in the above multiple sub-function samples, where one sub-test case is used to test an operation step described in the sub-function sample corresponding to the above-mentioned one sub-test case, and the above-mentioned sub-test case corresponds to one function Label, the above-mentioned function label is used to mark the operation step tested by the above-mentioned one sub-test case;

Construct the above-mentioned test case feature library based on the above-mentioned multiple sub-test cases.

In some feasible implementation manners, the aforementioned processor 41 is used to:

Determine the characteristic words of the operation steps corresponding to each sub-test case;

Store each of the above sub-test cases and corresponding feature words to obtain a test case feature library.

In some feasible implementation manners, the aforementioned processor 41 is used to:

Match the function label of each sub-test case in the above-mentioned test case feature library with each of the above-mentioned multiple test keywords respectively;

Determine any sub-test case marked by any functional label that matches any test keyword as the sub-test case corresponding to any of the above-mentioned test keywords to determine multiple sub-test cases corresponding to the above-mentioned multiple test keywords Test case.

In some feasible implementation manners, the aforementioned processor 41 is used to:

Arrange the above multiple sub-test cases according to the function expression order of the above-mentioned functional nodes to be tested to obtain a test case group, and generate a target test case based on the above-mentioned test case group;

A target test scenario corresponding to the operating environment of the target page is constructed, and the functional node to be tested on the target page is tested based on the target test case in the target test scenario.

In some feasible implementation manners, the foregoing processor 41 is further configured to:

Obtain test data after testing the functional node to be tested on the target page, and generate a target test report corresponding to the functional node to be tested on the target page based on the test data;

Store the target test report in a designated storage space to obtain a backup test report, and the designated storage space also includes test reports of one or more other functional nodes to be tested except for the functional node to be tested;

When displaying and/or querying the test report corresponding to any one of the above-mentioned functional nodes to be tested based on the display device, the test report corresponding to any one of the above-mentioned functional nodes to be tested is obtained from the above-mentioned standby test report and corresponds to any of the above-mentioned functional nodes The test report is output to the above display device.

In some feasible implementation manners, the aforementioned processor 41 is used to:

Analyze the above voice information to obtain target voice information related to the functional node to be tested on the target page;

Convert the above target voice information into text information.

In some feasible implementation manners, the above-mentioned test case feature library includes a set of sub-scenario keywords; the above-mentioned processor 41 is used for:

Match the above-mentioned sub-scene keyword set with each of the above-mentioned test keywords to obtain multiple sub-scene keywords;

A target test scenario is constructed based on the multiple sub-scene keywords and the target page.

It should be understood that in some feasible implementation manners, the aforementioned processor 41 may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors or digital signal processors (digital signal processors, DSP). , Application specific integrated circuit (ASIC), ready-made programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.

The memory 42 may include a read-only memory and a random access memory, and provides instructions and data to the processor 41. A part of the memory 42 may also include a non-volatile random access memory. For example, the memory 42 may also store device type information.

In specific implementation, the above-mentioned terminal device can execute the implementation manners provided in the steps in Figures 1 to 2 through its built-in functional modules. For details, refer to the implementation manners provided in the above-mentioned steps, which will not be repeated here.

The embodiment of this application can directly determine the target page and the functional node to be tested based on the voice information input by the user, and quickly generate the target test case and target test scenario to perform the functional test on the functional node to be tested on the target page. Under the circumstances, the page function is quickly tested.

The embodiment of the present application also provides a computer non-volatile readable storage medium, the computer non-volatile readable storage medium stores a computer program, and the computer program is executed by a processor to implement each step in FIGS. 1 to 2 For the provided method, please refer to the implementation manner provided in the above steps for details, which will not be repeated here.

The foregoing computer non-volatile readable storage medium may be the task processing apparatus provided in any of the foregoing embodiments or the internal storage unit of the foregoing terminal device, such as a hard disk or memory of an electronic device. The computer's non-volatile readable storage medium may also be an external storage device of the electronic device, such as a plug-in hard disk, a smart media card (SMC), and a secure digital (smart media card) equipped on the electronic device. SD card, flash card, etc. The above-mentioned computer non-volatile readable storage medium may also include a magnetic disk, an optical disk, a read-only memory (read-only memory, ROM), or a random access memory (random access memory, RAM). Further, the computer non-volatile readable storage medium may also include both an internal storage unit of the electronic device and an external storage device. The computer non-volatile readable storage medium is used to store the computer program and other programs and data required by the electronic device. The computer non-volatile readable storage medium can also be used to temporarily store data that has been output or will be output.

The terms "first" and "second" in the claims, specification and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. Reference to "embodiments" herein means that a specific feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The display of the phrase in various positions in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art clearly and implicitly understand that the embodiments described herein can be combined with other embodiments. The term "and/or" used in the specification of this application and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes these combinations.

A person of ordinary skill in the art may realize that the units and algorithm steps of the examples described in the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two, in order to clearly illustrate the hardware and software Interchangeability. In the above description, the composition and steps of each example have been generally described in terms of function. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of this application.

The above-disclosed are only the preferred embodiments of the application, which of course cannot be used to limit the scope of rights of the application. Therefore, equivalent changes made according to the claims of the application still fall within the scope of the application.

Claims (20)

A page function testing method, characterized in that the method includes: Receiving the voice information of the user feedback page function, and performing semantic analysis on the voice information to convert the voice information into text information; Perform information processing on the text information to obtain multiple test keywords, and determine the functional node to be tested on the target page according to the operation steps described by the multiple test keywords, wherein one test keyword is used to describe An operation step of the page function fed back by the user; Multiple sub-test cases matching the multiple test keywords are determined from the test case feature database, wherein one sub-test case is used to test an operation step of the functional node to be tested; A target test case is generated according to the multiple sub test cases, and the functional node to be tested on the target page is tested based on the target test case. The method according to claim 1, wherein before the receiving the voice information input by the user, the method further comprises: Obtain multiple function samples for describing page functions from the function sample library of the page function test system, and/or obtain multiple function samples for describing page functions from historical test records in the page function test system, Among them, a function sample is used to describe a page function; The test case feature database is constructed based on the multiple functional samples used to describe the page functions. The method according to claim 2, wherein the constructing the test case feature library based on the plurality of functional samples used to describe page functions comprises: The multiple function samples used to describe the page function are split according to the operation steps of the page function to obtain multiple sub-function samples, wherein one sub-function sample is used to describe one of the function samples corresponding to the one sub-function sample. Steps; Generate multiple sub-test cases according to the operation steps described in the multiple sub-function samples, where one sub-test case is used to test an operation step described in the sub-function sample corresponding to the one sub-test case, and the one sub-test case Corresponding to a function label, the one function label is used to mark the operation step tested by the one sub-test case; The test case feature database is constructed based on the multiple sub test cases. The method according to claim 3, wherein the constructing the test case feature database based on the multiple sub test cases comprises: Determine the characteristic words of the operation steps corresponding to each sub-test case; Store each sub-test case and the corresponding feature word to obtain a test case feature library. The method according to claim 3, wherein the determining, from the test case feature database, a plurality of sub-test cases matching the plurality of test keywords comprises: Matching the function label of each sub-test case in the test case feature library with each of the multiple test keywords; Determine any sub-test case marked by any function tag that matches any test keyword as the sub-test case corresponding to any test keyword, so as to determine the corresponding test keyword Multiple sub-test cases. The method according to claim 5, wherein the generating a target test case according to the multiple sub-test cases, and testing the functional node to be tested on the target page based on the target test case comprises: Arranging the multiple sub-test cases according to the function expression order of the function node to be tested to obtain a test case group, and generating a target test case based on the test case group; A target test scenario corresponding to the operating environment of the target page is constructed, and the functional node to be tested on the target page is tested based on the target test case in the target test scenario. The method according to any one of claims 1 to 5, wherein after the testing the functional node to be tested on the target page based on the target test case, the method further comprises: Acquiring test data after testing the functional node to be tested on the target page, and generating a target test report corresponding to the functional node to be tested on the target page based on the test data; Storing the target test report in a designated storage space to obtain a backup test report, where the designated storage space also includes test reports of one or more other functional nodes to be tested except for the functional node to be tested; When the test report corresponding to any functional node to be tested is displayed and/or inquired based on the display device, the test report corresponding to any functional node to be tested is obtained from the standby test report and the test report corresponding to any functional node to be tested The test report corresponding to the test function node is output to the display device. The method according to claim 1, wherein said performing semantic analysis on said voice information to convert said voice information into text information comprises: Parse the voice information to obtain target voice information related to the functional node to be tested on the target page; The target voice information is converted into text information. The method according to claim 6, wherein the test case feature library includes a set of sub-scenario keywords; and the constructing a target test scenario corresponding to the operating environment of the target page comprises: Matching the set of sub-scene keywords with the respective test keywords to obtain multiple sub-scene keywords; A target test scenario is constructed based on the multiple sub-scene keywords and the target page. A page function testing device, characterized in that the device includes: The receiving unit is configured to receive the voice information of the user feedback page function, and perform semantic analysis on the voice information to convert the voice information into text information; The processing unit is configured to perform information processing on the text information obtained by the receiving unit to obtain multiple test keywords, and determine the function to be tested on the target page according to the operation steps described by the multiple test keywords Node, where a test keyword is used to describe an operation step of the page function that the user feedbacks; The determining unit is used to determine multiple sub-test cases matching the multiple test keywords obtained by the processing unit from the test case feature library, wherein one sub-test case is used to test an operation of the functional node to be tested step; The test unit is configured to generate a target test case according to the multiple sub-test cases determined by the determining unit, and test the functional node to be tested on the target page based on the target test case. The device according to claim 10, wherein the device further comprises: The obtaining unit is also used to obtain multiple function samples for describing page functions from the function sample library of the page function test system, and/or obtain multiple descriptions from historical test records in the page function test system Function samples of page functions, where one function sample is used to describe a page function; The generating unit is further configured to construct the test case feature database based on the multiple functional samples used to describe the page functions. The device according to claim 11, wherein the generating unit is configured to: The multiple function samples used to describe the page function are split according to the operation steps of the page function to obtain multiple sub-function samples, wherein one sub-function sample is used to describe one of the function samples corresponding to the one sub-function sample. Steps; Generate multiple sub-test cases according to the operation steps described in the multiple sub-function samples, where one sub-test case is used to test an operation step described in the sub-function sample corresponding to the one sub-test case, and the one sub-test case Corresponding to a function label, the one function label is used to mark the operation step tested by the one sub-test case; The test case feature database is constructed based on the multiple sub test cases. The device according to claim 12, wherein the generating unit is configured to: Determine the characteristic words of the operation steps corresponding to each sub-test case; Store each sub-test case and the corresponding feature word to obtain a test case feature library. The device of claim 12, wherein the testing device further comprises: The matching unit is used to match the function label of each sub-test case in the test case feature library with each of the multiple test keywords; The generating unit is configured to determine any sub-test case marked by any function tag that matches any test keyword as the sub-test case corresponding to any test keyword to determine the multiple Multiple sub-test cases corresponding to a test keyword. The method according to claim 14, wherein the generating unit is configured to: Arranging the multiple sub-test cases according to the function expression order of the function node to be tested to obtain a test case group, and generating a target test case based on the test case group; A target test scenario corresponding to the operating environment of the target page is constructed, and the functional node to be tested on the target page is tested based on the target test case in the target test scenario. The method according to any one of claims 10 to 15, wherein the test unit is further used for: Acquiring test data after testing the functional node to be tested on the target page, and generating a target test report corresponding to the functional node to be tested on the target page based on the test data; Storing the target test report in a designated storage space to obtain a backup test report, where the designated storage space also includes test reports of one or more other functional nodes to be tested except for the functional node to be tested; When the test report corresponding to any functional node to be tested is displayed and/or inquired based on the display device, the test report corresponding to any functional node to be tested is obtained from the standby test report, and the test report corresponding to any functional node to be tested is obtained. The test report corresponding to the test function node is output to the display device. The method according to claim 10, wherein the receiving unit is configured to: Parse the voice information to obtain target voice information related to the functional node to be tested on the target page; The target voice information is converted into text information. The method according to claim 15, wherein the test case feature library includes a set of sub-scenario keywords; and the generating unit is configured to: Matching the set of sub-scene keywords with the respective test keywords to obtain multiple sub-scene keywords; A target test scenario is constructed based on the multiple sub-scene keywords and the target page. A terminal device, characterized by comprising a processor and a memory, and the processor and the memory are connected to each other; The memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method according to any one of claims 1-9. A computer nonvolatile readable storage medium, wherein the computer nonvolatile readable storage medium stores a computer program, the computer program includes program instructions, and the program instructions when executed by a processor , Execute the method according to any one of claims 1-9.

Images