Test case generation method and device, equipment and storage medium

Abstract

The invention provides a test case generation method and device, equipment and a storage medium. The test case generation method comprises the following steps: acquiring complaint work order data; performing duplicate removal and classification on the complaint work order data; determining target complaint work order data according to the type of the complaint work order data; and converting the target complaint work order data into a test case according to the standard case template. According to the method, the test case can be automatically generated, the workload of testers is greatly reduced, and the test efficiency is improved.

Description

Technical Field

[0001] The present invention belongs to the field of customer complaint management and test management, and in particular relates to a test case generation method and device, equipment and storage medium. Background Art

[0002] Customer complaint management is an important part of modern enterprise service management. Its process aims to effectively handle customer feedback and complaints and improve customer satisfaction and loyalty.

[0003] The typical process of current customer complaint management includes: complaint channel → information entry → automatic classification → responsibility allocation → tracking and communication → solution formulation → execution and confirmation → data analysis and reporting → continuous improvement and feedback → customer satisfaction survey → record and knowledge management. Among them, test management is a process of managing test activities to ensure that software applications are tested with high quality. The method includes organizing, controlling, and ensuring the traceability and visibility of the test process to provide high-quality software applications.

[0004] When testing, testers need to analyze complaint ticket data and generate test cases. There is a lot of complaint ticket data, which will lead to a large workload for testers. In addition, it is difficult for testers to accurately find the most important complaint ticket data from the massive complaint ticket data. How to provide a method to generate test cases based on complaint ticket data has become a top priority. Summary of the invention

[0005] The present invention provides a test case generation method and apparatus, equipment and storage medium, which can automatically generate test cases, greatly reduce the workload of testers, and improve test efficiency.

[0006] In one aspect, a method for generating a test case is provided, comprising: Obtain complaint ticket data; De-duplicate and classify complaint ticket data; Determine the target complaint ticket data based on the type of complaint ticket data; According to the standard case template, the target complaint ticket data is converted into test cases.

[0007] Optionally, obtain complaint ticket data, including: Obtain complaint ticket data that meets preset conditions in the customer service complaint ticket system, wherein the complaint ticket data includes complaint ticket data about the system, complaint ticket data about the business, and complaint ticket data about the product; under the preset conditions, the complaint ticket data is non-pending data, non-internal complaint data, and non-assistance data.

[0008] Optionally, deduplicate and classify the complaint ticket data, including: Generate a first data table, the first data table is used to store complaint work order data; Retrieve the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product in the first data table respectively, and remove the identical data in the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product respectively; The complaint work order data in the first data table are classified according to process category, function category and processing category, and stored in the second data table; process categories include general, external complaints, emergency, and switchboard complaints; function categories include value-added services, deposit business, loan business, account category, capital category, corporate business, general category, and complaint escalation; processing categories include paid, data change, system optimization, and no processing required.

[0009] Optionally, target complaint work order data is determined according to the type of complaint work order data, including: The complaint work order data in the second data table are prioritized according to their process categories, functional categories and processing categories; complaint work order data with process categories of external complaints and emergencies, or functional categories of funds and complaint upgrades, or processing categories of paid and data changes are determined as the first priority; complaint work order data with process categories of ordinary and PBX complaints, or functional categories of value-added services, deposit business, loan business, account category, corporate business, general category, or processing category of system optimization are determined as the second priority; complaint work order data with processing categories of no need to be processed are determined as the third priority; complaint work order data that meets the first priority is the target complaint work order data, complaint work order data that meets the second priority is the target complaint work order data when it is hit, and complaint work order data that meets the third priority is the target complaint work order data when the tester checks it.

[0010] Optionally, the target complaint ticket data is converted into test cases according to the standard case template, including: Complete the data mapping definition between the target complaint ticket data and the standard case template, including completing the data mapping of the system, business classification, test steps, expected test results, and prerequisites; Obtain the target complaint work order data in the second data table in turn, and fill in the main fields of the standard case template according to the data mapping relationship, and complete other fields to form a test case, and store the test case in the third data table. The test cases in the third data table are divided into system test cases, business test cases and product test cases.

[0011] Optionally, it also includes: At the beginning of the test plan, the test cases are pushed to the tester's test plan, and the tester performs tests according to the test cases in the test plan.

