CN112667512A - Data drive test method, device, equipment and computer readable storage medium - Google Patents
Data drive test method, device, equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN112667512A CN112667512A CN202011622433.2A CN202011622433A CN112667512A CN 112667512 A CN112667512 A CN 112667512A CN 202011622433 A CN202011622433 A CN 202011622433A CN 112667512 A CN112667512 A CN 112667512A
- Authority
- CN
- China
- Prior art keywords
- test
- function
- data
- acquiring
- case
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The embodiment of the application provides a data driving test method, a device, equipment and a computer readable storage medium; the data driving test method in the embodiment of the application comprises the following steps: receiving a data driving test instruction, and acquiring a tester identifier and a test scene identifier associated with the data driving test instruction; acquiring a test function corresponding to the test scene identification, acquiring test parameters corresponding to the tester identification, inputting the test parameters to the test function, acquiring a test case and executing the test case; when the test case is captured and the abnormality is thrown out, the abnormality is declared, the current test step in the test case is exited, and the next test step of the test case is entered; when the test case is executed, outputting a data driving test result; according to the embodiment of the application, the test case is configured according to the test scene identification and the tester identification, so that the data driving comprehensive test is realized, and the data driving abnormity test efficiency is improved.
Description
Technical Field
The embodiment of the application relates to the technical field of software automation test, in particular to a data driving test method, a device, equipment and a computer readable storage medium.
Background
With the rapid computer technology, various kinds of application software are more and more, and after the application software is developed, the application software needs to be tested in a series to be finally released to be on line.
The application software test comprises the following steps: data driving test (also called black box test or function test), performance test, stability test, etc.; the data driving test is a basic part of the application software test, and if the data driving is in a problem, the whole application software is likely to be unusable; the existing data driving test scheme is suitable for simple scenes (such as numerical operation and simple logic judgment), the most complicated part in the data driving test is the test on abnormal conditions, and the test on the abnormal conditions of the current application software is the targeted test on the possible 'unexpected abnormal conditions' by testers. That is to say, in the existing automatic test of data-driven test, a tester writes a test case according to a test task, such a test case is fixed in a data-driven test mode, and only a simple scene can be tested, and the test abnormal condition corresponding to the test case is incomplete, and the test case cannot cover all scene test schemes of the abnormal condition in the test process.
Disclosure of Invention
The embodiment of the application provides a data driving test method, a data driving test device, data driving test equipment and a computer readable storage medium, and aims to solve the technical problems that the existing automatic test of the data driving test cannot be comprehensively tested according to the requirements of testers, and the efficiency of the current abnormal data driving test of an application program is low.
In one aspect, an embodiment of the present application provides a data driving test method, where the data driving test method includes the following steps:
receiving a data driving test instruction, and acquiring a tester identifier and a test scene identifier associated with the data driving test instruction;
acquiring a test function corresponding to the test scene identification, acquiring test parameters corresponding to the tester identification, inputting the test parameters to the test function, acquiring a test case and executing the test case;
when the test case is captured and the abnormality is thrown out, the abnormality is declared, the current test step in the test case is exited, and the next test step of the test case is entered;
and outputting a data driving test result when the test case is executed.
In some embodiments of the present application, the first and second,
before the receiving of the data driving test instruction and the obtaining of the tester identifier and the test scene identifier associated with the data driving test instruction, the method comprises the following steps:
receiving a role setting request, acquiring a target role associated with the role setting request and role permission of the target role, configuring test parameters of the target role according to the role permission of the target role, and establishing a mapping relation between the target role and the test parameters;
when detecting that a background interface of an application program is updated, acquiring an updated target interface identifier, determining an application function of an interface corresponding to the target interface identifier, acquiring a target test function corresponding to the application function, and establishing a mapping relation between the target test function and a test scene identifier to which the application function belongs.
In some embodiments of the present application, the obtaining a test function corresponding to the test scenario identifier, obtaining a test parameter corresponding to the tester identifier, inputting the test parameter to the test function, obtaining a test case, and executing the test case includes:
acquiring a target function contained in the test scene identification, inquiring a preset function table, and acquiring a test function corresponding to the target function;
acquiring a target role corresponding to the tester identification, inquiring a preset parameter table, and acquiring test parameters corresponding to the target role and attributes of the test parameters;
and inputting the test parameters to the test function according to the respective attributes of the test parameters to obtain a test case and execute the test case.
In some embodiments of the present application, after obtaining the test function corresponding to the test scenario identifier, obtaining the test parameter corresponding to the tester identifier, inputting the test parameter to the test function, obtaining a test case, and executing the test case, the method includes:
judging whether the role corresponding to the tester identification has the execution authority of the target test step to be executed in the test case;
if the role corresponding to the tester identification does not have the execution authority of the target test step, outputting abnormal prompt information;
and if the role corresponding to the tester identification has the execution authority of the target test step, executing the test function contained in the target test step, and obtaining and outputting the execution result of the target test step.
In some embodiments of the present application, when capturing that the test case throws an exception, asserting the exception, exiting a current testing step in the test case, and entering a next testing step of the test case, includes:
when the test case is captured and the abnormality is thrown out, inquiring a preset abnormal data table, and judging whether an error code corresponding to the abnormality exists in the preset abnormal data table or not;
if the error code corresponding to the abnormality does not exist in the preset abnormal data table, outputting prompt information to prompt a user to configure the error code corresponding to the abnormality and the assertion corresponding to the error code;
and if the error code corresponding to the abnormality exists in the preset abnormal data table, obtaining the assertion corresponding to the test code, exiting the current test step of the test case, and entering the next test step of the test case.
In some embodiments of the present application, before receiving a data-driven test instruction and acquiring a tester identifier and a test scenario identifier associated with the data-driven test instruction, the method includes:
when detecting that the application program is updated, acquiring a newly added target function in the application program;
obtaining a test function corresponding to the target function, and analyzing the test function to generate a test parameter corresponding to the test function;
and associating the test function with the test parameters to obtain a test case corresponding to the target function.
In some embodiments of the present application, before receiving a data-driven test instruction and acquiring a tester identifier and a test scenario identifier associated with the data-driven test instruction, the method includes:
extracting test parameters from the test cases through a predefined test frame, and dividing the historical test cases into test parameters and test functions;
and storing the test parameters to a preset parameter table according to respective attributes, and storing the test functions to a preset function table according to respective types of the test functions.
On the other hand, an embodiment of the present application further provides a data driving test apparatus, where the data driving test apparatus includes:
the identification acquisition module is used for receiving a data driving test instruction and acquiring a tester identification and a test scene identification which are associated with the data driving test instruction;
the acquisition execution module is used for acquiring a test function corresponding to the test scene identifier, acquiring test parameters corresponding to the tester identifier, inputting the test parameters to the test function, acquiring a test case and executing the test case;
the abnormal assertion module is used for asserting the abnormality when capturing the abnormality thrown out by the test case, exiting the current test step in the test case and entering the next test step of the test case;
and the result output module is used for outputting a data driving test result when the test case is executed.
On the other hand, an embodiment of the present application further provides a data driving test device, where the data driving test device includes:
one or more processors;
a memory; and
one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the data driven testing method.
On the other hand, the embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is loaded by a processor to execute the steps in the data-driven testing method.
According to the technical scheme of the embodiment of the application, a data driving test instruction is received, and a tester identifier and a test scene identifier associated with the data driving test instruction are obtained; acquiring a test function corresponding to the test scene identification, acquiring test parameters corresponding to the tester identification, inputting the test parameters to the test function, acquiring a test case and executing the test case; when the test case is captured and the abnormality is thrown out, the abnormality is declared, the current test step in the test case is exited, and the next test step of the test case is entered; when the test case is executed, outputting a data driving test result; according to the method and the device, the test function is obtained according to the test scene identification, the test parameters are obtained according to the tester identification, the personalized configuration of the test case is achieved, the data driving test is more targeted, meanwhile, the abnormity is captured in the test case execution, the test case is not directly jumped out, the abnormity is predicated and then the next step is jumped to, the comprehensive test of the data driving is achieved, and the efficiency of testing the application program data driving abnormity is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic view of a scenario of a data-driven test provided in an embodiment of the present application;
FIG. 2 is a schematic flow chart diagram illustrating a first embodiment of a data-driven testing method provided in an embodiment of the present application;
FIG. 3 is a flowchart illustrating an embodiment of authority determination in the data driving test method provided in the embodiment of the present application;
FIG. 4 is a schematic flow chart diagram illustrating one embodiment of an exception assertion in the data-driven test method provided in the embodiments of the present application;
FIG. 5 is a flowchart illustrating an embodiment of creating a test case in the data-driven testing method provided in the embodiment of the present application;
FIG. 6 is a flowchart illustrating an embodiment of saving test functions and test parameters in the data-driven test method provided in the embodiment of the present application;
FIG. 7 is a schematic structural diagram of an embodiment of a data driver test apparatus provided in the embodiment of the present application;
fig. 8 is a schematic structural diagram of an embodiment of the data driving test device provided in the embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any inventive step, are within the scope of the present invention.
In the description of the present invention, it is to be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc. indicate orientations or positional relationships based on those shown in the drawings, and are only for convenience of description and simplicity of description, but do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be considered as limiting the present invention. Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, features defined as "first", "second", may explicitly or implicitly include one or more of the described features. In the description of the present invention, "a plurality" means two or more unless specifically defined otherwise.
In the embodiments of the present application, the word "exemplary" is used to mean "serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. The following description is presented to enable any person skilled in the art to make and use the invention. In the following description, details are set forth for the purpose of explanation. It will be apparent to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and processes are not shown in detail to avoid obscuring the description of the invention with unnecessary detail. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed in the embodiments herein.
Embodiments of the present application provide a data driving test method, apparatus, device, and computer readable storage medium, which are described in detail below.
The data driving test method in the embodiment of the invention is applied to a data driving test device, the data driving test device is arranged on data driving test equipment, one or more processors, a memory and one or more application programs are arranged in the data driving test equipment, wherein the one or more application programs are stored in the memory and are configured to be executed by the processor to realize the data driving test method; the data driving test device may be a terminal, for example, a mobile phone or a tablet computer, and the data driving test device may also be a server or a service cluster formed by multiple servers.
As shown in fig. 1, fig. 1 is a schematic view of a data driving test scenario according to an embodiment of the present disclosure, where the data driving test scenario includes a data driving test device 100 (a data driving test apparatus is integrated in the data driving test device 100), and the data driving test device 100 runs a computer readable storage medium corresponding to a data driving test to perform a data driving test.
It should be understood that the data driving test device in the scenario of the data driving test shown in fig. 1, or the device included in the data driving test device, does not limit the embodiment of the present invention, that is, the number of devices and the type of devices included in the scenario of the data driving test, or the number of devices and the type of devices included in each device do not affect the overall implementation of the technical solution in the embodiment of the present invention, and can be calculated as equivalent replacements or derivatives of the technical solution claimed in the embodiment of the present invention.
The data driving test equipment 100 in the embodiment of the invention is mainly used for:
receiving a data driving test instruction, and acquiring a tester identifier and a test scene identifier associated with the data driving test instruction;
acquiring a test function corresponding to the test scene identification, acquiring test parameters corresponding to the tester identification, inputting the test parameters to the test function, acquiring a test case and executing the test case;
when the test case is captured and the abnormality is thrown out, the abnormality is declared, the current test step in the test case is exited, and the next test step of the test case is entered;
and outputting a data driving test result when the test case is executed.
In this embodiment of the present invention, the data driving test device 100 may be an independent data driving test device, or may be a data driving test device network or a data driving test device cluster formed by data driving test devices, for example, the data driving test device 100 described in this embodiment of the present invention includes, but is not limited to, a computer, a network host, a single network data driving test device, a plurality of network data driving test device sets, or a cloud data driving test device formed by a plurality of data driving test devices. Among them, the Cloud data driving test device is constituted by a large number of computers based on Cloud Computing (Cloud Computing) or a network data driving test device.
Those skilled in the art can understand that the application environment shown in fig. 1 is only one application scenario related to the embodiment of the present application, and does not constitute a limitation on the application scenario of the embodiment of the present application, and that other application environments may further include more or less data-driven test devices than those shown in fig. 1, or a network connection relationship of the data-driven test devices, for example, only 1 data-driven test device is shown in fig. 1, and it can be understood that the scenario of the data-driven test may further include one or more other data-driven test devices, which is not limited herein; the data drive test equipment 100 may further include a memory therein.
In addition, in the scenario of the data driving test in the embodiment of the present application, the data driving test equipment 100 may be provided with a display device, or the data driving test equipment 100 is not provided with a display device in communication connection with the external display device 200, and the display device 200 is configured to output a result of executing the data driving test method in the data driving test equipment. The data driving test device 100 may access a background database 300 (the background database may be in a local memory of the data driving test device, and may also be set in the cloud), and information related to the data driving test is stored in the background database 300.
It should be noted that the scenario diagram of the data-driven test shown in fig. 1 is only an example, and the scenario of the data-driven test described in the embodiment of the present invention is for more clearly illustrating the technical solution of the embodiment of the present invention, and does not constitute a limitation on the technical solution provided by the embodiment of the present invention.
Based on the scenario of the data driving test, an embodiment of the data driving test method is provided.
As shown in fig. 2, fig. 2 is a schematic flow chart of a first embodiment of a data driving test method in the embodiment of the present application, where the data driving test method in the embodiment includes steps 201-204:
and 201, receiving a data driving test instruction, and acquiring a tester identifier and a test scene identifier associated with the data driving test instruction.
The data driving test method in this embodiment is applied to the data driving test device, and the type of the data driving test device is not particularly limited, for example, the data driving test device may be a terminal or a server, and the terminal is taken as an example in this embodiment for description.
It can be understood that the computer program corresponding to the data driving test method operates independently, and the computer program corresponding to the data driving test method can be directly installed on the terminal to implement the data driving automatic test.
In this embodiment, the terminal receives the data driving test instruction, where a triggering manner of the data driving test instruction is not specifically limited, that is, the data driving test instruction may be actively triggered by a user, for example, the user inputs: the xxx application program clicks a test key to actively trigger the data-driven automatic test; in addition, the data-driven test instruction may also be automatically triggered by the terminal, for example, the triggering condition for setting the data-driven test in the terminal is preset as follows: and carrying out data driving test on the newly installed application program, detecting the change condition of the application program in real time by the terminal, and automatically triggering a data driving test instruction by the terminal when detecting the newly installed application program.
The terminal receives the data driving test instruction, and acquires a tester identifier and a test scene identifier associated with the data driving test instruction, wherein the tester identifier is identifier information for uniquely identifying the data driving tester, and can be the name and the job number of the tester; the test scenario identifier refers to identification information of a scenario to be tested of the application program, and the test scenario identifier may be a page identifier of the application program, for example, the test scenario identifier of a commodity ordering scenario in the xxx application program is an xxx ordering page.
It should be added that, before the data-driven testing method of this embodiment is executed, the terminal pre-establishes a mapping relationship between the test scenario identifier and the test function, and the terminal pre-establishes a mapping relationship between the tester identifier and the test parameter, so that the terminal can respectively select the test function and the test parameter according to the test scenario identifier and the tester identifier, and combine to form a test case for performing the data-driven testing, specifically, the step of establishing the mapping relationship includes:
a1, receiving a role setting request, acquiring a target role associated with the role setting request and a role authority of the target role, configuring test parameters of the target role according to the role authority of the target role, and establishing a mapping relation between the target role and the test parameters;
step a2, when detecting background interface update of an application program, acquiring an updated target interface identifier, determining an application function of an interface corresponding to the target interface identifier, acquiring a target test function corresponding to the application function, and establishing a mapping relationship between the target test function and a test scenario identifier to which the application function belongs.
The method comprises the steps that a terminal receives a role setting request, the terminal obtains a target role (the target role can be flexibly set according to data drive test requirements, for example, the target role is set to be a super manager, a resource library owner, a resource library manager, a resource library member or other users) related to the role setting request and the role authority of the target role, the terminal configures test parameters of the target role according to the role authority of the target role, the terminal establishes a mapping relation between the target role and the test parameters, after the terminal obtains the identifier of the tester, the terminal can determine the role corresponding to the identifier of the tester according to the identifier of the tester, and the terminal obtains the test parameters corresponding to the role to carry out a targeted test.
The method comprises the steps that a terminal monitors the change condition of a target application program to be tested in real time, when the terminal detects that a background interface of the application program is updated, the terminal obtains an updated target interface identification, the terminal determines the application function of the interface corresponding to the target interface identification, a function table is preset in the terminal, the preset function table contains different types of functions, the terminal obtains a target test function corresponding to the application function, and the terminal establishes a mapping relation between the target test function and a test scene identification to which the application function belongs.
202, obtaining a test function corresponding to the test scene identification, obtaining a test parameter corresponding to the tester identification, inputting the test parameter to the test function, obtaining a test case, and executing the test case.
In this embodiment, the terminal obtains a test function corresponding to the test scene identifier, obtains a test parameter corresponding to the tester identifier, and inputs the test parameter to the test function, so as to obtain a test case and execute the test case, specifically, the method includes:
1. acquiring a target function contained in the test scene identification, inquiring a preset function table, and acquiring a test function corresponding to the target function;
2. acquiring a target role corresponding to the tester identification, inquiring a preset parameter table, and acquiring test parameters corresponding to the target role and attributes of the test parameters;
3. and inputting the test parameters to the test function according to the respective attributes of the test parameters to obtain a test case and execute the test case.
The terminal acquires the test functions contained in the test scene identification, inquires the preset function table and acquires the test functions corresponding to the target function mapping relation; the terminal is provided with a preset parameter table, the preset parameter table comprises different types of test parameters, the preset parameter table can be an excel table, a header of the excel table comprises key field information, and the excel table comprises test parameters corresponding to the key field information; the terminal determines a target role corresponding to the identifier of the tester, queries a preset parameter table, and acquires test parameters corresponding to the target role and attributes of the test parameters (the attributes of the test parameters refer to types of the test parameters, positions of the test parameters, incidence relations among the test parameters, and the like); and the terminal inputs the test parameters into the test function according to the respective attributes of the test parameters to obtain a test case and execute the test case.
203, when capturing the exception thrown out by the test case, asserting the exception, exiting the current test step in the test case, and entering the next test step of the test case.
The terminal detects the execution condition of the test case in real time, when the test case throws the abnormity, the terminal captures the abnormity, the terminal asserts the abnormity, namely, the terminal prestores assertions corresponding to different abnormity, and after the terminal captures the abnormity, the terminal exits the current test step in the test case and enters the next test step of the test case. For example, the terminal performs a process-related test in application software, if a previous operation has an influence on a subsequent operation, the terminal directly asserts an error code according to the error code corresponding to the abnormality after detecting that the operation throws the abnormality, then exits from the current test, and continues the subsequent test; if the former operation has no influence on the later operation, the terminal continues to execute the later operation in the test case, the complete flow in the application program is operation step 1, operation step 2, operation step 3 and operation step 4, each operation step depends on the former operation step, when the expected or unexpected abnormality occurs in operation step 3, the operation is failed, the function is directly return, and the whole flow is ended.
In the embodiment, the data driving test is a permission-related test, each operation may have permission or no permission, and the steps are independent of each other, so that after each operation is completed, the operation is directly compared with an expected operation, and an error code is asserted when an exception is captured. If the authority of the user A to the operation step 1, the operation step 2, the operation step 3 and the operation step 4 is { true, true, false, true }, the operation step 3 is executed to throw out the exception, the exception judgment is directly carried out, and then the operation step 4 is continuously executed to verify that the authority is normal.
And 204, outputting a data driving test result when the test case is executed.
The terminal detects the execution condition of the test case in real time, when the execution of the test case is finished, the terminal obtains the execution result of the test step in the test case, the terminal collects the execution result and outputs a data driving test result.
According to the technical scheme of the embodiment of the application, a data driving test instruction is received, and a tester identifier and a test scene identifier associated with the data driving test instruction are obtained; acquiring a test function corresponding to the test scene identification, acquiring test parameters corresponding to the tester identification, inputting the test parameters to the test function, acquiring a test case and executing the test case; when the test case is captured and the abnormality is thrown out, the abnormality is declared, the current test step in the test case is exited, and the next test step of the test case is entered; when the test case is executed, outputting a data driving test result; according to the method and the device, the test function is obtained according to the test scene identification, the test parameters are obtained according to the tester identification, the personalized configuration of the test case is achieved, the data driving test is more targeted, meanwhile, the abnormity is captured in the test case execution, the test case is not directly jumped out, the abnormity is predicated and then the next step is jumped to, the comprehensive test of the data driving is achieved, and the efficiency of testing the application program data driving abnormity is improved.
That is, in the embodiment of the present application, an open-source automated testing framework (for example, TestNG) is used for testing, Excel maintains case data, and a packaging function reads data therein, and transfers the data to a testing function for testing, specifically, a document is used to maintain a total test case in a manner of adding an automated testing item (or adding a testing code to testing data) to a test case document, a similar scenario uses the same flow, and key parameters of each case are extracted to make a table; the document facilitates verification and review. When the coding is automatically tested, the key parameters of the extracted case are taken as parameters and transmitted to a test function; one Sheet in the test data Excel corresponds to one large test scene, and the fields in the Sheet correspond to the parameters one by one.
As shown in fig. 3, fig. 3 is a schematic flow chart of an embodiment of authority determination in the data driving test method provided in the embodiment of the present application.
In some embodiments of the present application, when the data-driven test method executes a test case, the method includes the following steps 301-:
301, judging whether the role corresponding to the tester identifier has the execution authority of the target test step to be executed in the test case.
The terminal acquires a role corresponding to the calibration of a tester, and judges whether the role corresponding to the identifier of the tester has the execution authority of a target test step to be executed in a test case, namely, the terminal judges whether the test authority set of the role corresponding to the identifier of the tester contains the execution authority of the test step in the test case, if the test authority set of the role corresponding to the identifier of the tester contains the execution authority of the test step in the test case, the role corresponding to the identifier of the tester has the execution authority of the target test step; and if the test permission set of the role corresponding to the tester identifier does not contain the execution permission of the test step in the test case, the role corresponding to the tester identifier does not have the execution permission of the target test step.
302, if the role corresponding to the tester identifier does not have the execution authority of the target testing step, outputting an abnormal prompt message.
And if the corresponding role of the tester identification does not have the execution authority of the target test step, the terminal outputs abnormal prompt information so that the tester knows the execution information of the test case.
303, if the role corresponding to the tester identifier has the execution authority of the target testing step, executing the testing function included in the target testing step, and obtaining and outputting the execution result of the target testing step.
If the corresponding role of the tester identifier has the execution permission of the target test step, the terminal executes the test function contained in the target test step to obtain the execution result of the target test step and output the execution result.
For example, the test task corresponding to the test scenario identifier is relatively complex, so that a single case often contains more operations, the terminal combines the test cases similar to the flow together, and performs position numbering on each operation, for example, a Pair < > form is used for parameter transmission in normal and abnormal scenarios, the normal operation is only required to be transmitted 0 directly, the abnormal scenario asserts the position and error code where an abnormality is expected to occur, for example, Pair <2,10201> indicates that an error is expected to be reported in the 2 nd operation, and the error code is 10201; in the permission test scene, the parameter is transmitted in an array form, for example, { true, true, false, true } indicates that the user has an operation permission at 1/2/4, and has no operation permission at 3, and when the user has no permission, the user can normally capture an exception and an error code is correct.
Referring to fig. 4, fig. 4 is a schematic flow chart illustrating an embodiment of an exception assertion in the data-driven test method provided in the embodiment of the present application.
In some embodiments of the present application, specifically, the processing step when the terminal captures the test exception during the data driving test is described, including steps 401 and 403:
401, when the test case is captured and an exception is thrown out, querying a preset exception data table, and judging whether an error code corresponding to the exception exists in the preset exception data table.
An abnormal data table is preset in the terminal, wherein the preset abnormal data table is an abnormal data table formed by expressing historical abnormality by error codes by a tester and associating the error codes with assertions by the terminal; when capturing the abnormity, the terminal inquires a preset abnormal data table and judges whether an error code corresponding to the abnormity exists in the preset abnormal data table.
402, if the error code corresponding to the exception does not exist in the preset exception data table, outputting a prompt message to prompt a user to configure the error code corresponding to the exception and to prompt the user to assert the error code.
If the error code corresponding to the abnormality does not exist in the preset abnormal data table, the terminal outputs prompt information to prompt a user to configure the error code corresponding to the abnormality and the assertion corresponding to the error code. In this embodiment, when there is no error code corresponding to the anomaly, the terminal outputs the prompt information, so that the user can flexibly configure the error code corresponding to the anomaly and the assertion corresponding to the error code, and the data driving test is more convenient and flexible.
403, if the preset abnormal data table has an error code corresponding to the abnormality, obtaining an assertion corresponding to the test code, exiting the current test step of the test case, and entering the next test step of the test case.
If the preset abnormal data table has error codes corresponding to the abnormality, the assertion corresponding to the test codes is obtained, furthermore, the terminal obtains a test step executed currently in the test case, the terminal judges whether the current test step and the subsequent test step in the test case have a correlation, if the current test step and the subsequent test step in the test case have a correlation, the test is quitted, and if the current test step and the subsequent test step in the test case have no correlation, the terminal quits the current test step of the test case and enters the next test step of the test case. In the embodiment, the terminal can assert the exception in the test case, so that a user can know the execution condition of the test case in real time.
Referring to fig. 5, fig. 5 is a schematic flowchart of an embodiment of creating a test case in the data-driven testing method provided in the embodiment of the present application.
In some embodiments of the present application, after the data driving test in this embodiment, a test case is pre-constructed in the terminal, so that when the terminal performs the data driving test in the later stage, the terminal decomposes the pre-constructed test case to configure and form a new test case meeting different test scenarios, where the step of pre-constructing the test case in the terminal is specifically described in this embodiment, and includes step 501-:
501, when detecting the update of the application program, acquiring a newly added target function in the application program.
502, obtaining a test function corresponding to the target function, and analyzing the test function to generate a test parameter corresponding to the test function.
When the terminal detects that the application program is updated, the terminal acquires a target function newly added in the application program, in this embodiment, the terminal defines different test function sets in advance, the terminal acquires a test function corresponding to the target function, the terminal analyzes the test function to acquire dependent variables in the test function, dependent variable setting rules corresponding to dependent variables are obtained, the terminal generates test parameters corresponding to the test function according to the dependent variable setting rules, for example, the dependent variable is a telephone number, and the terminal generates the telephone number as the test parameter according to the rule of the telephone number.
503, associating the test function with the test parameter to obtain a test case corresponding to the target function.
The terminal associates the test function with the test parameter to obtain a test case corresponding to the target function, in this embodiment, the terminal combines the test function with the test function to generate a corresponding test parameter, and the terminal associates the test parameter with the test function to generate a test case; the terminal can analyze the generated test case so as to perform subsequent data-driven automatic test.
Referring to fig. 6, fig. 6 is a schematic flowchart of an embodiment of saving a test function and a test parameter in the data-driven test method provided in the embodiment of the present application.
In some embodiments of the present application, it is specifically described that the terminal analyzes a pre-constructed test case, and the terminal decomposes the test case to form a test function and a test parameter, so that the terminal can recombine the test parameter and the test function at a later stage to form a new test case to perform data-driven automated testing, where the implementation is a step of decomposing and storing the test case by the terminal, and includes 601-:
601, extracting test parameters from the test cases through a predefined test framework, and dividing the historical test cases into test parameters and test functions.
The terminal is internally predefined with a test frame, different test code automatic operation programs are arranged in the test frame, the terminal extracts test parameters from test cases through the predefined test frame, and the terminal divides historical test cases into test parameters and test functions.
And 602, storing the test parameters to a preset parameter table according to respective attributes, and storing the test functions to a preset function table according to respective types of the test functions.
The terminal stores the test parameters to a preset parameter table according to respective attributes, and the terminal stores the test functions to a preset function table according to respective types of the test functions. In this embodiment, the terminal may store the test parameters and the test functions to the preset parameter table and the preset function table, respectively, so as to facilitate later data-driven automated testing.
For convenience of understanding, a specific scenario of data-driven testing is provided in the application, and includes:
1) the complete test case is first collated. For example, the block of resource pool permissions sets the table horizontal axis as the resource pool operation (including checking resource pool/updating resource pool/adding member/updating member/removing member/deleting resource pool), and vertical axis as the role (including super manager/resource pool owner/resource pool manager/resource pool member/other user), and then marks whether all the roles have corresponding permissions according to the requirement document.
2) This rights table data is then collated into Excel.
3) The program reads the data in Excel line by line and passes each set of data to the test function to verify that the associated permissions are in anticipation.
4) If the role is newly added, deleted or modified in the system requirement, corresponding lines are directly added, deleted or modified in the test case and the Excel, the test code does not need to be changed, and the data in the Excel is automatically read when the test program runs. For example, the authority of a module of the application software to be tested mainly includes creating/viewing/modifying/uploading/downloading/deleting operations and the like. Because the creation is the basis of the following operation, the use case is independently specified to carry out permission data drive test on the creation function; other operations share one data driving test case, and when each pair of users executes the case, the appointed user creates the case first and then executes the following operation. All the rights of a user in a module are used as a group of test data; normally finishing the operation when the authority exists, throwing the exception when the authority does not exist, and setting the state code as a specified value; and after the error information is acquired, the assertion comparison is carried out on each captured abnormal state code, and the current test is continued.
5) If the background interface is changed, only the corresponding test function needs to be modified independently, and the data in the Excel does not need to be changed.
As shown in fig. 7, fig. 7 is a schematic structural diagram of an embodiment of a data driving test apparatus.
In order to better implement the data driving test method in the embodiment of the present application, on the basis of the data driving test method, an embodiment of the present application further provides a data driving test apparatus, where the data driving test apparatus includes:
the identification acquisition module 701 is used for receiving a data driving test instruction and acquiring a tester identification and a test scene identification which are associated with the data driving test instruction;
an obtaining and executing module 702, configured to obtain a test function corresponding to the test scene identifier, obtain a test parameter corresponding to the tester identifier, input the test parameter to the test function, obtain a test case, and execute the test case;
the exception assertion module 703 is configured to assert the exception when the exception thrown out by the test case is captured, exit the current test step in the test case, and enter the next test step of the test case;
a result output module 704, configured to output a data-driven test result when the test case is executed.
In some embodiments of the present application, the data driving test apparatus includes:
receiving a role setting request, acquiring a target role associated with the role setting request and role permission of the target role, configuring test parameters of the target role according to the role permission of the target role, and establishing a mapping relation between the target role and the test parameters;
when detecting that a background interface of an application program is updated, acquiring an updated target interface identifier, determining an application function of an interface corresponding to the target interface identifier, acquiring a target test function corresponding to the application function, and establishing a mapping relation between the target test function and a test scene identifier to which the application function belongs.
In some embodiments of the present application, the obtaining execution module 702 includes:
acquiring a target function contained in the test scene identification, inquiring a preset function table, and acquiring a test function corresponding to the target function;
acquiring a target role corresponding to the tester identification, inquiring a preset parameter table, and acquiring test parameters corresponding to the target role and attributes of the test parameters;
and inputting the test parameters to the test function according to the respective attributes of the test parameters to obtain a test case and execute the test case.
In some embodiments of the present application, the data driving test apparatus includes:
judging whether the role corresponding to the tester identification has the execution authority of the target test step to be executed in the test case;
if the role corresponding to the tester identification does not have the execution authority of the target test step, outputting abnormal prompt information;
and if the role corresponding to the tester identification has the execution authority of the target test step, executing the test function contained in the target test step, and obtaining and outputting the execution result of the target test step.
In some embodiments of the present application, the exception assertion module 703 includes:
when the test case is captured and the abnormality is thrown out, inquiring a preset abnormal data table, and judging whether an error code corresponding to the abnormality exists in the preset abnormal data table or not;
if the error code corresponding to the abnormality does not exist in the preset abnormal data table, outputting prompt information to prompt a user to configure the error code corresponding to the abnormality and the assertion corresponding to the error code;
and if the error code corresponding to the abnormality exists in the preset abnormal data table, obtaining the assertion corresponding to the test code, exiting the current test step of the test case, and entering the next test step of the test case.
In some embodiments of the present application, the data driving test apparatus includes:
when detecting that the application program is updated, acquiring a newly added target function in the application program;
obtaining a test function corresponding to the target function, and analyzing the test function to generate a test parameter corresponding to the test function;
and associating the test function with the test parameters to obtain a test case corresponding to the target function.
In some embodiments of the present application, the data driving test apparatus includes:
extracting test parameters from the test cases through a predefined test frame, and dividing the historical test cases into test parameters and test functions;
and storing the test parameters to a preset parameter table according to respective attributes, and storing the test functions to a preset function table according to respective types of the test functions.
The data driving test device receives a data driving test instruction, and obtains a tester identifier and a test scene identifier associated with the data driving test instruction; acquiring a test function corresponding to the test scene identification, acquiring test parameters corresponding to the tester identification, inputting the test parameters to the test function, acquiring a test case and executing the test case; when the test case is captured and the abnormality is thrown out, the abnormality is declared, the current test step in the test case is exited, and the next test step of the test case is entered; when the test case is executed, outputting a data driving test result; according to the method and the device, the test function is obtained according to the test scene identification, the test parameters are obtained according to the tester identification, the personalized configuration of the test case is achieved, the data driving test is more targeted, meanwhile, the abnormity is captured in the test case execution, the test case is not directly jumped out, the abnormity is predicated and then the next step is jumped to, the comprehensive test of the data driving is achieved, and the efficiency of testing the application program data driving abnormity is improved.
An embodiment of the present invention further provides a data driving test device, as shown in fig. 8, fig. 8 is a schematic structural diagram of an embodiment of the data driving test device provided in the embodiment of the present application.
The data driving test device integrates any one of the data driving test devices provided by the embodiment of the invention, and comprises:
one or more processors;
a memory; and
one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor for performing the steps of the data driven test method described in any of the above embodiments of the data driven test method.
Specifically, the method comprises the following steps: the data drive test equipment may include components such as a processor 801 of one or more processing cores, memory 802 of one or more computer-readable storage media, a power supply 803, and an input unit 804. Those skilled in the art will appreciate that the data driven test device architecture shown in FIG. 8 does not constitute a limitation of the data driven test device and may include more or fewer components than shown, or some components in combination, or a different arrangement of components. Wherein:
the processor 801 is a control center of the data driving test apparatus, connects various parts of the entire data driving test apparatus using various interfaces and lines, and performs various functions of the data driving test apparatus and processes data by running or executing software programs and/or modules stored in the memory 802 and calling data stored in the memory 802, thereby performing overall monitoring of the data driving test apparatus. Alternatively, processor 801 may include one or more processing cores; preferably, the processor 801 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 801.
The memory 802 may be used to store software programs and modules, and the processor 801 executes various functional applications and data processing by operating the software programs and modules stored in the memory 802. The memory 802 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to use of the data drive test apparatus, and the like. Further, the memory 802 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 802 may also include a memory controller to provide the processor 801 access to the memory 802.
The data drive test equipment further comprises a power supply 803 for supplying power to each component, and preferably, the power supply 803 can be logically connected with the processor 801 through a power management system, so that functions of charging, discharging, power consumption management and the like can be managed through the power management system. The power supply 803 may also include one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and any like components.
The data driven test device may also include an input unit 804, the input unit 804 being operable to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
Although not shown, the data driving test apparatus may further include a display unit and the like, which are not described in detail herein. Specifically, in this embodiment, the processor 801 in the data driving test equipment loads the executable file corresponding to the process of one or more application programs into the memory 802 according to the following instructions, and the processor 801 runs the application programs stored in the memory 802, so as to implement various functions as follows:
receiving a data driving test instruction, and acquiring a tester identifier and a test scene identifier associated with the data driving test instruction;
acquiring a test function corresponding to the test scene identification, acquiring test parameters corresponding to the tester identification, inputting the test parameters to the test function, acquiring a test case and executing the test case;
when the test case is captured and the abnormality is thrown out, the abnormality is declared, the current test step in the test case is exited, and the next test step of the test case is entered;
and outputting a data driving test result when the test case is executed.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, an embodiment of the present invention provides a computer-readable storage medium, which may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like. The computer program is loaded by a processor to execute the steps of any one of the data driving test methods provided by the embodiments of the present invention. For example, the computer program may be loaded by a processor to perform the steps of:
receiving a data driving test instruction, and acquiring a tester identifier and a test scene identifier associated with the data driving test instruction;
acquiring a test function corresponding to the test scene identification, acquiring test parameters corresponding to the tester identification, inputting the test parameters to the test function, acquiring a test case and executing the test case;
when the test case is captured and the abnormality is thrown out, the abnormality is declared, the current test step in the test case is exited, and the next test step of the test case is entered;
and outputting a data driving test result when the test case is executed.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed descriptions of other embodiments, and are not described herein again.
In a specific implementation, each unit or structure may be implemented as an independent entity, or may be combined arbitrarily to be implemented as one or several entities, and the specific implementation of each unit or structure may refer to the foregoing method embodiment, which is not described herein again.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
The data driving test method provided by the embodiment of the present application is described in detail above, and the principle and the implementation of the present invention are explained in this document by applying a specific example, and the description of the embodiment is only used to help understanding the method of the present invention and the core idea thereof; meanwhile, for those skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (10)
1. A data driving test method, comprising:
receiving a data driving test instruction, and acquiring a tester identifier and a test scene identifier associated with the data driving test instruction;
acquiring a test function corresponding to the test scene identification, acquiring test parameters corresponding to the tester identification, inputting the test parameters to the test function, acquiring a test case and executing the test case;
when the test case is captured and the abnormality is thrown out, the abnormality is declared, the current test step in the test case is exited, and the next test step of the test case is entered;
and outputting a data driving test result when the test case is executed.
2. The data-driven test method according to claim 1, wherein before receiving the data-driven test instruction and acquiring the tester identifier and the test scenario identifier associated with the data-driven test instruction, the method includes:
receiving a role setting request, acquiring a target role associated with the role setting request and role permission of the target role, configuring test parameters of the target role according to the role permission of the target role, and establishing a mapping relation between the target role and the test parameters;
when detecting that a background interface of an application program is updated, acquiring an updated target interface identifier, determining an application function of an interface corresponding to the target interface identifier, acquiring a target test function corresponding to the application function, and establishing a mapping relation between the target test function and a test scene identifier to which the application function belongs.
3. The data-driven testing method of claim 1, wherein the obtaining of the testing function corresponding to the testing scene identifier, obtaining of the testing parameters corresponding to the tester identifier, inputting of the testing parameters to the testing function, obtaining and executing of the testing case comprises:
acquiring a target function contained in the test scene identification, inquiring a preset function table, and acquiring a test function corresponding to the target function;
acquiring a target role corresponding to the tester identification, inquiring a preset parameter table, and acquiring test parameters corresponding to the target role and attributes of the test parameters;
and inputting the test parameters to the test function according to the respective attributes of the test parameters to obtain a test case and execute the test case.
4. The data-driven testing method of claim 1, wherein after the obtaining of the testing function corresponding to the testing scene identifier, the obtaining of the testing parameters corresponding to the tester identifier, the inputting of the testing parameters to the testing function, the obtaining of the testing case, and the execution of the testing case, the method comprises:
judging whether the role corresponding to the tester identification has the execution authority of the target test step to be executed in the test case;
if the role corresponding to the tester identification does not have the execution authority of the target test step, outputting abnormal prompt information;
and if the role corresponding to the tester identification has the execution authority of the target test step, executing the test function contained in the target test step, and obtaining and outputting the execution result of the target test step.
5. The data-driven test method of claim 1, wherein when capturing the exception thrown out by the test case, asserting the exception, exiting the current test step in the test case, and entering the next test step of the test case, comprises:
when the test case is captured and the abnormality is thrown out, inquiring a preset abnormal data table, and judging whether an error code corresponding to the abnormality exists in the preset abnormal data table or not;
if the error code corresponding to the abnormality does not exist in the preset abnormal data table, outputting prompt information to prompt a user to configure the error code corresponding to the abnormality and the assertion corresponding to the error code;
and if the error code corresponding to the abnormality exists in the preset abnormal data table, obtaining the assertion corresponding to the test code, exiting the current test step of the test case, and entering the next test step of the test case.
6. The data-driven test method according to any one of claims 1 to 5, wherein before receiving the data-driven test instruction and acquiring the tester identifier and the test scenario identifier associated with the data-driven test instruction, the method includes:
when detecting that the application program is updated, acquiring a newly added target function in the application program;
obtaining a test function corresponding to the target function, and analyzing the test function to generate a test parameter corresponding to the test function;
and associating the test function with the test parameters to obtain a test case corresponding to the target function.
7. The data-driven test method according to claim 6, wherein before receiving the data-driven test instruction and acquiring the tester identifier and the test scenario identifier associated with the data-driven test instruction, the method comprises:
extracting test parameters from the test cases through a predefined test frame, and dividing the historical test cases into test parameters and test functions;
and storing the test parameters to a preset parameter table according to respective attributes, and storing the test functions to a preset function table according to respective types of the test functions.
8. A data drive test apparatus, characterized in that the data drive test apparatus comprises:
the identification acquisition module is used for receiving a data driving test instruction and acquiring a tester identification and a test scene identification which are associated with the data driving test instruction;
the acquisition execution module is used for acquiring a test function corresponding to the test scene identifier, acquiring test parameters corresponding to the tester identifier, inputting the test parameters to the test function, acquiring a test case and executing the test case;
the abnormal assertion module is used for asserting the abnormality when capturing the abnormality thrown out by the test case, exiting the current test step in the test case and entering the next test step of the test case;
and the result output module is used for outputting a data driving test result when the test case is executed.
9. A data driving test apparatus, characterized in that the data driving test apparatus comprises:
one or more processors;
a memory; and
one or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the processor to implement the data driven testing method of any one of claims 1 to 7.
10. A computer-readable storage medium, having stored thereon a computer program which is loaded by a processor to perform the steps of the data-driven testing method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011622433.2A CN112667512A (en) | 2020-12-30 | 2020-12-30 | Data drive test method, device, equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011622433.2A CN112667512A (en) | 2020-12-30 | 2020-12-30 | Data drive test method, device, equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112667512A true CN112667512A (en) | 2021-04-16 |
Family
ID=75412190
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011622433.2A Pending CN112667512A (en) | 2020-12-30 | 2020-12-30 | Data drive test method, device, equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112667512A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116775500A (en) * | 2023-08-21 | 2023-09-19 | 深圳市广和通无线通信软件有限公司 | Autonomous test method for industrial Internet platform driving software |
-
2020
- 2020-12-30 CN CN202011622433.2A patent/CN112667512A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116775500A (en) * | 2023-08-21 | 2023-09-19 | 深圳市广和通无线通信软件有限公司 | Autonomous test method for industrial Internet platform driving software |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9569325B2 (en) | Method and system for automated test and result comparison | |
| CN111835584A (en) | Inspection method and device for products of Internet of things, computer equipment and storage medium | |
| CN110784374A (en) | Method, device, equipment and system for monitoring operation state of service system | |
| CN112506755B (en) | Log acquisition method, device, computer equipment and storage medium | |
| CN102415052B (en) | For the system and method for the configuration of management equipment | |
| CN112667512A (en) | Data drive test method, device, equipment and computer readable storage medium | |
| CN115190044B (en) | Device connection state checking method, device and storage medium | |
| CN115643163A (en) | Fault equipment positioning method, device, equipment and storage medium | |
| CN112181695A (en) | Abnormal application processing method, device, server and storage medium | |
| US20090083747A1 (en) | Method for managing application programs by utilizing redundancy and load balance | |
| CN115643158A (en) | Equipment cluster repairing method, device, equipment and storage medium | |
| CN115080412A (en) | Software update quality evaluation method, device, equipment and computer storage medium | |
| CN115080507A (en) | Vehicle fault snapshot data storage method, system, equipment and storage medium | |
| CN112035366B (en) | Test case generation method, device and equipment | |
| CN113900872A (en) | Hardware fault detection system, method and medium | |
| CN111459804A (en) | Node optimization method, device and storage medium in system test | |
| CN111159988A (en) | Model processing method and device, computer equipment and storage medium | |
| CN113971191A (en) | Data import method and device and computer readable storage medium | |
| CN113570333B (en) | Process design method suitable for integration | |
| CN111932706B (en) | Informationized inspection method and device, storage medium and electronic equipment | |
| CN117155772B (en) | Alarm information enrichment method, device, equipment and storage medium | |
| CN112035174B (en) | Method, apparatus and computer storage medium for running web service | |
| CN115658467A (en) | Service data testing method, device, equipment and storage medium | |
| CN115599671A (en) | Application program debugging method, device, equipment and storage medium | |
| CN115543422A (en) | Method, device, server and storage medium for automatic deployment of front-end codes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |