CN111352824B - Test method, device and computer equipment - Google Patents

Abstract

The application provides a testing method, a testing device and computer equipment. The method comprises the following steps: receiving a test request, inquiring a preset database according to test feature information carried in the test request, and acquiring test case data matched with the test feature information; generating a test case view used for representing the current test according to the acquired test case data; and calling a preset test application program, running the test case view to execute the test, acquiring an execution result, writing the acquired execution result into the test case view and storing the acquired execution result.

Description

Test method, device and computer equipment

Technical Field

The present application relates to the field of testing technology, and in particular to a testing method, apparatus and computer equipment.

Background Art

After completing the development of applications or products, it is necessary to ensure the quality of the developed services through testing. When testing the completed services, taking automated testing of various functions as an example, it is necessary to pre-write test cases based on the specific functions of the application to test and verify the functions of the application. Among them, a test case refers to a set of code segments written for a specific goal, including test input, execution conditions, and expected results. By running the test case, you can test a certain application path or verify whether the tested application meets a specific requirement.

However, in current test cases, relevant parameter data is written into the code of the test case through a development language, and each test case needs to be edited accordingly, which makes it take a long time to generate the test case and the test case generation efficiency is low. Furthermore, editors are required to master the development language, which places high demands on editors who edit test cases, and it is inconvenient to update, manage and maintain. Moreover, after the test case is tested and run in a certain device under test, the device under test that executes the test records the test case. When the test case is used again for testing the device under test, for example, according to different application situations, the test case needs to be reused. However, since the device under test has recorded and run the test case, an error message will appear, which makes it impossible to run the test case on the device under test again, so that the test case cannot be reused, and the reuse rate of the test case is low.

Summary of the invention

In a first aspect, an embodiment of the present application provides a testing method, the method comprising:

Receive a test request, and query a pre-set database based on the test feature information carried in the test request to obtain test case data that matches the test feature information;

Generate a test case view for representing the current test based on the acquired test case data;

Call a preset test application, run the test case view to execute the test, obtain the execution result, write the obtained execution result into the test case view and store it.

In combination with the first aspect, the embodiment of the present application provides a first possible implementation manner, wherein, before receiving the test request, the method further includes:

The test case data is edited by means of a spreadsheet, and the edited spreadsheet is stored in the database.

In combination with the first aspect, the embodiment of the present application provides a second possible implementation, wherein the method further includes:

According to the preset test case classification rules, the test case data in the database is classified and stored;

The test request also carries a classification identifier, and the acquiring of test case data matching the test feature information includes:

From the database, locate the classification database corresponding to the classification identifier;

The test case data matching the test feature information is searched from the classification database.

In combination with the second possible implementation of the first aspect, the embodiment of the present application provides a third possible implementation, wherein the classifying and storing the test cases in the database according to the preset test case classification rule includes:

Categorize test cases by application or product; and/or,

Categorize test cases by test module in the application or test module in the product; and/or,

Categorize test cases according to the test items in the test module; and/or,

Categorize test cases according to their attributes.

In combination with the first aspect and any one of the first to third possible implementations of the first aspect, the embodiment of the present application provides a fourth possible implementation, wherein the method further includes:

A test report is generated according to the execution result, and the test report is sent to a pre-set tester.

In combination with the first aspect and any possible implementation manner of the first to third aspects of the first aspect, the embodiment of the present application provides a fifth possible implementation manner, wherein the method further includes:

The total number of test executions and the number of successful tests for each test case are counted, and the execution success rate of the test case is calculated based on the number of successful tests and the total number of test executions.

In combination with the first aspect and any one of the first to third possible implementations of the first aspect, the embodiment of the present application provides a sixth possible implementation, wherein the method further includes:

The test case view with the execution results written in it is displayed.

In combination with the first aspect and any possible implementation manner of the first to third aspects, the embodiment of the present application provides a seventh possible implementation manner, wherein the test feature information includes: a test case name, a test case category, a test case keyword or one or any combination of test case keywords.

In a second aspect, an embodiment of the present application provides a testing device, the device comprising:

A query module is used to receive a test request, query a pre-set database according to the test feature information carried in the test request, and obtain test case data matching the test feature information;

A view generation module, used to generate a test case view for representing the current test based on the acquired test case data;

The test module is used to call a preset test application, run the test case view to execute the test, obtain the execution result, write the obtained execution result into the test case view and store it.

In a third aspect, an embodiment of the present application provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above method are executed.

Compared with the prior art, this application has the following beneficial effects:

The test method, device and computer equipment provided by the present application receive a test request, query a pre-set database according to the test feature information carried in the test request, and obtain test case data matching the test feature information; generate a test case view to characterize the current test according to the obtained test case data; call a pre-set test application, run the test case view to execute the test, obtain the execution result, write the obtained execution result into the test case view and store it. In this way, by using the database to store the test case data, there is no need to write code in the development language, the time required to generate the test case is short, and the efficiency of generating the test case is high; further, a test case view that uniquely identifies the test is generated according to the test case data extracted from the database, so that the device under test that executes the test considers it to be a new test case, thereby running and executing the test, and multiple reuse of the test cases in the database can be achieved; moreover, the execution result of the obtained test case view will not affect the original test cases in the database, and the execution result of each test case can be effectively obtained.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

FIG1 is a schematic diagram of a test method flow chart provided in an embodiment of the present application;

FIG2 is a schematic diagram of the structure of a testing device provided in an embodiment of the present application;

FIG3 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution 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 part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.

In the description of this application, it should also be noted that, unless otherwise clearly specified and limited, the terms "set", "install", "connect", and "connect" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal communication of two elements. For ordinary technicians in this field, the specific meanings of the above terms in this application can be understood according to specific circumstances.

FIG1 is a schematic diagram of a test method flow chart provided in an embodiment of the present application. As shown in FIG1 , the process includes:

Step 101, receiving a test request, querying a pre-set database according to the test feature information carried in the test request, and obtaining test case data matching the test feature information;

In this embodiment, as an optional embodiment, before receiving the test request, the method further includes:

The test case data is edited by means of a spreadsheet, and the edited spreadsheet is stored in the database.

In the present embodiment, the database is a warehouse that organizes, stores and manages data according to the data structure. Each test case corresponds to a row and column of an Excel spreadsheet in the database. The test case is characterized by the parameter data as described above. For example, the data in the first row and the first column correspond to the parameter data in a test case. As an optional embodiment, the test case exists in the format of data in the spreadsheet. Of course, in practical applications, the test case data can also be directly entered and stored in the database by manual entry, and the database stores each test case data.

Since conventional tests will reuse a large number of original test cases, and edit the original test cases according to the newly added needs of the business, and obtain test cases as a new round of tests, therefore, the code segments that run each test case, i.e., the test application, can also be reused for the most part. In this embodiment, the test case data and the test application contained in the test case are separated, and the test case data (parameter data) and the test application are extracted. It is only necessary to enter the test case data of the test case in the database, without editing the code segment for the running test of the test case data. In the subsequent test case running, the test case data in the database can be run by calling the pre-set test application edited with the code segment.

In this embodiment, as an optional embodiment, the test feature information includes but is not limited to: one or any combination of test case name, test case keyword, test case category, test case keyword, etc.

In this embodiment, by extracting keywords or test case names in the test feature information, one or more test cases matching the keywords or test case names are screened out from the database.

In this embodiment, as an optional embodiment, the method further includes:

According to the preset test case classification rules, the test case data in the database is classified and stored.

In this embodiment, if the test request also carries a classification identifier, obtaining test case data matching the test feature information includes:

From the database, locate the classification database corresponding to the classification identifier;

The test case data matching the test feature information is searched from the classification database.

In this embodiment, if the test request does not carry a classification identifier, the test feature information is matched with each test case data in the database to obtain matching test case data.