[0012] In another aspect, a test case generation device is provided, comprising: Acquisition module, used to obtain complaint ticket data; The processing module is used to deduplicate and classify the complaint work order data; and determine the target complaint work order data according to the type of the complaint work order data; The case generation module is used to convert the target complaint ticket data into test cases based on the standard case template.

[0013] Optionally, the processing module is used to: Generate a first data table, the first data table is used to store complaint work order data; Retrieve the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product in the first data table respectively, and remove the identical data in the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product respectively; The complaint work order data in the first data table are classified according to process category, function category and processing category, and stored in the second data table; process categories include general, external complaints, emergency, and switchboard complaints; function categories include value-added services, deposit business, loan business, account category, capital category, corporate business, general category, and complaint escalation; processing categories include paid, data change, system optimization, and no processing required.

[0014] On the other hand, an electronic device is provided, comprising the test case generation method as described above.

[0015] On the other hand, a computer-readable storage medium is provided, wherein at least one program code is stored in the computer-readable storage medium, and the program code is executed by a processor to implement the test case generation method as described in any one of the above items.

[0016] The technical solution provided by the embodiments of the present disclosure has the following beneficial effects: The present disclosure provides a method for generating a test case, which obtains a large amount of complaint work order data, removes duplicates and classifies the complaint work order data, and determines the target complaint work order data, and finally generates a test case based on a standard case template and the target complaint work order data. The method steps can save the workload of testers and improve test efficiency. In addition, by automatically analyzing the complaint work order data, the test case finally generated will more accurately point to the problem that needs to be solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to more clearly illustrate the technical solutions in the present invention or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0018] Figure 1 A flow chart of a method for generating a test case provided in an embodiment of the present disclosure; Figure 2 A structural block diagram of a test case generation device provided in an embodiment of the present disclosure; Figure 3 A structural block diagram of an electronic device provided in an embodiment of the present disclosure.

[0019] The reference numerals are as follows: 21: Acquisition module; 22: Processing module; 23: Case generation module; 24: Push module; 31: processor; 32: memory. DETAILED DESCRIPTION

[0020] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. 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.

[0021] A test plan can be defined as a document that describes the scope, methods, resources, and schedule of the testing activities. Without a complete test plan, a project may fail. Test plans are particularly important in the development of large software systems. The test goal is the most critical part of the entire test plan, which can determine whether the entire test plan can ultimately achieve its goals. At present, the most difficult aspects of determining test goals are as follows: First, unclear requirements: test goals often rely on project requirements documents, but in actual development, requirements may not be clear or complete enough, making it difficult for the test team to accurately identify the specific functions or features that need to be tested. Second, high complexity: software systems are usually complex, containing multiple modules and components, and functions are interrelated. Identifying all relevant test goals may require in-depth system understanding. Third, fast technology updates: With the development of technology, new development frameworks, tools, and methods emerge in an endless stream. Testers need to constantly learn and adapt to new technologies to ensure that they can identify test goals under the latest technologies. Fourth, user behavior diversity: users have different usage methods and habits, especially when facing users with different backgrounds and needs, it becomes difficult to identify all possible usage scenarios and their corresponding test goals. Fifth, resource constraints: When resources such as time, personnel, and budget are limited, the test team may not be able to cover all identified test targets, thus affecting the comprehensiveness of the test. Sixth, hidden defects: Some defects may not be easy to find or identify, especially those related to user interaction, which requires deeper exploration and detailed testing strategies. Seventh, test environment differences: There may be differences between the test environment and the production environment, which requires additional consideration of the impact of environmental factors on target testing when identifying targets in a specific environment. Eighth, cross-team collaboration: In large-scale projects, multiple teams are often involved in collaboration. How to effectively communicate and coordinate the identification and implementation of test targets between different teams is also a challenge.

[0022] The main solutions to the fourth, sixth, seventh and eighth difficulties are as follows: increase testing resources, introduce more testers and test rounds; promote cross-testing during the testing process; introduce quasi-production testing phase, and use the amount and type of production data after data desensitization for verification; the first and third difficulties are completely solved by resource accumulation, which wastes a certain amount of testing resources; the second difficulty, for projects with tight schedules, will increase the project duration and affect the time to go online. In addition, the first and second difficulties cannot introduce real users and real scenarios to increase the effect of test target identification and improve test quality without affecting the testing process.

