A software automated testing method and device

Abstract

The present invention proposes a software automation testing method and device, and relates to the field of software testing. The method comprises: creating a test case directory structure isomorphic to the operation page of the app to be tested; editing the test case file in the test case directory structure so that the name of the test case file is the same as the name of the folder in which it is located; setting the name of the test case file corresponding to the child page as a mark; setting a case containing a specific mark on the child page for returning to the parent page; extracting the selected test case through a script to generate a final test case library; executing the script to read the test case library and execute it. The execution order can be arbitrarily formulated, and even the program can be allowed to randomly arrange the case for execution. Redundant operations are greatly reduced, and some repeated page jumps are automatically realized by the program. The execution of repeated steps is greatly reduced, thereby reducing the execution time. Close to the user's usage scenario. The case can be selected for execution at will.

Description

Technical Field

[0001] The present invention relates to the field of software testing, and in particular to a method and device for automated software testing. Background Art

[0002] Automated testing is a process that converts human-driven testing behavior into machine execution. Usually, after the test case is designed and reviewed, the tester will perform the test step by step according to the procedures described in the test case to compare the actual results with the expected results.

[0003] The disadvantages of the prior art are as follows:

[0004] Without human intervention, the execution order cannot be arbitrarily specified. For example, there are three test cases A, B, and C. A requires login, B requires logout, and C requires login. There is no way to execute the test cases in the order of A, B, and C. You can only execute A and C in one group and B in another group.

[0005] A lot of redundant and repetitive code is written manually. For example, each use case needs to be written based on the home page, which requires that each use case must first be written with code to jump all the way to the current page before it is actually executed, and after execution, the code is used to ensure that the page returns all the way to the home page.

[0006] Executing repeated steps takes a long time to run; as mentioned in 2), redundant code steps lead to redundant operation steps at runtime, which takes up more execution time.

[0007] It is not close to the user usage scenario; or the scenario mentioned in 2), the user will not return to the homepage after completing some operations, and then jump back to the corresponding page step by step.

[0008] Unable to select a specific use case for execution. Use cases are usually divided into multiple levels. For example, our company has p0, p1, and p2. P0 represents basic use cases, p1 represents common use cases, and p2 represents remote functions. Sometimes, in order to reduce the running time, you may want to execute only p0-level use cases. Due to the problem mentioned in 1), it is impossible to automatically select such use cases for direct execution. Summary of the invention

[0009] In order to overcome the above problems or at least partially solve the above problems, an embodiment of the present invention provides a software automation testing method and device.

[0010] The embodiment of the present invention is achieved as follows:

[0011] In a first aspect, the present invention provides a software automation testing method, comprising:

[0012] Create a test case directory structure that is the same as the operation page of the app to be tested;

[0013] Edit the test case file in the test case directory structure so that the name of the test case file is the same as the name of the folder in which it is located;

[0014] In the test case where the parent page jumps to the sub-page, the name of the test case file corresponding to the sub-page is set as a flag;

[0015] In the child page, set up a specific flag case to return to the parent page;

[0016] After each test case is completed, stay on the corresponding page;

[0017] Extract the selected test cases through scripts to generate the final test case library;

[0018] The execution script reads the test case library and executes it.

[0019] Based on the first aspect, in some embodiments of the present invention, the step of creating a test case directory structure isomorphic to the operation page of the app to be tested includes:

[0020] In the test case directory structure, if the bottom tab has no parent-child page relationship, a main page is virtualized as the virtual parent page of the tab.

[0021] Based on the first aspect, in some embodiments of the present invention, the above-mentioned step of setting a specific flag use case in the child page for returning to the parent page further includes:

[0022] Each use case file has only one specific marker use case, which is used to return to the parent page from the current page.

[0023] Based on the first aspect, in some embodiments of the present invention, in response to a specific marking case of a virtual parent page and a corresponding child page being selected, the parent page of the virtual parent page is returned.

[0024] Based on the first aspect, in some embodiments of the present invention, after each of the above test cases is tested, before the step of staying on the corresponding page, the step further includes:

[0025] Make the page where the App to be tested is located correspond to the App page corresponding to the file where the test case is located.

[0026] Based on the first aspect, in some embodiments of the present invention, the step of extracting the selected test cases through the script to generate a final test case library includes:

[0027] During the selection process, for test cases belonging to different pages, the test cases corresponding to the page jumps are automatically selected according to the path information.

[0028] Based on the first aspect, in some embodiments of the present invention, the step of extracting includes:

[0029] When executing the two use case files A and B in sequence;

[0030] If A and B are in a parent-child relationship, first extract the test cases in file A and put them in the test library, then extract the test cases marked with B from the test file A and put them in the test library, and finally extract the test cases in file B and put them in the test library;

[0031] If A and B are grandparents and grandchildren, and the execution order is A, C, D, B, then first extract the test cases in file A and put them in the test library, then extract the test cases marked with C from file A and put them in the test library, then extract the test cases marked with D from file C and put them in the test library, then extract the test cases marked with B from file D and put them in the test library, and finally extract the test cases in file B and put them in the test library;

[0032] If A and B are in a child-parent relationship, first extract the test cases in file A and put them in the test library, then extract the test cases with specific mark cases from test file A and put them in the test library, and finally extract the test cases in file B and put them in the test library;

[0033] If A and B are grandchild and ancestor, and the execution order is A, C, D, B, then first extract the test cases in file A and put them in the test library, then extract the test cases with specific mark cases from test file A and put them in the test library, then extract the test cases with specific mark cases from test file C and put them in the test library, and finally extract the test cases in file B and put them in the test library;

[0034] When A and B have no father-son, son-father, grandfather-grandson, or grandson-grandfather relationship, according to the test case directory structure mentioned in S1, A and B must have a common ancestor. The processing process at this time is to first find their common ancestor D, then follow the grandson-ancestor process in the order of A and D, put the selected test cases into the test library, and then follow the grandfather-grandson process in the order of D and B, and put the selected test cases into the test library.

[0035] Based on the first aspect, in some embodiments of the present invention, the step of extracting the selected test cases through the script to generate a final test case library includes:

[0036] During the selection process, if you specify to select all test cases contained in a test file, test cases with specific marks will be excluded.

[0037] Based on the first aspect, in some embodiments of the present invention, in the test case in which the parent page jumps to the sub-page, the step of setting the name of the test case file corresponding to the sub-page as a mark includes:

[0038] The marker for jumping to a subpage is marked in the step of the use case, not in the use case itself.

[0039] In a second aspect, an embodiment of the present invention provides a software automation testing device, characterized in that it includes:

[0040] Create module: Create a test case directory structure that is isomorphic to the operation page of the app to be tested;

[0041] Edit module: edit the test case file in the test case directory structure so that the name of the test case file is the same as the name of the folder where it is located;

[0042] Set the flag module: In the test case where the parent page jumps to the sub-page, set the name of the test case file corresponding to the sub-page as a flag;

[0043] Set specific flag module: set a specific flag use case on the child page to return to the parent page;

[0044] Stay module: After each test case is tested, stay on the corresponding page;

[0045] Selection module: extracts the selected test cases through scripts to generate the final test case library;

[0046] Execution module: The execution script reads the test case library and executes it.

[0047] Compared with the prior art, the embodiments of the present invention have at least the following advantages or beneficial effects:

[0048] The present invention provides a software automation testing method and device, which are as follows: creating a test case directory structure isomorphic to the operation page of an app to be tested; editing a test case file in the test case directory structure so that the name of the test case file is the same as the name of the folder in which it is located; in a test case in which a parent page jumps to a child page, setting the name of a test case file corresponding to a child page as a flag; setting a case containing a specific flag on the child page for returning to the parent page; after each test case is tested, staying on the corresponding page; extracting the selected test case through a script to generate a final test case library; executing the script to read the test case library and execute it. The execution order can be arbitrarily formulated, and even the program can be allowed to randomly arrange the test cases for execution. Redundant operations are greatly reduced, and some repeated page jumps are automatically realized by the program. The execution of repeated steps is greatly reduced, thereby reducing the execution time. It is close to the user's usage scenario. The test case can be selected for execution at will. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention 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 creative work.

