CN117349161A

CN117349161A - Test method and device based on test steps

Info

Publication number: CN117349161A
Application number: CN202311289268.7A
Authority: CN
Inventors: 方海波; 梁家鹏
Original assignee: Zhejiang Geely Holding Group Co Ltd; Zhejiang Zeekr Intelligent Technology Co Ltd
Current assignee: Zhejiang Geely Holding Group Co Ltd; Zhejiang Zeekr Intelligent Technology Co Ltd
Priority date: 2023-09-28
Filing date: 2023-09-28
Publication date: 2024-01-05

Abstract

The application provides a testing method and device based on testing steps, wherein the method comprises the following steps: acquiring a test case, and determining at least one test step contained in the test case; the testing step is used for completing at least one testing function; determining the dependency relationship between the at least one test step and other test steps, and merging the test steps and the test steps determined based on the dependency relationship corresponding to the test steps into a group of test steps; respectively distributing priorities to the at least one group of testing steps according to a preset first evaluation index; and sequencing the at least one group of testing steps according to the priority of the testing steps so as to test according to the sequenced testing steps.

Description

Test method and device based on test steps

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a testing method and device based on testing steps.

Background

In the software testing process, test cases are important tools for verifying whether software functions meet requirements. However, the execution sequence of the test cases is always fixed, the step execution of the test cases is also fixed, and the dependency relationship and the importance among the test steps are not considered, so that the test efficiency is low, and the test coverage rate is not comprehensive enough. The existing test case management tool also provides little intelligent sorting function, and cannot meet the requirements of testers.

Disclosure of Invention

The application provides a test method based on a test step, which comprises the following steps:

acquiring a test case, and determining at least one test step contained in the test case; the testing step is used for completing at least one testing function;

determining the dependency relationship between the at least one test step and other test steps, and merging the test steps and the test steps determined based on the dependency relationship corresponding to the test steps into a group of test steps;

respectively distributing priorities to the at least one group of testing steps according to a preset first evaluation index;

and sequencing the at least one group of testing steps according to the priority of the testing steps so as to test according to the sequenced testing steps.

Optionally, the dependency relationship includes a precondition and a post-condition, the precondition is used for determining a test step performed before the target test step, and the post-condition is used for determining a test step performed after the target test step.

Optionally, before assigning priorities to the at least one set of test steps according to a preset first evaluation index, the method further includes:

at least one set of test steps including the same test step is deleted, and one set of test steps is reserved.

Optionally, the first evaluation index includes at least one or more of: the degree of importance of the test step, the time at which the test step is performed, the verifiability of the test step.

Optionally, the method further comprises:

and if the at least one group of testing steps are wrong when being executed, the at least one group of testing steps are rearranged to be tested according to the rearranged testing steps.

Optionally, if the at least one set of test steps is faulty when executed, reordering the at least one set of test steps includes:

if the at least one group of test steps have errors in execution, executing the test steps in advance or executing the test case steps later, and reordering the at least one group of test steps.

Optionally, the method further comprises:

and determining a second evaluation index based on the execution result of the test case, and determining whether to reorder or not based on the second evaluation index.

Optionally, the second evaluation index includes at least one or more of: the execution time of the test case step, the resource utilization rate of the test equipment corresponding to the test case and the error discovery rate when the test case is executed.

The application provides a testing device based on testing steps, the device includes:

the test case acquisition unit is used for acquiring a test case and determining at least one test step contained in the test case; the testing step is used for completing at least one testing function;

the test step merging unit is used for respectively determining the dependency relationship between at least one test step and other test steps, merging the test steps and the test steps determined based on the dependency relationship corresponding to the test steps into a group of test steps;

the priority distribution unit is used for distributing priorities to the at least one group of testing steps according to a preset first evaluation index;

and the test step sequencing unit is used for sequencing the at least one group of test steps according to the priority of the test steps so as to test according to the sequenced test steps.

Optionally, the apparatus further includes:

and the test step deleting unit is used for deleting at least one group of test steps comprising the same test steps and reserving one group of test steps.

Optionally, the apparatus further includes:

and the reordering unit is used for reordering the at least one group of testing steps to perform testing according to the reordered testing steps if the at least one group of testing steps are wrong when being executed.