[0023] Our company's test management platform has the following requirements regarding the need to consider real user differences and production scenario responsibilities for test targets during the test process: First, it should not occupy too many test resources; second, the test time should be extended; third, real user experience and real scenario data should be introduced. Therefore, using manpower or existing technology to achieve the above three requirements, the preparation difficulties are as follows: Difficulty 1, limited test resources, unable to fully consider the user scale; Difficulty 2, production scenarios require massive amounts of real data, and some scenarios will be invalid after desensitizing the data; Difficulty 3, the real user experience and scenario data testing team cannot quickly obtain and update; Based on the above three difficulties, the problem of considering real user differences and production scenario responsibilities for test targets during the test process is difficult to solve.

[0024] After the implementation of the present invention, the testing team only needs to extract data from the customer complaint work order system at regular intervals to obtain real user feedback data in real time, and obtain recommended case data during the testing process to correct the test objectives. No other environments are introduced in the testing process, the implementation difficulty is low, and the process is stable. The accumulated complaint data can complete a closed loop based on the testing process, which can quickly solve the user's intuitive needs without waiting for the demand process to advance slowly. The functional effect of the single online window can be improved and the repetitive workload can be reduced.

[0025] Figure 1 A flow chart of a method for generating a test case provided by an embodiment of the present disclosure. Figure 1 ,include: S11. Obtain complaint work order data.

[0026] In one example, step S1 includes: Obtain complaint ticket data that meets preset conditions in the customer service complaint ticket system, wherein the complaint ticket data includes complaint ticket data about the system, complaint ticket data about the business, and complaint ticket data about the product; under the preset conditions, the complaint ticket data is non-pending data, non-internal complaint data, and non-assistance data.

[0027] In the disclosed embodiment, by preliminarily classifying the complaint work order data, it is convenient for subsequent screening and test case generation. In addition, by obtaining the complaint work order data according to the preset conditions, unimportant complaint work order data can be removed, thereby ensuring that the introduced complaint work order data are all data associated with the test plan.

[0028] In the disclosed embodiment, before executing the content of step S11, the logic of connecting the data sources of the front and back systems will be unified according to the underlying data structure planning, specifically including: sorting out the underlying data classification according to the underlying data structure planning, and it is recommended to classify the data into three levels: the first level: system, a mandatory binding item, aligning the system name and code of the customer service complaint ticket and the test management platform; the second level: business, belonging to the system, a mandatory binding item; the third level: product, belonging to the system, a non-mandatory binding item. The data introduction principles will also be confirmed: Principle 1: The status in the customer service complaint ticket system is non-pending data; Principle 2: The process category in the customer service complaint ticket system is non-internal complaint data; Principle 3: The business category in the customer service complaint ticket system is non-assistance data.

[0029] S12. De-duplicate and classify complaint ticket data.

[0030] In one example, step S12 includes: The first step is to generate a first data table, which is used to store complaint work order data.

[0031] The second step is to retrieve the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product in the first data table respectively, and remove the identical data in the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product respectively.

[0032] Step 3. Classify the complaint ticket data in the first data table according to process category, function category and processing category, and store them in the second data table; process categories include general, external complaints, emergency, and switchboard complaints; function categories include value-added services, deposit business, loan business, account category, capital category, corporate business, general category, and complaint escalation; processing categories include paid, data change, system optimization, and no processing required.

[0033] In an embodiment of the present disclosure, the acquired complaint work order data is further classified according to the above-mentioned classification method, the same complaint work order data is removed, and the same type of complaint work order data is merged to avoid the generation of the same test cases when test cases are subsequently generated based on the complaint work order data.

[0034] S13. Determine target complaint work order data according to the type of complaint work order data.

[0035] In one example, step S13 includes: The complaint work order data in the second data table are prioritized according to their process categories, functional categories and processing categories; complaint work order data with process categories of external complaints and emergencies, or functional categories of funds and complaint upgrades, or processing categories of paid and data changes are determined as the first priority; complaint work order data with process categories of ordinary and PBX complaints, or functional categories of value-added services, deposit business, loan business, account category, corporate business, general category, or processing category of system optimization are determined as the second priority; complaint work order data with processing categories of no need to be processed are determined as the third priority; complaint work order data that meets the first priority is the target complaint work order data, complaint work order data that meets the second priority is the target complaint work order data when it is hit, and complaint work order data that meets the third priority is the target complaint work order data when the tester checks it.