[0050] Figure 1 A flowchart of an embodiment of a software automation testing method of the present invention;

[0051] Figure 2 The present invention is a structural block diagram of an embodiment of a software automation testing device.

[0052] Icons: 1. Create module; 2. Edit module; 3. Set mark module; 4. Set specific mark module; 5. Stay module; 6. Extract module; 7. Execute module. DETAILED DESCRIPTION

[0053] To make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be described clearly and completely in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.

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

[0055] 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.

[0056] In the embodiments provided in the present application, it should be understood that the disclosed methods and devices can also be implemented in other ways. The system embodiments are merely schematic, for example, the block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems and computer program products according to the multiple embodiments of the present application. In this regard, each box in the block diagram can represent a module, a program segment or a part of the code, and a part of the module, program segment or code contains one or more executable instructions for implementing the specified logical functions. 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 flow chart, and the combination of boxes in the block diagram and / or flow chart 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.

[0057] 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.

[0058] If the function is implemented in the form of a software function module and sold or used as an independent product, it 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 and includes several instructions to enable a computer device, which can be a personal computer, a server, or a network device, etc., to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0059] Example

[0060] Please refer to Figure 1 In a first aspect, the present invention provides a software automation testing method, comprising:

[0061] S1: Create a test case directory structure that is isomorphic to the operation page of the app to be tested;

[0062] In this step, after obtaining the directory structure of the operation page of the app to be tested, a test case directory structure is created that is isomorphic to the operation page of the app to be tested. This is equivalent to a one-to-one correspondence between the directory structure of the operation page of the app to be tested and the directory structure of the created test case, a one-to-one correspondence between parent pages and parent pages, and a one-to-one correspondence between child pages, to facilitate subsequent testing.

[0063] S2: Edit the test case file in the test case directory structure so that the name of the test case file is the same as the name of the folder where it is located;

[0064] In this step, the test case file is located in a folder. After obtaining the folder name, edit the name of the test case file so that the name of the edited test case file is the same as the name of the folder in which it is located, which is convenient for subsequent testing.

[0065] S3: In the test case where the parent page jumps to the sub-page, the name of the test case file corresponding to the sub-page is set as a mark;

[0066] In this step, in the test case of the parent page jumping to the sub-level page, the name of the test case file corresponding to the child page is set as a mark for jumping to the child page.

[0067] S4: Include a specific flag use case in the child page to return to the parent page;

[0068] In this step, a specific flag case can be "goBack". The purpose of this setting is to: greatly reduce redundant operations, and some repeated page jumps are automatically implemented by the program. It greatly reduces the execution of repeated steps, thereby reducing execution time

[0069] S5: After each test case is tested, stay on the corresponding page;

[0070] S6: Extract the selected test cases through the script to generate the final test case library;

[0071] In this step, the test cases that need to be tested are selected, and those that are not selected are not tested, which saves testing time and allows you to select test cases to execute at will.

[0072] S7: Execute the script to read the test case library and execute it.

[0073] Based on the first aspect, in some embodiments of the present invention, the step of creating a test case directory structure isomorphic to the operation page of the app to be tested includes:

[0074] In the test case directory structure, if the bottom tab has no parent-child page relationship, a main page is virtualized as the virtual parent page of the tab.

[0075] In this step, there may be special cases in the test case directory structure. For example, after logging in to WeChat, the tabbar at the bottom contains four tabs, namely "WeChat", "Address Book", "Discover", and "Me". These four tabs do not have a parent-child page relationship. In order to ensure logical consistency of logical processing, a virtual main page is created as the parent page of these four tabs.

[0076] Based on the first aspect, in some embodiments of the present invention, the above-mentioned step of setting a specific flag use case in the child page for returning to the parent page further includes:

[0077] Each use case file has only one specific marker use case, which is used to return to the parent page from the current page.

[0078] In this step, each use case file has only one specific marking use case, which is used to return to the parent page from the current page. This greatly reduces redundant operations, and some repeated page jumps are automatically implemented by the program.

[0079] Based on the first aspect, in some embodiments of the present invention, in response to a specific marking case of a virtual parent page and a corresponding child page being selected, the parent page of the virtual parent page is returned.

[0080] In this step, by selecting a specific flag, you can return to the parent page of the virtual parent page. For the virtual parent page, the implementation of the goBack use case of the virtual parent page and its child pages must return to the parent page of the virtual parent page, that is, return to the login page (go through the logout process), which greatly reduces the execution of repeated steps and thus reduces the execution time.

[0081] Based on the first aspect, in some embodiments of the present invention, after each of the above test cases is tested, before the step of staying on the corresponding page, the step further includes:

[0082] Make the page where the App to be tested is located correspond to the App page corresponding to the file where the test case is located.

[0083] In this step, the page where the App to be tested is located corresponds to the App page corresponding to the file where the test case is located, ensuring the consistency of logical processing.

[0084] Based on the first aspect, in some embodiments of the present invention, the step of extracting the selected test cases through the script to generate a final test case library includes:

[0085] During the selection process, for test cases belonging to different pages, the test cases corresponding to the page jumps are automatically selected according to the path information.

[0086] In this step, for test cases belonging to different pages, the test cases corresponding to the page jumps are automatically selected according to the path information, which greatly reduces the execution of repeated steps and thus reduces the execution time.

[0087] Based on the first aspect, in some embodiments of the present invention, the step of extracting includes:

[0088] When executing the two use case files A and B in sequence;

[0089] If A and B are in a parent-child relationship, first extract the test cases in file A and put them in the test library, then extract the test cases marked with B from the test file A and put them in the test library, and finally extract the test cases in file B and put them in the test library;

[0090] If A and B are grandparents and grandchildren, and the execution order is A, C, D, B, then first extract the test cases in file A and put them in the test library, then extract the test cases marked with C from file A and put them in the test library, then extract the test cases marked with D from file C and put them in the test library, then extract the test cases marked with B from file D and put them in the test library, and finally extract the test cases in file B and put them in the test library;

[0091] If A and B are in a child-parent relationship, first extract the test cases in file A and put them in the test library, then extract the test cases with specific mark cases from test file A and put them in the test library, and finally extract the test cases in file B and put them in the test library;

[0092] If A and B are grandchild and ancestor, and the execution order is A, C, D, B, then first extract the test cases in file A and put them in the test library, then extract the test cases with specific mark cases from test file A and put them in the test library, then extract the test cases with specific mark cases from test file C and put them in the test library, and finally extract the test cases in file B and put them in the test library;

[0093] When A and B have no father-son, son-father, grandfather-grandson, or grandson-grandfather relationship, according to the test case directory structure mentioned in S1, A and B must have a common ancestor. The processing process at this time is to first find their common ancestor D, then follow the grandson-ancestor process in the order of A and D, put the selected test cases into the test library, and then follow the grandfather-grandson process in the order of D and B, and put the selected test cases into the test library.

[0094] In the above embodiments, the execution order can be set at will, and the program can even be allowed to randomly arrange the use cases for execution, which is close to the user's usage scenario.

[0095] Based on the first aspect, in some embodiments of the present invention, the step of extracting the selected test cases through the script to generate a final test case library includes:

[0096] During the selection process, if you specify to select all test cases contained in a test file, test cases with specific marks will be excluded.

[0097] Based on the first aspect, in some embodiments of the present invention, in the test case in which the parent page jumps to the sub-page, the step of setting the name of the test case file corresponding to the sub-page as a mark includes:

[0098] The marker for jumping to a subpage is marked in the step of the use case, not in the use case itself.