Optionally, the reordering unit is further configured to, if the at least one set of test steps is wrong when executed, execute the test steps in advance, or delay execution of the test case steps, and reorder the at least one set of test steps.

Optionally, the apparatus further includes:

and the sorting evaluation unit is used for determining a second evaluation index based on the execution result of the test case and determining whether to reorder based on the second evaluation index.

The application also provides electronic equipment, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;

the memory stores machine readable instructions and the processor performs the method by invoking the machine readable instructions.

The present application also provides a computer readable storage medium storing machine readable instructions that when invoked and executed by a processor implement the above-described methods.

In the solution described in the above embodiment, at least one test step included in the test case is determined, the test steps having the dependency relationship are combined, then priorities are respectively assigned to the test steps, and further, the test steps are ranked based on the priorities, by preferentially executing the steps with the higher priorities, problems can be found more quickly and the quality of software can be improved, and by combining the steps having the dependency relationship and ranking according to the priorities, each function and situation of the test case can be covered more comprehensively, thereby improving the test coverage rate.

Drawings

Fig. 1 is a flow chart of a testing method based on a testing step according to an exemplary embodiment.

Fig. 2 is a hardware configuration diagram of an electronic device where a testing apparatus based on a testing procedure is provided in an exemplary embodiment.

FIG. 3 is a block diagram of a test apparatus based on test steps, as provided by an exemplary embodiment.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.

It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. Furthermore, individual steps described in this specification, in other embodiments, may be described as being split into multiple steps; while various steps described in this specification may be combined into a single step in other embodiments. '

Referring to fig. 1, fig. 1 is a flow chart of a testing method based on testing steps according to an exemplary embodiment. The method may comprise the steps of:

step 102, acquiring a test case, and determining at least one test step contained in the test case; the testing step is used for completing at least one testing function.

In the specification, acquiring test cases refers to collecting and acquiring written test cases in a test process so as to perform execution and evaluation.

The specific manner in which the test case is obtained is not specifically limited in this specification. For example, a special test case library or test document sharing platform can be built inside the test team, so that the test team members upload written test cases to the platform for other members to review and use. For another example, a version control system, such as Git, may be used to version manage the test cases as code files, which test team members may share and update by submitting and merging code.

Determining at least one test step contained in the test case refers to analyzing the test case, identifying each test step contained in the test case, and determining the specific test function they represent.

A test case may typically consist of a plurality of test steps, each designed to perform a particular test function. In the test case, each test step will describe a specific operation that should be clearly performed, as well as a desired result.

For example, a simple test case may contain test steps that include:

step 1: the application is opened.

Step 2: and inputting a user name and a password for login.

Step 3: clicking on the "view order" button.

Step 4: confirm whether the order list is displayed or not, and contain the correct order information.

In this example, each test step has an explicit test target: the function of logging in and checking orders of the application program is tested. By performing these test steps, the tester can be assisted in discovering potential defects and errors and evaluating the quality of the system.

Step 104, determining the dependency relationship between the at least one test step and other test steps, and merging the test steps and the test steps determined based on the dependency relationship corresponding to the test steps into a group of test steps, and merging the test steps into a group of test steps.

In this specification, the dependency relationship of test steps refers to that some test steps need to depend on the result or execution state of other test steps in executing the test. In other words, if a test step depends on other steps, then these dependent steps must be performed first, ensuring that the required preconditions are met before they can be performed.

By definitely defining the dependency relationship of the test steps, the correct execution sequence and flow of the test can be ensured, thereby improving the reliability and effectiveness of the test. Test management tools or test frameworks typically support defining and managing dependencies between test steps, helping test teams to better plan and execute test plans.

In one embodiment, the dependency relationship may be divided into a pre-condition for determining a test step performed before the target test step and a post-condition for determining a test step performed after the target test step.

Preconditions refer to the fact that the execution of a certain test step depends on the results of other steps. Before this step is performed, all of its preconditioning steps must be performed and the results of these steps are ensured to be correct. For example, a test step needs to be logged in first, and then the logging operation is the test step corresponding to the precondition of the step.

For example, the test procedure corresponding to the precondition is exemplified:

step 1: the application is opened.

Step 2: and (5) performing login operation.

Step 3: after the login is successful, other operations are performed.

In this example, step 2 depends on the execution result of step 1, because the application needs to be opened first to log in.

Post conditions mean that the result of a certain test step affects the execution of other steps. After this step is performed, a subsequent step depending on the step must be performed, and the result of the step is used as an input condition. For example, one test step is to create an order, and then subsequent test steps may involve viewing the order, modifying the order, etc., all depending on the outcome of the successful creation of the order.

For example, the test procedure corresponding to the post condition is exemplified:

step 1: an order is created.

Step 2: the order list is reviewed.

Step 3: the order is modified.

In this example, both step 2 and step 3 rely on the results of step 1 execution because an order needs to be created before it can be viewed and modified.

In this specification, the dependency relationship between each test step and other test steps may be determined, and the test steps determined based on the dependency relationship corresponding to the test steps may be combined into one test step.

For example, the test cases may include test steps that include:

step 1: the application is opened.

Step 2: and inputting a user name and a password for login.

Step 3: clicking on the "view order" button.

Step 5: a new order is created.

And 6, modifying the content in the new order.

In this example, the test steps determined based on the post conditions of step 1 may include step 2, so step 1, step 2 may be combined into a set of test steps. The testing step determined based on the preconditions of step 2 includes step 1. Step 1, step 2, can thus be combined into a set of steps. Similarly, the testing step determined based on the preconditions of step 5 includes step 1, step 2. The test step determined based on the post conditions of step 5 includes step 6. Steps 1,2,5,6 can thus be combined into a set of steps.

In one embodiment, at least one set of test steps comprising the same test step may also be deleted before assigning the priority.

For example, the test cases may include test steps that include:

step 1: the application is opened.

Step 2: and inputting a user name and a password for login.

Step 3: clicking on the "view order" button.

Step 5: a new order is created.

And 6, modifying the content in the new order.

In this example, the test steps determined based on the post conditions of step 1 may include step 2, so step 1, step 2 may be combined into a set of test steps. The testing step determined based on the preconditions of step 2 includes step 1. Step 1, step 2, can thus be combined into a set of steps. The test steps in the two sets of test steps are step 1 and step 2, so that one of the two sets of test steps can be deleted.

And 106, respectively distributing priorities to the at least one group of testing steps according to a preset first evaluation index.

In the present specification, priorities are assigned to at least one set of test steps according to a preset first evaluation index. The first evaluation index is not particularly limited in this specification. For example, priorities may be assigned based on the business value of the test steps, or the degree to which the test steps affect system stability, security, and reliability, etc.

In practical application, the time of the test case can be executed according to the importance degree of the test case steps, and the verifiability of the test case can be used for distributing priorities to at least one group of test steps.

In actual allocation, the priority of the test steps may be indicated using numbers, letters or custom indicia, e.g., high, medium, low priority using 1,2, 3, or priority ranking using A, B, C. The testing steps can be flexibly assigned with proper priorities according to specific projects and requirements so as to ensure orderly performance of testing work.

And step 108, sequencing the at least one testing step according to the priority of the testing step so as to test according to the sequenced testing step.

In this specification, at least one set of test steps may be ordered according to the priority of each set of test steps, and tested according to the ordered test steps.

For example, the test cases associated with user registration may include test steps that include:

step 1, filling in a user name

Step 2, filling in the password

Step 3, mailbox verification

Step 4, selecting a security problem

Step 5, setting a safety question answer

Step 6, submitting registration information

Step 7, checking page display after successful registration

According to the test steps determined by the dependency relationship, the step 1 and the step 2 can be combined into a group of test steps, and the step 4 and the step 5 can be combined into a group of test steps.

Thus, the test steps included in the combined test case may include:

step 1, filling in a user name and a password

Step 2, mailbox verification

Step 3, selecting a safety question and setting a safety question answer

Step 4, submitting registration information

Step 5, checking page display after successful registration

The 5 steps may be respectively assigned priorities according to the importance degree of the test step.

For example, the priority of step 2 is a, and mailbox verification is a key step for ensuring the validity and accuracy of the user registration information in practical application, and the registration information without mailbox verification may not be normally used.