In this embodiment, by classifying and storing the test case data in the database, it is possible to facilitate the management and maintenance of the test cases. As an optional embodiment, according to the preset test case classification rules, classifying and storing the test case data in the database includes:

Categorize test cases by application or product; and/or,

Categorize test cases by test module in the application or test module in the product; and/or,

Categorize test cases according to the test items in the test module; and/or,

Categorize test cases according to their attributes.

In this embodiment, as an optional embodiment, the test case attributes include but are not limited to: data type, execution conditions (for example, the software and hardware environment of the test case execution and the logical conditions of the test case execution, etc.), data size, etc.

In this embodiment, test cases belonging to the same application or the same product can be classified into a primary classification; under the primary classification, test cases belonging to the same test module can be classified into a secondary classification; under the secondary classification, test cases belonging to the same test project can be classified into a tertiary classification; or, test cases can be classified according to test case attributes. In this way, the editing and management efficiency of a large number of test cases can be improved, and it is also convenient to query according to test feature information and quickly query the corresponding test cases for testing.

Step 102, generating a test case view for representing the current test based on the acquired test case data;

In this embodiment, a view is a virtual table in a computer database, and the content in the view can be defined by a query or customized. The format of the virtual table is the same as that of the real table, and each row and column contains data of a data identifier, wherein the data identifier can be a data name or a data sequence number, etc. Different from the real table, only the definition of the view is stored in the database. When operating the data in the view, it is necessary to operate the electronic table associated with the view in the database according to the definition of the view. That is, the view does not exist in the format of data or data strips in the database. The row and column data are associated with the electronic table referenced by the query that defines the view, and when operating the view, the associated electronic table is dynamically called.

In this embodiment, as an optional embodiment, the test case view used for the current test can be characterized by information such as a test case view identifier or a test case view version number. In this way, for each test, even if the test cases contained in the test case view are the same, different test case views correspond to different test case view identifiers or test case view version numbers. Therefore, when input to the device under test for testing, the device under test considers that the test case view is different from the recorded test case view. Therefore, running the current test case view identified by the test case view identifier or the test case view version number can effectively avoid test case errors, thereby enabling the same test case to be reused multiple times through different test case view identifiers or version numbers, and the test case reuse rate is high.

In this embodiment, the specific process of generating a view can be found in relevant technical documents, and detailed description is omitted here.

Step 103, calling a preset test application, running the test case view to execute the test, obtaining the execution result, writing the obtained execution result into the test case view and storing it.

In this embodiment, the code segments for running each test case can be reused. In this embodiment, a test application for executing the test case is pre-written, which can effectively reduce the workload of editors in editing the test case, improve editing efficiency, and reduce the technical requirements for editors.

In this embodiment, by calling a pre-set automated test application, the test application will automatically execute the data (test case) in the generated test case view, and write the execution result back to the test case view. Each test case corresponds to an execution result. For example, if the test case view contains multiple test cases, the execution result obtained by executing each test case is written to the end of the test case. In this way, by using the test case view for testing, the execution result of each execution test case can be written into the test case view through the view method, so that the test cases that have passed successfully and the test cases that have failed can be known in detail. It is possible to track the status of the test case after each execution of the test case view, so that the test case results of each test can be recorded and stored.

In this embodiment, as an optional embodiment, the execution result includes: success, failure, and if it is a failure, the method further includes: recording the reason for the test failure.

In this embodiment, after the acquired execution result is written into the test case view, the test case view is stored in the database. In this way, by storing the execution result of the test case view, it is convenient for testers to retrieve the execution result of each test case and understand the execution result of the same test case in different test environments.

