Modularized business process-based test case design method and framework thereof

Through the test case design method of modular business processes, the testing requirements are refined and the black box testing method is combined with the problem of insufficient coverage of test cases in the existing technology, and more efficient software quality assurance is achieved.

CN119003369AInactive Publication Date: 2024-11-22TALENT YOUNG INFORMATION TECH (WEIHAI) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411251679.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-09
Publication Date
2024-11-22
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

During the software testing process, it is difficult for the prior art to design test cases with high adequacy, correctness and effectiveness, especially when modular business processes and testing needs are complex, resulting in insufficient software quality assurance.

Method used

Using a test case design method based on modular business processes, we use black box testing through the ideas of input, logic processing, and output, combining rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenario dimensions. Methods design verification points and form test plans, write test cases, and manage and maintain them.

Benefits of technology

It improves the coverage of test cases and improves the universality and efficiency of test design, and ensures the quality of software.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119003369A_ABST
    Figure CN119003369A_ABST
Patent Text Reader

Abstract

The invention discloses a test case design method based on a modular business process and a framework thereof, and relates to the technical field of software testing. The method comprises the following steps: S1, based on a modular business process and a test demand, adopting thoughts of input, logic processing and output to refine the test demand, and forming business logic processing; and S2, further carrying out detailed analysis from the dimensions of rule constraint, a normal scene, an abnormal scene, an interaction scene, a special scene and an interface scene, and identifying influence factors. According to the test case design method and the framework provided by the invention, based on a modular business process and test requirements, the test requirements are refined by adopting thoughts of input, logic processing and output; and forming business logic processing, namely a business flow chart, configuration (such as parameter configuration and the like) related to business flow development, an interface related to business flow development, a database table related to business flow development and a log related to business flow development.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of software testing, and in particular to a test case design method based on modular business processes and a framework thereof. Background Art

[0002] The development model that supports the software development model has evolved from the waterfall model, rapid prototyping model, iteration model, spiral model to the currently widely used agile model, with different eras, different product forms and different requirements for cost, quality and efficiency. Regardless of the model, testing is one of the important links and one of the important measures for software quality assurance. Software testing has gone through a long development process. Early software showed the characteristics of simple structure, limited functions and small scale. Testing during this period was equivalent to debugging. As the scale of software becomes larger and larger, the scope of verification becomes wider and wider, such as interface logic, functional modules, coupling between different functional modules, etc., and an independent testing organization needs to be introduced for independent testing. At this stage, the testing methodology has not yet been formed, and testing mainly relies on conjecture and inference. There are still many problems after the software is delivered. With the accumulation of software testing experience, the emphasis on software quality in the industry, and the significance of software testing as one of the important measures for software quality assurance, after continuous exploration by industry experts, IEEE defined software testing at the first technical conference on software testing held at the University of North Carolina in 1983: Software testing is the process of running or measuring a system using manual or automatic means, with the purpose of verifying whether it meets the specified requirements or finding out the difference between the expected results and the actual results. Software testing has become a discipline, a process that needs to go through complete stages such as design, development and maintenance, with concepts, principles, processes, methods and technologies. Even so, in the general software development model, testing work almost always starts after the software functional module is completed or the entire software is completed. At this time, if defects are found in the test and the development is modified, it will inevitably consume a lot of manpower, material resources and time costs. Until the current popular agile model, it optimized the concept of software testing, that is, "testing before development". Testers participate in the software requirements analysis stage, understand the requirements and design of the entire software, and can develop test code in advance to identify and correct potential defects as early as possible. In this way, the efficiency of software development and testing has been greatly improved, and the software quality is more guaranteed. With the rapid development of artificial intelligence and big data, software testing will inevitably receive more and more attention, and software testing ideas and methods will inevitably need to be continuously explored and evolved.

[0003] The software development and system file sub-classification in the national standard information technology and office machinery classification clearly explains the computer software testing specifications to guide the specific implementation of software testing work. Among them, the testing process is divided into four activities, in order: test planning, test design, test execution, and test summary.

[0004] Test planning: mainly involves conducting test requirements analysis, determining the content or quality characteristics that need to be tested, and developing a test plan.

[0005] Test design: Analyze and select existing test cases or design new test cases based on test requirements, determine the execution order of test cases, and review the correctness, effectiveness, and coverage of test cases.

[0006] Test execution: execute test cases, obtain test results, analyze and judge test results. Check the normal or abnormal termination of the test process. Based on the check results, decide whether to stop the test, modify or supplement the test case set, and conduct further testing for test cases that do not meet the test termination conditions.

[0007] Test summary: organize and analyze test data, evaluate test results and tested software items, describe test status, complete software test report, and pass test review.

[0008] For test planning, test requirements analysis is conducted to determine the quality characteristics that need to be tested as functionality, reliability, usability, efficiency, maintainability, and portability, and the content that needs to be tested is determined to be software modules or business processes or business process customization requirements. For test design, based on the content or quality characteristics that need to be tested determined by the test requirements analysis, the commonly used black box testing methods, namely the boundary value equivalence class method and the scenario method, are used to design test cases. However, the granularity of the content or quality characteristics that need to be tested determined by the test requirements analysis is too large. Using this as the entry point for designing test cases by the black box testing method, the test cases finally formed lack sufficient coverage and are difficult to guarantee their correctness and effectiveness. At the same time, considering the update and replacement of test team members, for new employees, the lack of familiarity with software business and insufficient testing skills make the quality of test cases formed by the above method even more worrying. In the entire software testing process, the test cases formed by the test design activities can be compared to the development output code, and their importance is self-evident. If the quality of the test cases finally formed cannot be guaranteed, it will directly affect the quality and effect of the software testing itself, and thus the software quality assurance will be greatly reduced. Considering that current software demand analysis and system design mostly adopt the idea of ​​modular business process to carry out demand planning and design.

[0009] Therefore, a test case design method and its framework based on modular business process are proposed. Summary of the invention

[0010] The purpose of the present invention is to solve the problems raised in the above background technology, and provide a test case design method and a framework thereof based on modular business processes.

[0011] In order to achieve the above-mentioned purpose, the present invention specifically adopts the following technical solutions:

[0012] The test case design method based on modular business process includes the following steps:

[0013] S1. Based on modular business processes and test requirements, the idea of ​​input, logic processing, and output is used to refine the test requirements and form business logic processing;

[0014] S2. Further detailed analysis from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios to identify influencing factors;

[0015] S3. Design verification points based on influencing factors using black box testing methods to form a test plan;

[0016] S4. Write test cases according to the test plan;

[0017] S5. Test case management and maintenance.

[0018] Furthermore, the modular business process, for different software, modularly classifies the software from the functional dimension, such as system management, business module, statistical analysis, etc., and then based on each module, sorts out the business process from the user's perspective, such as user role authority management and basic data management in the system management module. The test requirements are the content or quality characteristics that need to be tested determined by the test requirements analysis in the test planning. The business logic processing involves business process diagrams, configurations related to business process development (such as parameter configuration, etc.), interfaces related to business process development, database tables related to business process development, and logs related to business process development, which are carried out using mind maps.

[0019] Furthermore, the rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenario dimensions are:

[0020] Rules and constraints: the rules and constraints that need to be followed in carrying out business processes;

[0021] Normal scenario: When the business process is carried out, data that meets the requirements is input, and after logical processing, the expected output is given;

[0022] Abnormal scenario: When the business process is in progress, if data that does not meet the requirements is entered, the software will give a friendly prompt after logical processing;

[0023] Interaction scenario: data related to business process development can be used as input or output for other business processes, and different channels can interact with each other to develop the same business process;

[0024] Special scenarios: scenarios where the software and hardware environment in which the software runs is abnormal;

[0025] Interface scenario: Each interface related to the business process has a unified interface style, correct and friendly text descriptions, friendly layout, and buttons on the interface are available and correct;

[0026] The influencing factors are key points that affect the development of business processes from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios.