Step 4 has a priority of B, and submitting registration information in the actual application is the main step of ensuring that the user data is properly saved and processed, and if this step has a problem, it may result in that the user cannot register successfully.

The priority of step 1 is C, and filling in user name and password is an essential step in the registration process in practical application, but the service value is relatively low compared with mailbox verification and submitting registration information

The priority of the step 3 is D, and the selection and setting of the security problem in the actual application is an optional step in the registration process, so that the service value is relatively low, and the key functions of the registration cannot be directly influenced.

The priority of step 5 is E, and in practical application, this step is mainly used for user experience and confirmation of registration results, and has relatively small influence on critical functions.

Thus, testing may be performed in accordance with ordered testing steps, such as:

step 1, mailbox verification

Step 2, submitting registration information

Step 3, filling in the user name and the password

Step 4, selecting a safety question and setting a safety question answer

Step 5, checking page display after successful registration

According to this ordering, the tests may be performed in a top-to-bottom order, ensuring that the higher priority test steps are performed first, followed by the lower priority steps. This ensures that critical functions are first verified during the test and that other functions are tested step by step.

In one embodiment, if the at least one set of test steps is incorrect when executed, the at least one set of test steps is reordered to perform the test according to the reordered test steps.

In practical applications, if an error occurs during execution of the test case, specific details and reasons of the error can be confirmed, and further determination is made as to which test step has a problem and the root cause of the problem.

The priority of the test steps is re-evaluated based on the nature and importance of the error. If the error severely affects the critical function or user experience, the relevant steps may need to be promoted to a higher priority.

The order of the test steps is adjusted according to the re-evaluated priorities. Ensuring that those steps critical to core functionality and system stability, as well as steps that have previously found errors, are tested for priority.

In one embodiment, the testing step with the error may be performed in advance, or the testing case step may be performed later, and the at least one set of testing steps may be reordered.

By performing critical test steps in advance, possible problems and errors can be found earlier. Therefore, the problems can be solved as soon as possible, the influence of subsequent testing work is reduced, and the overall testing efficiency is improved.

While placing important test steps in front can reduce the risk of the project. By verifying the core function and the key flow as early as possible, the stability and reliability of the system in the subsequent development and testing stages can be ensured, and the probability of serious problems is reduced.

While in most cases the early test step is a better choice, in certain specific cases the late test step may also bring about some beneficial effects:

if many reconfiguration and redesign situations occur in the development, this may result in all of the previous testing effort being ineffective. At this time, delaying the testing step can avoid wasting testing resources and time. After the function is stable, the test is performed, so that the efficiency and the accuracy of the test can be improved.

If the quality of the data acquired is low in the earlier test steps, it may lead to inaccuracy in the subsequent analysis and decision making. The postponed testing step can obtain more accurate data, thereby better supporting subsequent product improvement.

In one embodiment, a second evaluation index is determined based on the execution result of the test case, and whether to reorder is determined based on the second evaluation index.

The specific content of the second evaluation index is not specifically limited in this specification. For example, the execution time of the test case step, the resource utilization rate of the test equipment corresponding to the test case, and the error discovery rate when the test case is executed may be set.

Based on the results of the test cases, a second evaluation index may be determined. Further, whether the sorting needs to be performed again can be determined based on whether the second evaluation index reaches a preset condition, so that the test efficiency and the test coverage rate can be improved.

The present specification also provides embodiments of the test apparatus based on the test steps, corresponding to the embodiments of the test method based on the test steps described above.

Referring to fig. 2, fig. 2 is a hardware configuration diagram of an electronic device where a testing device based on a testing procedure is shown in an exemplary embodiment. At the hardware level, the device includes a processor 202, an internal bus 204, a network interface 206, a memory 208, and a non-volatile storage 210, although other hardware required for the service is possible. One or more embodiments of the present description may be implemented in a software-based manner, such as by the processor 202 reading a corresponding computer program from the non-volatile storage 210 into the memory 208 and then running. Of course, in addition to software implementation, one or more embodiments of the present disclosure do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.