In this embodiment, the database is queried based on the test feature information contained in the test request to obtain test case data that matches the test feature information, and the matching test case data is organized to generate a test case view with a unique identifier, thereby calling the corresponding test application for testing based on the test case view with the unique identifier. In this way, by storing test cases in a database, there is no need to write code using a development language, and the requirements for editors who edit test cases are low, making it convenient to update and manage test cases. At the same time, it also shortens the time required to generate test cases and increases the efficiency of generating test cases. Furthermore, when conducting a test, a query is performed according to the test request, and corresponding test case data is extracted from the database. A test case view that uniquely identifies the test is generated based on the extracted test case data. The test case view identifier generated for each test is different, so that the device under test that executes the test considers it to be a new test case, thereby running and executing the test. The execution result of the test case view obtained will not affect the original test cases in the database, and multiple reuse of test cases in the database can be achieved, effectively improving the reuse rate of test cases. In addition, by managing test case data using database technology, queries can be performed based on the test feature information carried in the test request, and test cases can be dynamically configured to meet the different functional requirements of each test environment.

In this embodiment, the execution result obtained by the test can also be notified to relevant personnel. Therefore, as an optional embodiment, the method also includes:

A test report is generated according to the execution result, and the test report is sent to a pre-set tester.

In this embodiment, as an optional embodiment, after the automated testing application completes the test case view, a test report is generated based on the execution results, and the email sending function or message sending function in the automated testing application is called to send the test report to relevant testers.

In this embodiment, since the execution result of each test case can be recorded, the execution result of each test case in different test environments can be counted. As an optional embodiment, the method further includes:

The total number of test executions and the number of successful tests for each test case are counted, and the execution success rate of the test case is calculated based on the number of successful tests and the total number of test executions.

In this embodiment, as an optional embodiment, the method further includes:

The test case view with the execution results written in it is displayed.

In this embodiment, by displaying the execution results, the execution result status and the overall test status of the test case view can be intuitively known.

In this embodiment, the test cases stored in the database may also be edited, for example, the test cases may be modified, deleted, added, etc., so that the test cases may be updated.

The following is a partial code snippet (Java language example) for storing test cases in a database in an embodiment of the present application:

The following code snippet is a code snippet (Java language) that executes the test case (tests the application and organizes the generated test case view):

FIG2 is a schematic diagram of the structure of a test device provided in an embodiment of the present application. As shown in FIG2 , the device includes:

The query module 21 is used to receive a test request, query a pre-set database according to the test feature information carried in the test request, and obtain test case data matching the test feature information;

In this embodiment, as an optional embodiment, the test feature information includes: a test case name, a test case category, a test case keyword, or one or any combination of test case keywords.

In this embodiment, by extracting keywords or test case names in the test feature information, one or more test cases matching the keywords or test case names are screened out from the database.

A view generation module 22, used to generate a test case view for representing the current test based on the acquired test case data;

In this embodiment, as an optional embodiment, the test case view used for the current test may be characterized by information such as a test case view identifier or a test case view version number.

The test module 23 is used to call a preset test application, run the test case view to execute the test, obtain the execution result, write the obtained execution result into the test case view and store it.

In this embodiment, as an optional embodiment, the execution result includes: success, failure, and if it is a failure, the method further includes: recording the reason for the test failure.

In this embodiment, as an optional embodiment, the device further includes:

The test case editing module (not shown in the figure) is used to edit the test case data in an electronic form and store the edited electronic form in the database.

In this embodiment, as another optional embodiment, the device further includes:

A test case classification module (not shown in the figure) is used to classify and store each test case in the database according to a preset test case classification rule;

The test request also carries a classification identifier, and the acquiring of test case data matching the test feature information includes:

From the database, locate the classification database corresponding to the classification identifier;

The test case data matching the test feature information is searched from the classification database.

In this embodiment, as an optional embodiment, the test case classification module is specifically used for:

Categorize test cases by application or product; and/or,

Categorize test cases by test module in the application or test module in the product; and/or,

Categorize test cases according to the test items in the test module; and/or,

Categorize test cases according to their attributes.

In this embodiment, as another optional embodiment, the device further includes:

The test report sending module is used to generate a test report according to the execution result and send the test report to a pre-set tester.

In this embodiment, as another optional embodiment, the device further includes:

The statistics module is used to count the total number of test executions of each test case and the number of successful tests of the test case, and calculate the execution success rate of the test case based on the number of successful tests and the total number of test executions.