[0027] Furthermore, the black box testing method includes common boundary value equivalence class methods, scenario methods, etc. The boundary value equivalence class method: boundary value analysis uses data equal to, less than or greater than the boundary value to carry out testing. The equivalence class divides the input domain into several parts, and selects representative data in each part to carry out testing. The boundary value equivalence class method focuses on data, complements each other, and is used in combination. The scenario method: with the event flow as the core, the path from a certain initial state of the software to a certain end state constitutes a use case scenario, focusing on the business process. The test plan includes checkpoints and verification points. The checkpoints include business checks, interface checks, database checks, and log checks carried out by the business process. The verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios, and the test scenario level is identified according to the degree to which the user cares about the software function. The normal scenario level is level 1, the rule constraints, abnormal scenarios, and interaction scenarios are level 2, the special scenarios are level 3, and the interface scenarios are level 4; the test plan is carried using a mind map.

[0028] Furthermore, the test cases are written according to the test plan, and the test cases are planned using the module and business process tree directory structure; the specific test case content is reflected using the use case title, use case number, prerequisites, test steps, expected results, and use case level basic element templates, and the use case level is equivalent to the test scenario level; combined with modular business processes and test requirements, the verification points and checkpoints in the test plan are expanded into the test case template to form a test case.

[0029] Furthermore, the test case management and maintenance uses modules and business process tree directory structures to plan test cases; customizes business process demand points, optimizes on the basis of existing business process test plans, and then improves test cases based on the optimized test plans; adds, deletes, and modifies test cases identified during test execution, optimizes on the basis of corresponding business process test plans, and then improves test cases based on the optimized test plans; and strategically selects test cases that need to be executed in regression testing based on the case level and specific test execution conditions.

[0030] A test case design framework based on modular business processes includes a business logic processing module, an influencing factor identification module, a test plan forming module, a test case forming module, and a test case management and maintenance module, wherein: the business logic processing module, based on modular business processes and test requirements, adopts the ideas of input, logic processing, and output to refine the test requirements, and forms a business process diagram, configurations related to business process development, interfaces related to business process development, database tables related to business process development, and logs related to business process development.

[0031] Furthermore, the influencing factor identification module further analyzes in detail the key points that affect the development of business processes from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios.

[0032] Furthermore, the test scheme forms a module, and verification points are designed based on influencing factors using a black box testing method. The black box testing method includes common boundary value equivalence class methods, scenario methods, etc. The test scheme includes checkpoints and verification points. The checkpoints include business checks, interface checks, database checks, and log checks carried out by business processes. Verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios. The test scenario level is identified according to the degree to which users care about software functions. The normal scenario level is level 1, the rule constraints, abnormal scenarios, and interactive scenarios are level 2, the special scenarios are level 3, and the interface scenarios are level 4.

[0033] Furthermore, the test case formation module is described, and test cases are written according to the test plan, and the test cases are planned using the module and business process tree directory structure; the specific test case content is reflected using the use case number, use case title, use case level, pre-conditions, operation steps, and expected result basic element templates, and the use case level is equivalent to the test scenario level; in combination with modular business processes and test requirements, the verification points and checkpoints in the test plan are expanded into the test case template to form a test case, and the test case management and maintenance module plans the test cases using the module and business process tree directory structure; for the customized demand points of the business process, the test plan of the existing business process is optimized, and then the test case is improved based on the optimized test plan; for the addition, deletion, and modification of the test cases identified during the test execution, the test plan of the corresponding business process is optimized, and then the test case is improved based on the optimized test plan; for the test cases that need to be executed in the regression test, they are strategically selected based on the use case level and the specific test execution situation.

[0034] The beneficial effects of the present invention are as follows:

[0035] 1. The test case design method and framework provided by the present invention are based on modular business processes and test requirements, and adopt the ideas of input, logic processing, and output to refine the test requirements, forming business logic processing, i.e., business process diagrams, business process development-related configurations (such as parameter configuration, etc.), business process development-related interfaces, business process development-related database tables, and business process development-related logs. Further detailed analysis and identification of the key points that affect the development of business processes from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios. It can be seen that the present invention, on the one hand, adopts the ideas of input, logic processing, and output to refine the test requirements, and further analyzes the test requirements in detail from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios, and refines the content or quality characteristics granularity determined by the test requirements analysis to be tested into key points, as the entrance of the black box test method to design test cases, so that the test design is comprehensive, and the test case coverage is improved. At the same time, the test requirements after the detailed analysis have clear details of the business process, which can ensure the correctness and effectiveness of the test cases. On the other hand, it is not limited to the design of a certain test requirement test case, which can improve the universality of the test case design.

[0036] 2. The test case design method and framework provided by the present invention use a black box test method to design verification points based on influencing factors, form a test plan, and write test cases according to the test plan. Black box test methods include common boundary value equivalence methods, scenario methods, etc. The boundary value equivalence method focuses on data, and the scenario method focuses on business processes. According to the characteristics of the influencing factors, a suitable black box test method is selected to design verification points. At the same time, the test plan includes checkpoints and verification points. The checkpoints include business checks, interface checks, database checks, and log checks carried out by the business process. The verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios. It can be seen that the present invention uses a suitable black box test method to design verification points based on influencing factors, which can reduce the redundancy of the test cases finally formed and improve the coverage of test cases. On the other hand, test cases are written according to the formed test plan. The test plan contains checkpoints and verification points. Checkpoints include business checks, interface checks, database checks, and log checks for business processes. Verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios. The consideration of checkpoints and verification points reflects full completeness and detail. Using the test plan as the basis for writing test cases can ensure the correctness and effectiveness of the test cases and improve the coverage of the test cases.

[0037] 3. The test case design method and framework provided by the present invention identify the test scenario level according to the degree to which the user cares about the software function, with the normal scenario level being level 1, the rule constraint, abnormal scenario, and interactive scenario level 2, the special scenario level 3, and the interface scenario level 4; plan test cases using the module and business process tree directory structure; optimize the test scheme of the existing business process based on the customized demand points of the business process, and then improve the test cases based on the optimized test scheme; optimize the test cases based on the test scheme of the corresponding business process for the addition, deletion, and modification of the test cases identified during the test execution, and then improve the test cases based on the optimized test scheme. For the test cases that need to be executed in the regression test, strategic selection is made based on the case level and the specific test execution situation. It can be seen that the present invention uses modules and business process tree directory structures to plan test cases on the one hand, customizes demand points for business processes, does not need to start from scratch, optimizes on the basis of the test scheme of the existing business process, and then improves the test cases based on the optimized test scheme, which can improve the efficiency of test case design. For new employees who are replaced by test team members, while improving their test case design efficiency, they can also improve their test case design quality. On the other hand, for the addition, deletion, and modification of test cases identified in the test execution, optimization is performed on the basis of the test scheme of the corresponding business process, and then the test cases are improved based on the optimized test scheme, which can always retain a complete test plan and test cases for the software, thereby improving the coverage adequacy of the test cases and ensuring the correctness and effectiveness of the test cases. On the other hand, the test scenario level is identified according to the degree to which the user cares about the software function, and the test cases to be executed are strategically selected according to the case level and the specific test execution situation in the regression test, which helps to improve the efficiency and quality of test execution. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 It is a schematic diagram of the mind map of the present invention;

[0039] Figure 2 It is a schematic diagram of the present invention for a detailed analysis of the key points affecting its development;

[0040] Figure 3 It is a schematic diagram of the design verification points of the black box testing method of the present invention;

[0041] Figure 4 It is a schematic diagram of the test scheme of the present invention using a mind map;

[0042] Figure 5 It is a schematic diagram for schematic testing of the present invention;

[0043] Figure 6It is a schematic flowchart diagram of a test case design method according to an embodiment of the present invention;

[0044] Figure 7 It is a structural schematic diagram of the test case design framework described in the present invention. DETAILED DESCRIPTION

[0045] In order 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 clearly and completely described below 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.

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

[0047] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. In addition, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0048] In the description of the embodiments of the present invention, it should be noted that the terms "inside", "outside", "upper", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, or are the orientations or positional relationships in which the inventive product is usually placed when used. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention.