[0099] Please refer to Figure 2 In a second aspect, an embodiment of the present invention provides a software automation testing device, characterized in that it includes:

[0100] Creation module 1: Create a test case directory structure that is isomorphic to the operation page of the app to be tested;

[0101] Editing module 2: Edit the test case file in the test case directory structure so that the name of the test case file is the same as the name of the folder where it is located;

[0102] Set flag module 3: In the test case where the parent page jumps to the sub-page, set the name of the test case file corresponding to the sub-page as a flag;

[0103] Set specific flag module 4: Set a specific flag use case on the child page to return to the parent page;

[0104] Stay module 5: After each test case is tested, stay on the corresponding page;

[0105] Selection module 6: extract the selected test cases through scripts to generate the final test case library;

[0106] Execution module 7: The execution script reads the test case library and executes it.

[0107] For the specific implementation of the device, please refer to the embodiment of the above method, which will not be described in detail here.

[0108] In summary, the present invention provides a software automation testing method and device, by creating a test case directory structure isomorphic to the operation page of the app to be tested; editing the test case file in the test case directory structure so that the name of the test case file is the same as the name of the folder in which it is located; in the test case in which the parent page jumps to the sub-level page, the name of the test case file corresponding to the child page is set as a flag; a case containing a specific flag is set on the sub-level page for returning to the parent page; after each test case is tested, it stays on the corresponding page; the selected test case is extracted by a script to generate a final test case library; the script is executed to read the test case library and execute it. The execution order can be arbitrarily formulated, and even the program can be allowed to randomly arrange the case for execution. Redundant operations are greatly reduced, and some repeated page jumps are automatically realized by the program. The execution of repeated steps is greatly reduced, thereby reducing the execution time. Close to the user's usage scenario. The case can be selected for execution at will.

[0109] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

[0110] It will be apparent to those skilled in the art that the present application is not limited to the details of the exemplary embodiments described above, and that the present application can be implemented in other specific forms without departing from the spirit or essential features of the present application. Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of the present application is defined by the appended claims rather than the above description, and it is intended that all changes falling within the meaning and scope of the equivalent elements of the claims be included in the present application. Any reference numeral in a claim should not be considered as limiting the claim to which it relates.

Claims

1. A software automated testing method, characterized in that: include: Create a test case directory structure that is the same as the operation page of the app to be tested; Edit the test case file in the test case directory structure so that the name of the test case file is the same as the name of the folder in which it is located; In the test case where the parent page jumps to the sub-page, the name of the test case file corresponding to the sub-page is set as a flag; In the child page, set up a specific flag case to return to the parent page; After each test case is completed, stay on the corresponding page; Extract the selected test cases through scripts to generate the final test case library; The execution script reads the test case library and executes it; The steps of selection include: When executing the two use case files A and B in sequence; If A and B are in a parent-child relationship, first extract the test cases in file A and put them in the test library, then extract the test cases marked with B from the test file A and put them in the test library, and finally extract the test cases in file B and put them in the test library; If A and B are grandparents and grandchildren, and the execution order is A, C, D, B, then first extract the test cases in file A and put them in the test library, then extract the test cases marked with C from file A and put them in the test library, then extract the test cases marked with D from file C and put them in the test library, then extract the test cases marked with B from file D and put them in the test library, and finally extract the test cases in file B and put them in the test library; If A and B are in a child-parent relationship, first extract the test cases in file A and put them in the test library, then extract the test cases with specific mark cases from test file A and put them in the test library, and finally extract the test cases in file B and put them in the test library; If A and B are grandchild and ancestor, and the execution order is A, C, D, B, then first extract the test cases in file A and put them in the test library, then extract the test cases with specific mark cases from test file A and put them in the test library, then extract the test cases with specific mark cases from test file C and put them in the test library, and finally extract the test cases in file B and put them in the test library; When A and B have no father-son, son-father, grandfather-grandson, and grandson-grandfather relationship, according to the test case directory structure described in S1, A and B must have a common ancestor. The processing process at this time is to first find their common ancestor D, and then follow the grandson-ancestor process in the order of A and D, put the selected test cases into the test library, and then follow the grandfather-grandson process in the order of D and B, and put the selected test cases into the test library.