In this embodiment, as another optional embodiment, the device further includes:

The display module is used to display the test case view with the execution results written in it.

Figure 3 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. As shown in Figure 3, a computer device provided in an embodiment of the present application is used to execute the test method in Figures 1 to 3, and the device includes a memory 1000, a processor 2000, and a computer program stored in the memory 1000 and executable on the processor 2000, wherein the processor 2000 implements the steps of the test method when executing the computer program.

Specifically, the memory 1000 and the processor 2000 can be general-purpose memories and processors, which are not specifically limited here. When the processor 2000 runs the computer program stored in the memory 2000, the test method can be executed.

Corresponding to the testing method of FIG. 1 , an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the above-mentioned testing method are executed.

Specifically, the storage medium can be a general storage medium, such as a mobile disk, a hard disk, etc. When the computer program on the storage medium is run, the above-mentioned test method can be executed.

In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to the multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and/or the flowchart, and the combination of boxes in the block diagram and/or the flowchart can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

In addition, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (10)

1. A test method, characterized in that the method comprises: Receiving a test request, querying a preset database according to the test feature information carried in the test request, and obtaining test case data matching the test feature information; According to the obtained test case data, generate a test case view to represent the current test, and use the test case view identification or test case view version number to characterize the test case view for the current test; wherein, the test case view is the a virtual table in said database, and in said database, said test case view does not exist in the format of data or data bars, the row and column data are associated with the spreadsheet referenced by the query defining said test case view, and When operating on the test case view, dynamically invoke the associated spreadsheet; Invoking a preset test application program, running the test case view to execute the test, obtaining the execution result, writing the obtained execution result into the test case view and storing it. 2. The method according to claim 1, wherein, before the receiving test request, the method further comprises: The test case data is edited in a spreadsheet, and the edited spreadsheet is stored in the database. 3. The method according to claim 1, wherein the method further comprises: Classify and store each test case data in the database according to the preset test case classification rules; The test request also carries a classification identifier, and the acquisition of test case data matching the test feature information includes: From the database, locate the classification database corresponding to the classification identifier; From the classification database, query the test case data matching the test characteristic information. 4. The method according to claim 3, wherein, according to the preset test case classification rules, classifying and storing each test case in the database comprises: Categorize test cases by application or product; and/or, Categorize test cases by test modules in the application or test modules in the product; and/or, Categorize the test cases according to the test items in the test module; and/or, Classify test cases according to test case attributes. 5. The method according to any one of claims 1 to 4, wherein the method further comprises: A test report is generated according to the execution result, and the test report is sent to a preset tester. 6. The method according to any one of claims 1 to 4, characterized in that the method further comprises: Count the total number of test executions of each test case and the number of successful tests of the test case, and calculate the execution success rate of the test case according to the number of successful tests and the total number of test executions. 7. The method according to any one of claims 1 to 4, wherein the method further comprises: The test case view with execution results will be written for display. 8. The method according to any one of claims 1 to 4, wherein the test characteristic information includes: a test case name, a test case category, a test case keyword or a test case keyword or any of them combination. 9. A testing device, characterized in that the device comprises: A query module, configured to receive a test request, query a preset database according to the test feature information carried in the test request, and obtain test case data matching the test feature information; The view generation module is used to generate a test case view for representing the current test according to the obtained test case data, and characterize the test case view for the current test through the test case view identification or the test case view version number; wherein, all The test case view is a virtual table in the database, and in the database, the test case view does not exist in the format of data or data bars, and the row and column data are referenced by the query that defines the test case view The spreadsheet is associated, and when the test case view is operated, the associated spreadsheet is dynamically invoked; The test module is used to call a preset test application program, run the test case view to execute the test, obtain the execution result, write the obtained execution result into the test case view and store it. 10. A computer device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, characterized in that the above-mentioned claims are realized when the processor executes the computer program The step of the method described in any one of 1 to 8.

Images