[0049] like Figures 1 to 7 As shown, taking the appointment registration of self-service software in the medical field as the test requirement, a schematic test case is designed based on the test case design method of the present invention. Figure 1 As shown, the test case design method includes:

[0050] Step 110, based on the modular business process and test requirements, the test requirements are refined using the idea of ​​input, logic processing, and output to form business logic processing;

[0051] The modular business process, for different software, modularizes the software from the functional dimension, such as system management, business module, statistical analysis, etc., and then sorts out the business process from the user's perspective based on each module, such as user role authority management and basic data management in the system management module. The test requirements are the content or quality characteristics that need to be tested determined by the test requirements analysis in the test planning. The business logic processing involves business process diagrams, configurations related to business process development (such as parameter configuration, etc.), interfaces related to business process development, database tables related to business process development, and logs related to business process development, which are carried out using mind maps.

[0052] For self-service software in the medical field, its modular classification is registration, payment, system management, query and printing, etc. Based on the registration module, the business process is sorted out from the user's perspective. The business processes of the registration module include appointment registration, registration, and number collection. The test requirement is appointment registration. The input, logic processing, and output ideas are used to refine the test requirements to form business logic processing. Business logic processing involves business process diagrams, configurations related to business process development (such as parameter configuration, etc.), interfaces related to business process development, database tables related to business process development, and logs related to business process development, which are carried out using mind maps.

[0053] Step 120, further detailed analysis is performed from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios to identify influencing factors;

[0054] The influencing factors are key points that affect the development of business processes from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios.

[0055] For the appointment registration business process, the key factors that affect its development are further analyzed in detail from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios.

[0056] It can be seen that the present invention, on the one hand, adopts the idea of ​​input, logic processing, and output to refine the test requirements and form business logic processing. Business logic processing involves business process diagrams, configurations related to business process development (such as parameter configuration, etc.), interfaces related to business process development, database tables related to business process development, and logs related to business process development. The test requirements are further analyzed in detail from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios. The content or quality characteristics granularity determined by the test requirement analysis to be tested are refined into element points, i.e., influencing factors, as the entry point for designing test cases by the black box testing method, so that the test design is comprehensive and the test case coverage is improved. At the same time, the test requirements after the refinement analysis have clear details of the business process, which can ensure the correctness and effectiveness of the test cases. On the other hand, it is not limited to the design of a test case for a certain test requirement, and can improve the universality of the test case design.

[0057] Step 130, designing verification points using a black box testing method based on the influencing factors to form a testing plan;

[0058] The black box testing method includes common boundary value equivalence method, scenario method, etc. The boundary value equivalence method focuses on data, the scenario method focuses on business processes, and the appropriate black box testing method is selected according to the characteristics of the influencing factors to design verification points.

[0059] The test plan includes checkpoints and verification points. The checkpoints include business checks, interface checks, database checks, and log checks for business processes. The verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios. The test scenario levels are identified according to the degree to which users care about software functions. The normal scenario level is level 1, the rule constraints, abnormal scenarios, and interactive scenarios level 2, the special scenario level 3, and the interface scenario level 4. The test plan is carried using a mind map.

[0060] Step 140, writing test cases according to the test plan;

[0061] Use modules and business process tree directory structure to plan test cases; use case title, case number, precondition, test steps, expected results, and basic element templates of case level to reflect specific test case content. The case level is equivalent to the test scenario level; combine modular business processes and test requirements to expand the verification points and checkpoints in the test plan to the test case template to form a test case. For the verification point of the rule constraint dimension, it is impossible to make an appointment with a doctor within 7 days, but the appointment with a doctor after 7 days is successful.

[0062] It can be seen that the present invention adopts a suitable black box test method to design verification points based on the influencing factors, forms a test plan, and writes test cases according to the test plan. The black box test method includes common boundary value equivalence class methods, scenario methods, etc. The boundary value equivalence class method focuses on data, and the scenario method focuses on business processes. According to the characteristics of the influencing factors, the appropriate black box test method is selected to design verification points, which can reduce the redundancy of the test cases finally formed and improve the coverage of the test cases. At the same time, the test plan includes checkpoints and verification points. The checkpoints include business checks, interface checks, database checks, and log checks carried out by the business process. The verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios. The consideration of checkpoints and verification points reflects sufficient integrity and details. Using the test plan as the basis for writing test cases can ensure the correctness and effectiveness of the test cases and improve the coverage of the test cases.

