Self-test case generation and management method
Through the classification storage and management method of test case tree graph, the problem of low efficiency in traditional self-test use cases is solved, efficient self-test use cases generation, classification and reuse is achieved, and the testing efficiency and accuracy of software development is improved.
Patent Information
- Application Number
- CN202411348502.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-26
- Publication Date
- 2025-01-07
AI Technical Summary
During the software development process, traditional self-test use case management methods are difficult to maintain, have low query efficiency, and low reuse rate of self-test use cases, resulting in developers facing the challenges of writing, accumulating and managing self-test use cases.
The test case tree diagram is used to store completed test cases in the classified branch, including branches classified by functional modules, business processes and test types. It searches for relevant test cases by searching information, generates and manages test cases, and supports automatic import, Modify and execute test scripts.
It improves the reusability and management efficiency of self-test use cases, reduces maintenance complexity and cost, realizes the automated accumulation, classification and reuse of self-test use cases, and improves testing efficiency and accuracy.
Smart Images
Figure CN119271553A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of software development and testing, and more specifically to a method for generating and managing self-test cases. Background Art
[0002] In the software development process, self-testing is an important part of ensuring software quality. However, with the continuous increase in software functions and the improvement in complexity, how to effectively write, accumulate and manage self-test cases has become a major challenge for developers. Traditional self-test case management methods are often based on documents or simple database storage. This method has many problems, such as difficult maintenance, low query efficiency, and low reuse rate of self-test cases. Summary of the invention
[0003] In view of the above problems, the present disclosure provides a method for generating and managing self-test cases for developers to write, accumulate, manage and reuse software self-test cases.
[0004] The present disclosure provides a method for generating and managing self-test cases, comprising: according to the test case being written, using a test case tree diagram to search for related test cases for generating completed test cases; the test case tree diagram is used to store the completed test cases in each branch of the tree diagram; each branch includes at least one of a branch classified by functional module, a branch classified by business process, and a branch classified by test type; and the completed test cases are imported into the test case tree diagram for managing all completed test cases.
[0005] According to an embodiment of the present disclosure, according to the test case being written, a test case tree diagram is used to search for related test cases for generating a completed test case, including: searching for related test cases according to the retrieval information of the test case being written; the retrieval information includes at least one of business process branch information, functional module branch information, and test type branch information; using the related test cases, the test conditions and requirement analysis diagram of the related test cases are obtained; the test conditions include parameters and parameter boundary values of the related test cases; the requirement analysis diagram is used to characterize the critical path, data flow, and business logic of the related test cases; using the test conditions and the requirement analysis diagram, a completed test case is generated.
[0006] According to an embodiment of the present disclosure, a completed test case is generated using test conditions and a requirement analysis diagram, including: using some test conditions in the test conditions to generate test conditions for a test case being written; generating a requirement analysis diagram for the test case being written based on the requirement analysis diagram; generating a completed test case based on the test conditions and the requirement analysis diagram for the test case being written.
[0007] According to an embodiment of the present disclosure, related test cases are searched based on the retrieval information of the test case being written, including: determining the current branch where the test case being written is located based on the current branch information contained in the retrieval information; sorting the branch information contained in the retrieval information from superior to subordinate according to the branch hierarchy; in response to the existence of next branch information, re-executing the step of determining the current branch where the test case being written is located based on the current branch information contained in the retrieval information according to the next branch information contained in the retrieval information as the current branch information; and searching in the current branch using the keywords of the test case being written to obtain related test cases.
[0008] According to an embodiment of the present disclosure, completed test cases are imported into a test case tree diagram for managing all completed test cases, including: generating tags based on keywords of the completed test cases for association with the completed test cases; and storing the completed test cases in the test case tree diagram based on retrieval information.
[0009] According to an embodiment of the present disclosure, a test case tree diagram includes test case tree diagrams of various versions of a test system; completed test cases are imported into the test case tree diagram for managing all completed test cases, and then further includes: managing all completed test cases according to the test case tree diagram, including: using the current version of the test case tree diagram to add, delete, modify and / or search for completed test cases; writing test scripts according to the completed test cases, and associating the test scripts with the test cases; wherein, deleting and / or modifying completed test cases includes: using the test case tree diagram to search for related test cases, and deleting and / or modifying related test cases in batches.
[0010] According to an embodiment of the present disclosure, a test script is written according to a completed test case, and the test script is associated with the test case, and then the method further includes: automatically executing the associated test script in response to selecting a completed test case; and saving the result of running the test script to the completed test case.
[0011] The second aspect of the present disclosure provides a self-test case generation and management device, which can be used to implement the above method, and the device includes: a generation module, which is used to use a test case tree diagram to find related test cases according to the test case being written to generate a completed test case; the test case tree diagram is used to classify and store the test cases in each branch of the tree diagram; each branch includes at least one of the branches classified by functional modules, the branches classified by business processes, and the branches classified by test types; a management module, which is used to import the completed test cases into the test case tree diagram for managing all completed test cases.
[0012] A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned method for generating and managing self-test cases.
[0013] A fourth aspect of the present disclosure further provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the above-mentioned method for generating and managing self-test cases.
[0014] According to the generation and management method of self-test cases provided by the present disclosure, completed test cases are accumulated and classified through the test case tree diagram. Since test cases can be classified and stored, and related test cases can be retrieved efficiently, the technical problems of difficult maintenance, low query efficiency, and low reuse rate of self-test cases are at least partially solved, and the technical effect of assisting developers to efficiently write self-test cases and realize automatic accumulation, classification, retrieval and reuse of self-test cases is achieved, thereby improving the efficiency and accuracy of self-testing and reducing the cost of self-testing is achieved. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 A flowchart schematically illustrates a method for generating and managing self-test cases according to an embodiment of the present disclosure;
[0016] Figure 2 A schematic diagram schematically shows a system for generating and managing a self-test case according to an embodiment of the present disclosure;
[0017] Figure 3 A structural block diagram of a device for generating and managing self-test cases according to an embodiment of the present disclosure is schematically shown;
[0018] Figure 4 A block diagram of an electronic device suitable for implementing a method for generating and managing self-test cases according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION
[0019] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.
[0020] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.
[0021] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.
[0022] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).
[0023] First, the technical terms involved in this disclosure are explained as follows:
[0024] Parameter boundary values of test cases: refers to a strategy for testing values on the boundary of the input or output range in software testing. Boundary value testing is based on the assumption that a large number of errors tend to occur on the boundary of the input or output range, rather than inside the range. Boundary Value Testing is a black box testing method that focuses on testing the boundary values of the input or output range. By designing test cases to cover these boundary values, potential errors and anomalies can be discovered more effectively.
[0025] Requirements analysis diagram: is a graphical representation method used to display the results of software requirements analysis. It usually presents the functional requirements, business logic, data flow and other key information of the software system intuitively through charts, flow charts, UML (Unified Modeling Language) diagrams and other forms. In the process of writing self-test cases, the role of the requirements analysis diagram is mainly reflected in the following aspects: through graphical methods, developers can more easily understand the complex requirements of the system and clarify the goals and scope of the test; the key paths, data flows, business logic, etc. in the requirements analysis diagram can be used as a reference for test case design, helping developers to design test cases with clear structure and comprehensive coverage; in the process of drawing the requirements analysis diagram, developers can more easily find contradictions, omissions or ambiguities between requirements, so as to communicate with the demander in a timely manner to avoid discovering problems in the testing phase.
[0026] Figure 1The flowchart of the method for generating and managing self-test cases according to an embodiment of the present disclosure is schematically shown. Figure 1 As shown, an embodiment of the present disclosure provides a method for generating and managing self-test cases, including: S1, according to the test case being written, using a test case tree diagram to search for related test cases for generating completed test cases; the test case tree diagram is used to store the completed test cases in each branch of the tree diagram; each branch includes at least one of a branch classified by functional module, a branch classified by business process, and a branch classified by test type; S2, importing the completed test case into the test case tree diagram for managing all completed test cases.
[0027] Through the embodiments of the present disclosure, test cases are organized and managed through a test case tree diagram, which improves the reusability and management efficiency of test cases, makes the operations of searching, generating, modifying, deleting and associating scripts of test cases more convenient and efficient, and reduces the complexity and cost of test case maintenance. At the same time, the automatic accumulation, classification, retrieval and reuse of self-test cases reduces the repetitive work of developers and improves the efficiency and accuracy of self-testing.
[0028] On the basis of the above-mentioned embodiment, according to the test case being written, the test case tree diagram is used to search for related test cases for generating a completed test case, including: searching for related test cases according to the retrieval information of the test case being written; the retrieval information includes at least one of the business process branch information, the functional module branch information, and the test type branch information; using the related test cases, the test conditions and the requirement analysis diagram of the related test cases are obtained; the test conditions include the parameters and the parameter boundary values of the related test cases; the requirement analysis diagram is used to characterize the critical path, data flow, and business logic of the related test cases; using the test conditions and the requirement analysis diagram, a completed test case is generated.
[0029] In this embodiment, a graphical or coded self-test case writing tool is provided to help developers quickly write self-test cases with clear structure and accurate description. During the writing process, similar test cases are automatically identified to prompt the writing personnel to avoid duplication of test cases, and related test cases are used to provide references for the writing personnel.
[0030] Through the embodiments of the present disclosure, by searching the retrieval information (such as business process, function module, test type, etc.) of the test case being written, the relevant test cases are found in the test case tree diagram, providing a reference for generating new test cases. The reusability of the test cases is improved, and the repeated writing of similar test cases is avoided, while also ensuring the integrity and accuracy of the new test cases.
[0031] On the basis of the above-mentioned embodiment, a completed test case is generated by using test conditions and requirement analysis diagram, including: using part of the test conditions in the test conditions to generate the test conditions of the test case being written; generating the requirement analysis diagram of the test case being written according to the requirement analysis diagram; generating a completed test case according to the test conditions and requirement analysis diagram of the test case being written.
[0032] In this embodiment, during the writing process, a parameterized test writing function is provided, each test condition includes multiple parameters, and a test scenario is a combination of various conditions. By automatically selecting different conditions and different parameters for each condition, a test case is automatically generated.
[0033] In this embodiment, according to the relevant test cases, a requirement analysis diagram and input and output boundary values are provided to provide a reference for writing test cases. It should be noted that the present disclosure provides a graphical or coded self-test case writing tool, which generates test cases more efficiently through a requirement analysis diagram, reducing the difficulty and complexity of self-test case writing.
[0034] It should be noted that in this embodiment, the test case being written can be directly generated only through the test conditions; or the test case being written can be directly generated only through the requirement analysis diagram. When it is not possible to directly generate, only the test conditions of the relevant test case and the requirement analysis diagram are used as references, and the writing personnel complete the writing of the test case through the provided self-test case writing tool.
[0035] Through the embodiments of the present disclosure, test conditions and requirement analysis diagrams are extracted from relevant test cases, and new test cases are generated in combination with the requirements of the test cases being written, so that the generation of test cases is more standardized and systematic, and the quality of test cases is improved. At the same time, by reusing existing self-test cases and modifying the parameters of existing self-test cases, the workload of test case writing for new test tasks is reduced, and the cost of self-testing is reduced.
[0036] On the basis of the above embodiment, according to the retrieval information of the test case being written, the related test cases are searched, including: determining the current branch where the test case being written is located according to the current branch information contained in the retrieval information; sorting the branch information contained in the retrieval information from superior to subordinate according to the branch hierarchy; in response to the existence of the next branch information, re-executing the step of determining the current branch where the test case being written is located according to the current branch information contained in the retrieval information based on the next branch information contained in the retrieval information as the current branch information; and searching in the current branch using the keywords of the test case being written to obtain the related test cases.
[0037] In this embodiment, for example, after each version is released, select "smoke test" in the test case category column, and the interface displays all the test cases of "smoke test". Click each test case one by one to view the content of the test case. If you want to test, after connecting the test equipment, click the test button to automatically send the test message and control the hard-line signal to complete the test of this test case. For the results that the software cannot recognize, the user is prompted to recognize them by himself, and finally compare them with the results of the use case, and fill in the test results as required. The results that the software can automatically recognize are recognized by the software and automatically filled in the test results.
[0038] Through the embodiments of the present disclosure, a process of searching for relevant test cases in a test case tree diagram according to retrieval information is provided, thereby ensuring the accuracy and efficiency of the search process.
[0039] Based on the above embodiment, the completed test cases are imported into the test case tree diagram for managing all completed test cases, including: generating tags based on the keywords of the completed test cases for association with the completed test cases; and storing the completed test cases in the test case tree diagram based on the retrieval information.
[0040] In this embodiment, the self-test cases written by developers are automatically accumulated into the system, and are classified and marked to facilitate subsequent management and retrieval. The writing module imports the tree diagram according to the required scenario, and the test cases can be saved under different branches of the tree diagram according to the scenario, which is conducive to the subsequent retrieval of the test cases according to the dimensions of functional modules, business processes, test types, etc., so as to quickly locate the target test cases. Appropriate tags are added to the test cases, such as "regression test", "smoke test", "performance test", etc., and test cases that meet specific requirements can be quickly screened out through tags. Therefore, users are supported to customize the classification, marking and retrieval conditions of self-test cases to meet the needs of different projects and teams.
[0041] It should be noted that each version of the software has a corresponding test case tree diagram. The test cases are managed using a version control system to ensure that updates and changes to the test cases can be tracked and traced, while avoiding confusion between different versions.
[0042] It should be noted that if the new test case is only a minor modification of an existing test case, it will not be stored to avoid wasting system resources.
[0043] Through the embodiments of the present disclosure, newly generated or modified test cases are imported into the test case tree diagram for unified management, thereby maintaining the consistency and maintainability of the test cases and facilitating subsequent search, modification and deletion operations.
[0044] On the basis of the above-mentioned embodiment, the test case tree diagram includes test case tree diagrams of various versions of the test system; the completed test cases are imported into the test case tree diagram for managing all completed test cases, and then it also includes: managing all completed test cases according to the test case tree diagram, including: using the current version of the test case tree diagram to add, delete, modify and / or search for completed test cases; writing test scripts according to the completed test cases, and associating the test scripts with the test cases; wherein, deleting and / or modifying the completed test cases includes: using the test case tree diagram to search for related test cases, and deleting and / or modifying related test cases in batches.
[0045] In this embodiment, the functions of adding, deleting, modifying and checking self-test cases are provided, allowing developers to maintain and manage self-test cases at any time. At the same time, the historical record function of adding, deleting and modifying is provided, and the content before each of the above operations can be found later, which is convenient for backtracking historical cases. It supports the retrieval of self-test cases based on keywords, function points, modules and other conditions to improve the retrieval efficiency and accuracy. It can also be retrieved through a tree diagram. At the same time, a historical version can be selected to retrieve the test cases in the historical version.
[0046] In this embodiment, developers are allowed to write test scripts according to test cases and associate them with test cases. During the test process, they can click the corresponding button to perform automated testing on this test case, avoiding the tediousness and errors of manual operation. For example, for relevant test cases, if you want to test, after connecting the test equipment, click the test button to automatically send the test message and control the hard-line signal to complete the test of this test case. For results that the software cannot recognize, the user is prompted to recognize them by himself, and finally compare them with the results of the use case, and fill in the test results as required. The results that the software can automatically recognize are recognized by the software and automatically filled in the test results.
[0047] It should be noted that the trial case must be updated according to the version of the requirement, and at this time, the original test case needs to be modified. Find the branch where the requirement is changed according to the tree diagram, analyze all the test cases under this branch, and see if there are any places that need to be modified according to the new requirements. Click the Modify button to make the modification. If the modified case has a test script, modify the script accordingly, and finally click Save. If the test case is completely outdated and does not meet the new requirements, click the Delete button to delete it. Programs usually have old versions that need to be maintained, and the old versions of the program correspond to the old requirements. When testing the old version, you can view the modification record of the test case and find the test case of the old version for testing, instead of using the test case of the new requirement to test the old version of the program.
[0048] Through the embodiments of the present disclosure, multi-version management of the test case tree diagram is supported, and test scripts can be written and associated, thereby meeting the test requirements in different test phases or different test environments and improving the flexibility and automation of the test.
[0049] Based on the above embodiment, a test script is written according to the completed test case, and the test script is associated with the test case. It also includes: in response to selecting the completed test case, automatically executing the associated test script; saving the result of the test script running to the completed test case.
[0050] In this embodiment, before the release, the completed test cases also include self-verification of the software developer's own changes. Find all the test cases corresponding to the change points in the tree diagram, identify each test case, and find the most relevant test case. If there is no relevant test case, click Add Test Case to add the test content according to the test case template. Focus on testing the boundary conditions of the requirements prompted in the template. After writing the test case, add the test script in the script to automatically send messages and hard-wired signals for testing.
[0051] In this embodiment, the automatic execution and result analysis of self-test cases are supported, which helps developers to locate problems quickly and improves test accuracy.
[0052] Through the embodiments of the present disclosure, after selecting a completed test case, the associated test script is automatically executed and the result is saved in the test case, which simplifies the test process, improves the test efficiency, and also facilitates the tracing and analysis of the test results.
[0053] Figure 2 The following is a schematic diagram of a system for generating and managing self-test cases according to an embodiment of the present disclosure. Figure 2 As shown. A developer software self-test case accumulation and management system includes a self-test case writing module, a self-test case accumulation module, a self-test case management module, a self-test case retrieval module, a self-test case reuse module and a test execution and result analysis module, wherein the self-test case writing module is used to assist developers in writing self-test cases; the self-test case accumulation module is used to automatically accumulate self-test cases and classify and mark them; the self-test case management module is used to add, delete, modify and query self-test cases; the self-test case retrieval module supports the retrieval of self-test cases based on keywords, function points, modules and other conditions; the self-test case reuse module allows the reuse of existing self-test cases in new test tasks; the test execution and result analysis module supports self-test cases. It can be understood that the developer software self-test case accumulation and management system is configured to be able to implement any of the above-mentioned self-test case generation and management methods.
[0054] In this embodiment, the "self-test case writing module" and "self-test case accumulation module" write the written cases into the database; the "self-test case management module", "self-test case retrieval module" and "self-test case reuse module" process the case data in the database. The "test case execution and analysis module" controls the device to test through the communication line such as the CAN network, and compares and analyzes the test execution results with the results of the case.
[0055] Through the embodiments of the present disclosure, developers use the self-test case writing module to write self-test cases, and can choose a graphical or coded method. After the self-test case is written, the self-test case accumulation module automatically accumulates the self-test case into the system, and classifies and marks it. Developers can add, delete, modify, and check self-test cases through the self-test case management module, and maintain and manage self-test cases at any time. When testing is required, developers can retrieve self-test cases according to keywords, function points, modules and other conditions through the self-test case retrieval module. The retrieved self-test cases can be directly used in new test tasks through the self-test case reuse module to reduce duplication of work. The test execution and result analysis module supports the automated execution and result analysis of self-test cases, helping developers to quickly locate problems and improve test accuracy. The system adopts a modular design, is easy to expand and maintain, and can adapt to software development projects of different scales and complexities.
[0056] Based on the above self-test case generation and management method, the present disclosure also provides a self-test case generation and management device, which is configured to implement the above self-test case generation and management method. Figure 3 The device is described in detail.
[0057] Figure 3 The structural block diagram of the device for generating and managing self-test cases according to an embodiment of the present disclosure is schematically shown.
[0058] like Figure 3 As shown, the self-test case generation and management device of this embodiment includes a generation module and a management module.
[0059] The generation module is used to use the test case tree diagram to search for related test cases according to the test case being written to generate a completed test case. In one embodiment, the generation module can be used to perform the operation S1 described above, which will not be repeated here.
[0060] The management module is used to import the completed test cases into the test case tree diagram for managing all completed test cases. In one embodiment, the management module can be used to perform the operation S2 described above, which will not be described in detail here.
[0061] Figure 4A block diagram of an electronic device suitable for implementing a method for generating and managing self-test cases according to an embodiment of the present disclosure is schematically shown.
[0062] like Figure 4 As shown, the electronic device 400 according to an embodiment of the present disclosure includes a processor 401, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 402 or a program loaded from a storage part 408 to a random access memory (RAM) 403. The processor 401 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 401 may also include an onboard memory for caching purposes. The processor 401 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.
[0063] In RAM 403, various programs and data required for the operation of electronic device 400 are stored. Processor 401, ROM 402 and RAM 403 are connected to each other via bus 404. Processor 401 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 402 and / or RAM 403. It should be noted that the program can also be stored in one or more memories other than ROM 402 and RAM 403. Processor 401 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in one or more memories.
[0064] According to an embodiment of the present disclosure, the electronic device 400 may further include an input / output (I / O) interface 405, which is also connected to the bus 404. The electronic device 400 may further include one or more of the following components connected to the I / O interface 405: an input portion 406 including a keyboard, a mouse, etc.; an output portion 407 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 408 including a hard disk, etc.; and a communication portion 409 including a network interface card such as a LAN card, a modem, etc. The communication portion 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. A removable medium 411, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 410 as needed, so that a computer program read therefrom is installed into the storage portion 408 as needed.
[0065] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.
[0066] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method provided by the embodiment of the present disclosure.
[0067] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).
[0068] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing 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 boxes represented in succession 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 or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0069] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.
[0070] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.
Claims
1. A method for generating and managing self-test cases, characterized in that: include: Based on the test case being written, use the test case tree diagram to find related test cases for generating completed test cases; The test case tree diagram is used to store completed test cases in each branch of the tree diagram; The branches include at least one of branches classified by functional modules, branches classified by business processes, and branches classified by test types; The completed test cases are imported into the test case tree diagram for managing all completed test cases.
2. The method according to claim 1, wherein: The method of searching for related test cases based on the test case being written to generate a completed test case by using the test case tree diagram includes: Searching for relevant test cases according to the search information of the test case being written; the search information includes at least one of business process branch information, function module branch information, and test type branch information; Using relevant test cases, test conditions and requirement analysis diagrams of relevant test cases are obtained; the test conditions include parameters and parameter boundary values of relevant test cases; the requirement analysis diagram is used to characterize the key path, data flow, and business logic of relevant test cases; A completed test case is generated using the test conditions and the requirement analysis diagram.
3. The method according to claim 2, wherein: The step of generating a completed test case by using the test conditions and the requirement analysis diagram includes: Using some of the test conditions, generating test conditions for the test case being written; Generate a requirement analysis diagram for the test case being written according to the requirement analysis diagram; Generate completed test cases based on the test conditions and requirement analysis diagram of the test case being written.
4. The method according to claim 2, wherein: The step of searching for relevant test cases according to the search information of the test case being written includes: According to the current branch information contained in the search information, determine the current branch where the test case being written is located; the branch information contained in the search information is sorted from upper to lower according to the branch hierarchy; In response to the existence of next branch information, the step of determining the current branch where the test case being written is located according to the current branch information contained in the retrieval information is re-executed according to the next branch information contained in the retrieval information as the current branch information; The keyword of the test case being written is used to search in the current branch to obtain the related test case.
5. The method according to claim 2, wherein: Importing the completed test cases into the test case tree diagram for managing all completed test cases, including: generating tags according to the keywords of the completed test cases to be associated with the completed test cases; The completed test cases are stored in the test case tree diagram according to the retrieval information.
6. The method according to claim 1, wherein: The test case tree diagram includes test case tree diagrams of various versions of the test system; Importing the completed test cases into the test case tree diagram for managing all completed test cases, and then further comprising: Manage all completed test cases according to the test case tree diagram, including: Using the current version of the test case tree diagram, add, delete, modify and / or search for completed test cases; Writing a test script according to the completed test case, and associating the test script with the test case; Wherein, deleting and / or modifying the completed test cases includes: using the test case tree diagram to search for related test cases, and deleting and / or modifying the related test cases in batches.
7. The method according to claim 6, wherein: Writing a test script according to the completed test case, associating the test script with the test case, and then further comprising: In response to selecting a completed test case, automatically executing the associated test script; The result of running the test script is saved to the completed test case.
8. A device for generating and managing self-test cases, characterized in that: The device can be used to implement the method according to any one of claims 1 to 7, and the device comprises: A generation module, used for searching related test cases for generating completed test cases by using a test case tree diagram according to the test case being written; the test case tree diagram is used for classifying and storing the test cases in branches of the tree diagram; the branches at least include one of branches classified by functional modules, branches classified by business processes, and branches classified by test types; A management module is used to import the completed test cases into the test case tree diagram for managing all completed test cases.
9. An electronic device, comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are caused to execute the method according to any one of claims 1 to 7.
10. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 7.