[0036] In the disclosed embodiment, by further classification, the complaint ticket data is prioritized according to its importance, so that the most urgent problem to be solved in the current complaint ticket data can be determined.

[0037] S14. Convert the target complaint work order data into test cases according to the standard case template.

[0038] In one example, step S14 includes: The first step is to complete the data mapping definition between the target complaint work order data and the standard case template, including completing the data mapping of the system, business classification, test steps, expected test results, and prerequisites.

[0039] The second step is to obtain the target complaint work order data in the second data table in turn, and fill in the main fields of the standard case template according to the data mapping relationship, and complete other fields to form a test case, and store the test case in the third data table. The test cases in the third data table are divided into system test cases, business test cases and product test cases.

[0040] In the disclosed embodiment, the user fills in the complaint content on a complaint worksheet with a preset format. When the target complaint worksheet data is screened out, the content on the complaint worksheet can be directly filled into the standard case template by mapping, thereby generating a test case.

[0041] S15: At the beginning of the test plan, the test cases are pushed to the test plan of the tester, and the tester performs the test according to the test cases in the test plan.

[0042] The present disclosure provides a method for generating a test case, which obtains a large amount of complaint work order data, removes duplicates and classifies the complaint work order data, and determines the target complaint work order data, and finally generates a test case based on a standard case template and the target complaint work order data. The method steps can save the workload of testers and improve test efficiency. In addition, by automatically analyzing the complaint work order data, the test case finally generated will more accurately point to the problem that needs to be solved.

[0043] Figure 2 This is a structural block diagram of a test case generation device provided by an embodiment of the present disclosure. Figure 2 ,include: Acquisition module 21, used to acquire complaint work order data; The processing module 22 is used to remove duplicates and classify the complaint work order data; and determine the target complaint work order data according to the type of the complaint work order data; The case generation module 23 is used to convert the target complaint work order data into a test case according to the standard case template.

[0044] Optionally, the acquisition module 21 is used to: Obtain complaint ticket data that meets preset conditions in the customer service complaint ticket system, wherein the complaint ticket data includes complaint ticket data about the system, complaint ticket data about the business, and complaint ticket data about the product; under the preset conditions, the complaint ticket data is non-pending data, non-internal complaint data, and non-assistance data.

[0045] Optionally, the processing module 22 is used to: Generate a first data table, the first data table is used to store complaint work order data; Retrieve the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product in the first data table respectively, and remove the identical data in the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product respectively; The complaint work order data in the first data table are classified according to process category, function category and processing category, and stored in the second data table; process categories include general, external complaints, emergency, and switchboard complaints; function categories include value-added services, deposit business, loan business, account category, capital category, corporate business, general category, and complaint escalation; processing categories include paid, data change, system optimization, and no processing required.

[0046] Optionally, the processing module 22 is used to: The complaint work order data in the second data table are prioritized according to their process categories, functional categories and processing categories; complaint work order data with process categories of external complaints and emergencies, or functional categories of funds and complaint upgrades, or processing categories of paid and data changes are determined as the first priority; complaint work order data with process categories of ordinary and PBX complaints, or functional categories of value-added services, deposit business, loan business, account category, corporate business, general category, or processing category of system optimization are determined as the second priority; complaint work order data with processing categories of no need to be processed are determined as the third priority; complaint work order data that meets the first priority is the target complaint work order data, complaint work order data that meets the second priority is the target complaint work order data when it is hit, and complaint work order data that meets the third priority is the target complaint work order data when the tester checks it.

[0047] Optionally, the case generation module 23 is used to: Complete the data mapping definition between the target complaint ticket data and the standard case template, including completing the data mapping of the system, business classification, test steps, expected test results, and prerequisites; Obtain the target complaint work order data in the second data table in turn, and fill in the main fields of the standard case template according to the data mapping relationship, and complete other fields to form a test case, and store the test case in the third data table. The test cases in the third data table are divided into system test cases, business test cases and product test cases.

[0048] Optionally, the test case generation device further includes a push module 24, which is used to: At the beginning of the test plan, the test cases are pushed to the tester's test plan, and the tester performs tests according to the test cases in the test plan.

[0049] Figure 3 This is a structural block diagram of an electronic device provided by an embodiment of the present disclosure. Figure 3 , electronic devices may include Figure 2 The test case generation device generally includes a processor 31 and a memory 32 .