2. A software automated testing method according to claim 1, characterized in that: Also includes: The step of creating a test case directory structure that is isomorphic to the operation page of the app to be tested includes: In the test case directory structure, if the bottom tab has no parent-child page relationship, a main page is virtualized as the virtual parent page of the tab.

3. A software automation testing method according to claim 1, characterized in that: Also includes: The step of setting a specific flag use case on the child page to return to the parent page also includes: Each use case file has only one specific marker use case, which is used to return to the parent page from the current page.

4. A software automated testing method according to claim 2, characterized in that: Also includes: In response to the specific marking case of the virtual parent page and the corresponding child page being selected, the parent page of the virtual parent page is returned.

5. A software automated testing method according to claim 2, characterized in that: After each test case is tested, before the step of staying on the corresponding page, the following steps are also included: Make the page where the App to be tested is located correspond to the App page corresponding to the file where the test case is located.

6. A software automated testing method according to claim 2, characterized in that: The step of extracting the selected test cases through the script to generate the final test case library includes: During the selection process, for test cases belonging to different pages, the test cases corresponding to the page jumps are automatically selected according to the path information.

7. A software automated testing method according to claim 1, characterized in that: The step of extracting the selected test cases through the script to generate the final test case library includes: During the selection process, if you specify to select all test cases contained in a test file, test cases with specific marks will be excluded.

8. A software automated testing method according to claim 1, characterized in that: In the test case in which the parent page jumps to the sub-level page, the step of setting the name of the test case file corresponding to the sub-level page as a mark includes: The marker for jumping to a subpage is marked in the step of the use case, not in the use case itself.

9. A software automated testing device, characterized in that: include: Create module: Create a test case directory structure that is isomorphic to the operation page of the app to be tested; Edit module: edit the test case file in the test case directory structure so that the name of the test case file is the same as the name of the folder where it is located; Set the flag module: In the test case where the parent page jumps to the sub-page, set the name of the test case file corresponding to the sub-page as the flag; Set specific flag module: set a specific flag use case on the child page to return to the parent page; Stay module: After each test case is tested, stay on the corresponding page; Selection module: extracts the selected test cases through scripts to generate the final test case library; The extraction steps include: when executing two use case files A and B in sequence; if A and B are in a parent-child relationship, first extract the test cases in file A and put them in the test library, then extract the test cases marked with B from the A test file and put them in the test library, and finally extract the test cases in file B and put them in the test library; if A and B are in a grandparent-grandchild relationship, and the execution order is A, C, D, B, then first extract the test cases in file A and put them in the test library, then extract the test cases marked with C from A and put them in the test library, then extract the test cases marked with D from file C and put them in the test library, then extract the test cases marked with B from file D and put them in the test library, and finally extract the test cases in file B and put them in the test library; if A and B are in a child-parent relationship, first extract the test cases in file A and put them in the test library, then extract the test cases with specific marks from the A test file The test cases of A are put into the test library, and finally the test cases in the B file are extracted and put into the test library; if A and B are grandchild and ancestor relationships, and the execution order is A, C, D, B, then the test cases in the A file are first extracted and put into the test library, and then the test cases with specific marked cases are extracted from the A test file and put into the test library, and then the test cases with specific marked cases are extracted from the C test file and put into the test library, and finally the test cases in the B file are extracted and put into the test library; when A and B do not have a father-son, child-father, grandparent-grandchild, and grandchild-grandparent relationship, according to the test case directory structure described in S1, A and B must have a common ancestor. At this time, the processing process is to first find their common ancestor D, and then follow the grandchild-ancestor process in the order of A and D, put the extracted test cases into the test library, and then follow the grandparent-grandchild process in the order of D and B, and put the extracted test cases into the test library; Execution module: The execution script reads the test case library and executes it.

Images