Referring to fig. 3, fig. 3 is a block diagram of a testing apparatus based on testing steps according to an exemplary embodiment. The testing device based on the testing step can be applied to the electronic equipment shown in fig. 2 to realize the technical scheme of the specification. The testing device based on the testing step may include:

the test case obtaining unit 302 is configured to obtain a test case, and determine at least one test step included in the test case; the testing step is used for completing at least one testing function;

a test step merging unit 304, configured to determine dependency relationships between the at least one test step and other test steps, and merge the test steps and the test steps determined based on the dependency relationships corresponding to the test steps into a set of test steps;

a priority allocation unit 306, configured to allocate priorities to the at least one group of test steps according to a preset first evaluation index;

a test step sorting unit 308, configured to sort the at least one group of test steps according to the priorities of the test steps, so as to perform a test according to the sorted test steps.

In this embodiment, the dependency relationship includes a precondition for determining a test step performed before the target test step and a post-condition for determining a test step performed after the target test step.

In this embodiment, the apparatus further includes:

In this embodiment, the first evaluation index includes at least one or more of the following: the degree of importance of the test step, the time at which the test step is performed, the verifiability of the test step.

In this embodiment, the apparatus further includes:

In this embodiment, the reordering unit is further configured to, if the at least one set of test steps is wrong when executed, execute the test steps in advance, or execute the test case step later, and reorder the at least one set of test steps.

In this embodiment, the apparatus further includes:

In this embodiment, the second evaluation index includes at least one or more of the following: the execution time of the test case step, the resource utilization rate of the test equipment corresponding to the test case and the error discovery rate when the test case is executed.

The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.

For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are illustrative only, in that the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purposes of the present description. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

User information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in this specification are both information and data authorized by the user or sufficiently authorized by the parties, and the collection, use and processing of relevant data requires compliance with relevant laws and regulations and standards of the relevant country and region, and is provided with corresponding operation portals for the user to choose authorization or denial.

The present specification also provides an embodiment of a computer-readable storage medium. The computer readable storage medium stores machine readable instructions that, when invoked and executed by a processor, implement the test procedure based test method provided by any of the embodiments of the present specification.

The computer readable storage medium provided by the embodiments of the present specification may include, but is not limited to, any type of disk including floppy disks, hard disks, optical disks, CD-ROMs, and magneto-optical disks, ROMs (Read-Only memories), RAMs (Random Access Memory, random access memories), EPROMs (Erasable Programmable Read-Only memories), EEPROMs (Electrically Erasable Programmable Read-Only memories), flash memories, magnetic cards, or optical fiber cards. That is, a readable storage medium includes a readable medium that can store or transfer information.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.

In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, etc., such as Read Only Memory (ROM) or flash memory (flashRAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, read only compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by the computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

The terminology used in the one or more embodiments of the specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the one or more embodiments of the specification. As used in this specification, one or more embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.

The foregoing description of the preferred embodiment(s) is (are) merely intended to illustrate the embodiment(s) of the present invention, and it is not intended to limit the embodiment(s) of the present invention to the particular embodiment(s) described.

Claims

1. A test method based on a test step, the method comprising:

2. The method of claim 1, the dependency comprising a pre-condition for determining a test step performed prior to a target test step and a post-condition for determining a test step performed after the target test step.

3. The method of claim 1, further comprising, prior to assigning priorities to the at least one set of test steps, respectively, according to a preset first evaluation index:

4. The method of claim 1, the first evaluation index comprising at least one or more of: the degree of importance of the test step, the time at which the test step is performed, the verifiability of the test step.

5. The method of claim 1, the method further comprising:

6. The method of claim 5, the reordering the at least one set of test steps if the at least one set of test steps is in error when executed, comprising:

7. The method of claim 1, the method further comprising:

8. The method of claim 7, the second evaluation index comprising at least one or more of: the execution time of the test case step, the resource utilization rate of the test equipment corresponding to the test case and the error discovery rate when the test case is executed.

9. A test apparatus based on a test step, the apparatus comprising:

10. An electronic device comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;

the memory stores machine readable instructions, and the processor performs the method of any of claims 1-8 by invoking the machine readable instructions.

11. A computer readable storage medium storing machine readable instructions which, when invoked and executed by a processor, implement the method of any one of claims 1-8.