[0063] Step 150: Test case management and maintenance.

[0064] The test case management and maintenance uses modules and business process tree directory structures to plan test cases; customize demand points for business processes, optimize on the basis of the test scheme of existing business processes, and then improve test cases based on the optimized test scheme; optimize on the basis of the test scheme of the corresponding business process for the addition, deletion, and modification of test cases identified during test execution, and then improve test cases based on the optimized test scheme. For test cases that need to be executed in regression testing, they are strategically selected based on the case level and the specific test execution situation. It can be seen that the present invention uses modules and business process tree directory structures to plan test cases on the one hand, customize demand points for business processes, and optimize on the basis of the test scheme of existing business processes without starting from scratch, and then improve test cases based on the optimized test scheme, which can improve the efficiency of test case design. For new employees whose test team members are updated and replaced, while improving their test case design efficiency, their test case design quality can also be improved. On the other hand, the addition, deletion, and modification of test cases identified during test execution are optimized based on the test plan of the corresponding business process, and then the test cases are improved based on the optimized test plan, so that a complete test plan and test cases for the software can always be retained, thereby improving the coverage of the test cases and ensuring the correctness and effectiveness of the test cases. On the other hand, the test scenario level is identified according to the degree to which users care about the software functions, and the test cases to be executed are strategically selected in regression testing based on the case level and the specific test execution situation, which helps to improve the efficiency and quality of test execution.

[0065] In summary:

[0066] 1. On the one hand, the present invention adopts the idea of ​​input, logic processing, and output to refine the test requirements, form business logic processing, and further analyze the test requirements in detail from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios, and refine the content or quality characteristics granularity that needs to be tested determined by the test requirements analysis into factor points, i.e., influencing factors, as the entry point for designing test cases by the black box testing method, so that the test design is comprehensive and the test case coverage is improved. At the same time, the test requirements after refinement and analysis have clear details of the business process, which can ensure the correctness and effectiveness of the test cases. On the other hand, it is not limited to the design of a certain test requirement test case, and can improve the universality of the test case design.

[0067] 2. The present invention adopts a suitable black box testing method to design verification points based on influencing factors, which can reduce the redundancy of the test cases finally formed and improve the coverage of test cases. The formed test scheme includes checkpoints and verification points. The checkpoints include business checks, interface checks, database checks, and log checks carried out by the business process. The verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios. The consideration of checkpoints and verification points reflects full integrity and details. Using the test scheme as the basis for writing test cases can ensure the correctness and effectiveness of the test cases and improve the coverage of the test cases.

[0068] 3. On the one hand, the present invention uses modules and business process tree directory structures to plan test cases, customize demand points for business processes, and optimize on the basis of the test scheme of existing business processes without starting from scratch. Then, the test cases are improved based on the optimized test scheme, which can improve the efficiency of test case design. For new employees who are replaced by test team members, while improving their test case design efficiency, they can also improve their test case design quality. On the other hand, for the addition, deletion, and modification of test cases identified in the test execution, optimization is performed on the basis of the test scheme of the corresponding business process, and then the test cases are improved based on the optimized test scheme, which can always retain a complete test scheme and test cases of the software, thereby improving the coverage adequacy of the test cases and ensuring the correctness and effectiveness of the test cases. On the other hand, the test scenario level is identified according to the degree to which the user cares about the software function, and the test cases to be executed are strategically selected according to the use case level and the specific test execution situation in the regression test, which helps to improve the test execution efficiency and quality.

[0069] The test case design framework of the present invention, the test case design framework 200 of the present invention, corresponds to the above-mentioned test case design method, and includes a business logic processing forming module 210, an influencing factor identification module 220, a test scheme forming module 230, a test case forming module 240, and a test case management and maintenance module 250.