[0050] The processor 31 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 31 may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). The processor 31 may also include a main processor and a coprocessor, the main processor is a processor for processing data in the wake-up state, also known as a CPU (Central Processing Unit); the coprocessor is a low-power processor for processing data in the standby state. The memory 32 may include one or more computer-readable storage media, which may be non-transitory. The memory 32 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In some embodiments, the non-transitory computer-readable storage medium in the memory 32 is used to store at least one instruction, which is used to be executed by the processor 31 to implement the method for generating a test case performed by an electronic device provided in the method embodiment of the present application.

[0051] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for generating a test case, characterized in that: include: Obtain complaint ticket data; De-duplicate and classify complaint ticket data; Determine the target complaint ticket data based on the type of complaint ticket data; According to the standard case template, the target complaint ticket data is converted into test cases.

2. The method for generating a test case according to claim 1, characterized in that: Obtain complaint ticket data, including: Obtain complaint ticket data that meets preset conditions in the customer service complaint ticket system, wherein the complaint ticket data includes complaint ticket data about the system, complaint ticket data about the business, and complaint ticket data about the product; under the preset conditions, the complaint ticket data is non-pending data, non-internal complaint data, and non-assistance data.

3. The method for generating a test case according to claim 2, characterized in that: De-duplicate and classify complaint ticket data, including: Generate a first data table, the first data table is used to store complaint work order data; Retrieve the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product in the first data table respectively, and remove the identical data in the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product respectively; The complaint work order data in the first data table are classified according to process category, function category and processing category, and stored in the second data table; process categories include general, external complaints, emergency, and switchboard complaints; function categories include value-added services, deposit business, loan business, account category, capital category, corporate business, general category, and complaint escalation; processing categories include paid, data change, system optimization, and no processing required.

4. The method for generating a test case according to claim 3, characterized in that: Determine the target complaint ticket data based on the type of complaint ticket data, including: The complaint work order data in the second data table are prioritized according to their process categories, functional categories and processing categories; complaint work order data with process categories of external complaints and emergencies, or functional categories of funds and complaint upgrades, or processing categories of paid and data changes are determined as the first priority; complaint work order data with process categories of ordinary and PBX complaints, or functional categories of value-added services, deposit business, loan business, account category, corporate business, general category, or processing category of system optimization are determined as the second priority; complaint work order data with processing categories of no need to be processed are determined as the third priority; complaint work order data that meets the first priority is the target complaint work order data, complaint work order data that meets the second priority is the target complaint work order data when it is hit, and complaint work order data that meets the third priority is the target complaint work order data when the tester checks it.

5. The method for generating a test case according to claim 4, characterized in that: According to the standard case template, the target complaint ticket data is converted into test cases, including: Complete the data mapping definition between the target complaint ticket data and the standard case template, including completing the data mapping of the system, business classification, test steps, expected test results, and prerequisites; Obtain the target complaint work order data in the second data table in turn, and fill in the main fields of the standard case template according to the data mapping relationship, and complete other fields to form a test case, and store the test case in the third data table. The test cases in the third data table are divided into system test cases, business test cases and product test cases.

6. The method for generating a test case according to any one of claims 1 to 5, characterized in that: Also includes: At the beginning of the test plan, the test cases are pushed to the tester's test plan, and the tester performs tests according to the test cases in the test plan.

7. A test case generation device, characterized in that: include: Acquisition module, used to obtain complaint ticket data; Processing module, used to deduplicate and classify complaint ticket data; Determine the target complaint ticket data based on the type of complaint ticket data; The case generation module is used to convert the target complaint ticket data into test cases based on the standard case template.

8. A test case generation device according to claim 7, characterized in that: Processing modules for: Generate a first data table, the first data table is used to store complaint work order data; Retrieve the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product in the first data table respectively, and remove the identical data in the complaint work order data about the system, the complaint work order data about the business, and the complaint work order data about the product respectively; Classify the complaint work order data in the first data table according to process category, function category and processing category, and store them in the second data table; Process categories include general, external complaints, emergency, and switchboard complaints; functional categories include value-added services, deposit business, loan business, account category, capital category, corporate business, general category, and complaint escalation; processing categories include paid, data changes, system optimization, and no processing required.

9. An electronic device, characterized in that: The invention comprises a method for generating a test case as claimed in claim 7 or 8.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores at least one program code, and the program code is executed by a processor to implement the test case generation method according to any one of claims 1 to 6.

Images