[0070] The business logic processing module 210 is based on modular business processes and test requirements, and uses the ideas of input, logic processing, and output to refine the test requirements, forming a business process diagram, business process development-related configurations (such as parameter configuration, etc.), business process development-related interfaces, business process development-related database tables, and business process development-related logs.

[0071] The influencing factor identification module 220 further analyzes in detail the key points that affect the development of the business process from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios.

[0072] The test scheme forming module 230 uses a black box test method to design verification points based on influencing factors. The black box test method includes common boundary value equivalence class methods, scenario methods, etc. The test scheme includes checkpoints and verification points. The checkpoints include business checks, interface checks, database checks, and log checks for business processes. The verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenarios. The test scenario level is identified according to the degree to which users care about software functions. The normal scenario level is level 1, the rule constraints, abnormal scenarios, and interactive scenarios level 2, the special scenario level 3, and the interface scenario level 4. The test scheme is carried using a mind map.

[0073] The test case forming module 240 writes test cases according to the test plan, and plans the test cases using the module and business process tree directory structure; uses the basic element template of the use case number, use case title, use case level, pre-conditions, operation steps, and expected results to reflect the specific test case content, and the use case level is equivalent to the test scenario level; combines the modular business process and test requirements, expands the verification points and checkpoints in the test plan into the test case template to form a test case.

[0074] The test case management and maintenance module 250 uses the module and business process tree directory structure to plan test cases; customizes the business process requirements, optimizes the test plan of the existing business process, and then improves the test cases based on the optimized test plan; optimizes the test case addition, deletion, and modification identified during the test execution based on the test plan of the corresponding business process, and then improves the test cases based on the optimized test plan. For the test cases that need to be executed in the regression test, they are strategically selected according to the case level and the specific test execution situation.

[0075] It should be noted that the technical effects that can be achieved by the test case design framework described in the present invention can be found in the description of the test case design method above, and will not be repeated here.

[0076] The above shows and describes the basic principles, main features and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The above embodiments and descriptions only describe the principles of the present invention. The present invention may be subject to various changes and improvements without departing from the spirit and scope of the present invention. These changes and improvements fall within the scope of the present invention. The scope of protection claimed by the present invention is defined by the attached claims and their equivalents.

Claims

1. A test case design method based on modular business processes, characterized in that: Includes steps: S1. Based on modular business processes and test requirements, the idea of ​​input, logic processing, and output is used to refine the test requirements and form business logic processing; S2. Further detailed analysis from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios to identify influencing factors; S3. Design verification points based on influencing factors using black box testing methods to form a test plan; S4. Write test cases according to the test plan; S5. Test case management and maintenance.

2. The test case design method based on modular business process according to claim 1, characterized in that: The modular business process, for different software, modularizes the software from the functional dimension, such as system management, business module, statistical analysis, etc., and then sorts out the business process from the user's perspective based on each module, such as user role authority management and basic data management in the system management module. The test requirements are the content or quality characteristics that need to be tested determined by the test requirements analysis in the test planning. The business logic processing involves business process diagrams, configurations related to business process development (such as parameter configuration, etc.), interfaces related to business process development, database tables related to business process development, and logs related to business process development, which are carried out using mind maps.

3. The test case design method based on modular business process according to claim 1, characterized in that: The rule constraints, normal scenarios, abnormal scenarios, interactive scenarios, special scenarios, and interface scenario dimensions: Rules and constraints: the rules and constraints that need to be followed in carrying out business processes; Normal scenario: When the business process is carried out, data that meets the requirements is input, and after logical processing, the expected output is given; Abnormal scenario: When the business process is in progress, if data that does not meet the requirements is entered, the software will give a friendly prompt after logical processing; Interaction scenario: data related to business process development can be used as input or output for other business processes, and different channels can interact with each other to develop the same business process; Special scenarios: scenarios where the software and hardware environment in which the software runs is abnormal; Interface scenario: Each interface related to the business process has a unified interface style, correct and friendly text descriptions, friendly layout, and buttons on the interface are available and correct; The influencing factors are key points that affect the development of business processes from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios.

4. The test case design method based on modular business process according to claim 1, characterized in that: The black box testing method includes common boundary value equivalence class method, scenario method, etc. Boundary value equivalence class method: boundary value analysis uses data equal to, less than or greater than the boundary value to carry out testing. The equivalence class divides the input domain into several parts, and selects representative data in each part to carry out testing. The boundary value equivalence class method focuses on data, complements each other, and is used in combination. Scenario method: with event flow as the core, the path from a certain initial state of the software to a certain end state constitutes a use case scenario, focusing on the business process. The test plan includes checkpoints and verification points. Checkpoints include business checks, interface checks, database checks, and log checks carried out by the business process. Verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios, and the test scenario level is identified according to the degree to which users care about the software function. The normal scenario level is level 1, rule constraints, abnormal scenarios, and interaction scenarios level 2, special scenarios level 3, and interface scenarios level 4; The test plan is carried out using a mind map.

5. The test case design method based on modular business process according to claim 1, characterized in that: The test cases are written according to the test plan, and the test cases are planned using the module and business process tree directory structure; Use the use case title, use case number, prerequisites, test steps, expected results, and use case level basic element templates to reflect the specific test case content. The use case level is equivalent to the test scenario level. Combine modular business processes and test requirements, and expand the verification points and checkpoints in the test plan to the test case template to form a test case.

6. The test case design method based on modular business process according to claim 1, characterized in that: The test case management and maintenance uses modules and business process tree directory structures to plan test cases; customizes the business process requirements, optimizes the existing business process test plan, and then improves the test cases based on the optimized test plan; Optimize the test plan of the corresponding business process based on the addition, deletion, and modification of test cases identified during test execution, and then improve the test cases based on the optimized test plan; For the test cases that need to be executed in regression testing, they are selected strategically based on the case level and the specific test execution situation.

7. A test case design framework based on modular business processes, characterized by: It includes a business logic processing module, an influencing factor identification module, a test plan forming module, a test case forming module, and a test case management and maintenance module, wherein: the business logic processing module, based on modular business processes and test requirements, adopts the ideas of input, logic processing, and output to refine the test requirements, and forms a business process diagram, business process-related configurations, business process-related interfaces, business process-related database tables, and business process-related logs.

8. The test case design framework based on modular business process according to claim 7, characterized in that: The influencing factor identification module further analyzes in detail the key points that affect the development of business processes from the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios.

9. The test case design framework based on modular business process according to claim 7, characterized in that: The test scheme forming module adopts the black box test method to design verification points based on influencing factors. The black box test method includes common boundary value equivalence class method, scenario method, etc. The test scheme includes checkpoints and verification points. The checkpoints include business checks, interface checks, database checks, and log checks carried out by the business process. The verification points include test scenarios in the dimensions of rule constraints, normal scenarios, abnormal scenarios, interaction scenarios, special scenarios, and interface scenarios. The test scenario level is identified according to the degree to which users care about the software functions. The normal scenario level is level 1, the rule constraints, abnormal scenarios, and interaction scenarios are level 2, the special scenarios are level 3, and the interface scenarios are level 4.

10. The test case design framework based on modular business process according to claim 7, characterized in that: The test cases are formed into modules, test cases are written according to the test plan, and test cases are planned using the module and business process tree directory structure; The use case number, use case title, use case level, preconditions, operation steps, and expected results basic element templates are used to reflect the specific test case content. The use case level is equivalent to the test scenario level. Combined with modular business processes and test requirements, the verification points and checkpoints in the test plan are expanded to the test case template to form a test case. The test case management and maintenance module uses modules and business process tree directory structures to plan test cases. Customize the demand points of the business process, optimize the test plan of the existing business process, and then improve the test case based on the optimized test plan. Optimize the test plan of the corresponding business process based on the addition, deletion, and modification of test cases identified during test execution, and then improve the test cases based on the optimized test plan; For the test cases that need to be executed in regression testing, they are selected strategically based on the case level and the specific test execution situation.