Method, device, computer device and storage medium for improving test efficiency

Abstract

The application discloses a method and device for improving test efficiency, a computer device and a storage medium. The method comprises the following steps: writing test cases, setting a corresponding feature ID for each test case; obtaining each feature under the to-be-released version, adding the test case corresponding to the to-be-released version to a system test plan according to the feature number of the feature; obtaining the test case under the system test plan and the feature ID of each test case, obtaining each feature under the to-be-released version and a user story under the feature, and establishing an association relationship among the feature, the test case and the user story according to the feature ID; according to the association relationship, the test case under the same feature is circularly bound to the user story associated with the test case, and the system test plan is executed. The test case and the user story can be bound by one key, manual operation time can be saved, and the test efficiency is greatly improved.

Description

Technical Field

[0001] This application relates to the field of research and development management technology, and in particular to a method, apparatus, computer equipment, and storage medium for improving testing efficiency. Background Technology

[0002] The R&D management platform is a tool specifically developed for product development units to manage some, or even all, of the daily management tasks related to R&D activities. Within the platform, R&D tasks are categorized into objectives, features, and user stories. Objectives are the overall requirements proposed by the business stakeholders, while features are the sub-requirements broken down by various business lines to support these overall requirements. To implement these sub-requirements, developers need to create user stories under each sub-requirement, enabling developers to submit code, testers to associate test cases, and submit defects. During requirement testing, testers must first write test cases, then bind them to the corresponding user stories, and finally test and execute the test cases against the requirements. Because each user story performs a different function, and each user story requires a corresponding test case, testers need to continuously perform this process, consuming significant manpower and resulting in long overall testing times and low efficiency. Summary of the Invention

[0003] This application provides a method, apparatus, computer equipment, and storage medium to improve testing efficiency, aiming to solve the technical problems of long testing time and low testing efficiency in existing R&D management platform testing methods.

[0004] To solve the above-mentioned technical problems, the technical solution adopted in this application is as follows:

[0005] One method to improve testing efficiency includes:

[0006] Write test cases for the version to be released, and set a corresponding feature ID for each test case. The feature ID is the feature number of the feature corresponding to the test case in the version to be released.

[0007] Obtain all features of the version to be released, and add the test cases corresponding to the version to be released to the system test plan according to the feature number of the feature;

[0008] Obtain the test cases under the system test plan and the feature ID of each test case, and obtain each feature under the version to be released and the user stories under the features. Establish the association between the features, test cases and user stories based on the feature IDs.

[0009] Based on the relationships between the features, test cases, and user stories, test cases under the same feature are cyclically bound to the user stories associated with the test cases, and the system test plan is executed.

[0010] The technical solution adopted in this application embodiment also includes: before writing test cases for the version to be released, the following is also included:

[0011] Create a new version to be released, and create a system test plan based on the version number of the version to be released, and generate a system test plan name; the system test plan name includes the system name and version number.

[0012] The technical solution adopted in this application embodiment further includes: setting a corresponding feature ID for each test case specifically involves:

[0013] Add a Feature ID field to the custom attribute tag of the test case. When writing the test case, enter the feature number of the corresponding feature of the test case in the version to be released in the Feature ID field to complete the feature ID setting of the test case.

[0014] The technical solution adopted in this application embodiment further includes: obtaining test cases under the system test plan and feature IDs of each test case, obtaining various features under the version to be released and user stories under the features, and establishing the association between the features, test cases, and user stories based on the feature IDs, including:

[0015] Input the system test plan name and system name, call the test case interface according to the system test plan name and system name, parse the JSON data returned by the test case interface, obtain all test cases under the system test plan and the feature ID of each test case, and establish the association relationship between the feature and the test case according to the feature ID.

[0016] The technical solution adopted in this application embodiment further includes: obtaining test cases under the system test plan and feature IDs of each test case, obtaining various features under the version to be released and user stories under the features, and establishing the association between the features, test cases, and user stories based on the feature IDs further includes:

[0017] Obtain the version number of the version to be released based on the system test plan name, call the feature interface based on the version number to obtain all feature numbers under the version number, and call the user story interface using the feature numbers to parse the JSON data returned by the user story interface to obtain all user stories under the version number and the feature number corresponding to each user story. Establish the association between the feature, test case and user story based on the feature number.

[0018] Another technical solution adopted in this application embodiment is: a device for improving testing efficiency, comprising:

[0019] Test Case Setting Module: Used to write test cases for the version to be released, and to set a corresponding feature ID for each test case. The feature ID is the feature number of the feature corresponding to the test case in the version to be released.

[0020] Test Case Addition Module: Used to obtain each feature under the version to be released, and add the test cases corresponding to the version to be released to the system test plan according to the feature number of the feature;

[0021] Test Case Association Module: Used to obtain test cases under the system test plan and the feature ID of each test case, and to obtain each feature under the release version and the user stories under the feature, and to establish the association relationship between the feature, test case and user story based on the feature ID;

[0022] Relationship Binding Module: Based on the relationships between the features, test cases, and user stories, this module cyclically binds test cases under the same feature to user stories associated with the test cases and executes the system test plan.

[0023] The technical solution adopted in this application embodiment further includes: the test case association module obtains the test cases under the system test plan and the feature ID of each test case, and obtains each feature under the version to be released and the user stories under the features, and establishes the association relationship between the features, test cases and user stories according to the feature IDs. Specifically, this is as follows:

[0024] Input the system test plan name and system name, call the test case interface according to the system test plan name and system name, parse the JSON data returned by the test case interface, obtain all test cases under the system test plan and the feature ID of each test case, and establish the association relationship between the feature and the test case according to the feature ID.

[0025] The technical solution adopted in this application embodiment further includes: the test case association module obtains the test cases under the system test plan and the feature ID of each test case, and obtains each feature under the version to be released and the user stories under the features. Establishing the association relationship between the features, test cases and user stories according to the feature IDs further includes:

[0026] Obtain the version number of the version to be released based on the system test plan name, call the feature interface based on the version number to obtain all feature numbers under the version number, and call the user story interface using the feature numbers to parse the JSON data returned by the user story interface to obtain all user stories under the version number and the feature number corresponding to each user story. Establish the association between the feature, test case and user story based on the feature number.

[0027] Another technical solution adopted in this application embodiment is: a computer device, the computer device comprising:

[0028] Memory that stores executable program instructions;

[0029] The processor connected to the memory;

[0030] The processor calls the executable program instructions stored in the memory to execute the method for improving testing efficiency as described above.

[0031] Another technical solution adopted in this application embodiment is: a storage medium storing processor-executable program instructions, the program instructions being used to execute the above-mentioned method for improving testing efficiency.

[0032] The method, apparatus, computer device, and storage medium for improving testing efficiency in this application embodiment set a feature ID consistent with the feature number in the test case, establishes an association between the feature and the test case based on the feature ID, and establishes an association between the feature, test case, and user story of the version to be released based on the feature number, thereby completing the binding of test cases and user stories with one click, saving manual operation time and greatly improving testing efficiency. Attached Figure Description

[0033] Figure 1 This is a flowchart illustrating the method for improving testing efficiency according to the first embodiment of this application;

[0034] Figure 2 This is a flowchart illustrating a method for improving testing efficiency according to a second embodiment of this application;

[0035] Figure 3 This is a schematic diagram of the structure of the device for improving testing efficiency according to an embodiment of this application;

[0036] Figure 4 This is a schematic diagram of the computer device structure according to an embodiment of this application;

[0037] Figure 5 This is a schematic diagram of the storage medium structure according to an embodiment of this application. Detailed Implementation

[0038] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0039] The terms "first," "second," and "third" in this application are for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified. All directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of this application are only used to explain the relative positional relationships and movements between components in a specific orientation (as shown in the figures). If the specific orientation changes, the directional indications also change accordingly. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0040] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0041] Please see Figure 1 This is a flowchart illustrating a method for improving testing efficiency according to the first embodiment of this application. The method for improving testing efficiency according to the first embodiment of this application includes the following steps:

[0042] S100: Write test cases for the version to be released, and set a corresponding feature ID for each test case. The feature ID is the feature number of the feature corresponding to the test case in the version to be released.

[0043] S110: Obtain each feature under the version to be released, and add the test cases corresponding to the version to be released to the system test plan according to the feature number of the feature;

[0044] S120: Obtain the test cases under the system test plan and the feature ID of each test case, and obtain each feature under the version to be released and the user stories under the features, and establish the association between the features, test cases and user stories according to the feature ID;

[0045] S130: Based on the relationship between the features, test cases, and user stories, bind test cases under the same feature to user stories associated with the test cases in a loop, and execute the system test plan.

[0046] Based on the above, the method for improving testing efficiency in the first embodiment of this application sets a feature ID that is consistent with the feature number in the test case, and establishes the association between the features of the release version, test cases and user stories based on the feature ID, thereby completing the binding of test cases and user stories with one click, which can save manual operation time and greatly improve testing efficiency.

[0047] Please see Figure 2 This is a flowchart illustrating a method for improving testing efficiency according to a second embodiment of this application. The method for improving testing efficiency according to a second embodiment of this application includes the following steps:

[0048] S200: Create a new version to be released, create a system test plan based on the version number of the version to be released, and generate a system test plan name;

[0049] In this step, the system test plan name is generated by combining the system name and version number. For example, the generated system test plan name is EHIS-POS3.29.0, where EHIS-POS is the system name and 3.29.0 is the version number.

[0050] S210: Write test cases and set a corresponding feature ID for each test case, wherein the feature ID is the feature number of the feature corresponding to the test case in the version to be released;

[0051] In this step, a feature ID field is added to the custom attribute tag of the test case. When writing the test case, the feature ID field is entered to show the feature number of the corresponding feature in the version to be released, thus completing the setting of the test case feature ID.

[0052] S220: Obtain all features of the version to be released, and add the test cases involved in the version to be released to the system test plan according to the feature number;

[0053] In this step, since the test cases are set with feature IDs that are consistent with the feature numbers, the system test plan establishes a relationship between the features in the version to be released and the test cases under the features.

[0054] S230: Create user stories under the various features of the release version;

[0055] In this step, it can be understood that the user story created under each feature corresponds to the feature number of that feature. Since the test case is set with a feature ID that is consistent with the feature number, a relationship is established between the features under the release version, the user stories under the same feature, and the test cases.

[0056] S240: Call the test case interface according to the system test plan name, obtain the test cases under the system test plan, read the feature ID of each test case, and establish the association between the feature and the test case according to the feature ID;

[0057] In this step, the tester enters the system test plan name and system name on the associated test case page, such as EHIS-POS3.29.0 and EHIS-POS. Based on the system test plan name and system name, the test case interface for improving testing efficiency is called, and the JSON (JavaScript Object Notation) data returned by the test case interface is parsed to obtain all test cases under the system test plan and the feature ID of each test case, which are then stored in a map. For example, if the obtained test cases and feature IDs are: EHIS-POS#12345 = HLW-GXXB#7125, EHIS-POS#12346 = HLW-GXXB#7125, it means that the two test cases EHIS-POS#12345 and EHIS-POS#12346 both correspond to the feature with feature number HLW-GXXB#7125.

[0058] S250: Obtain the version number based on the system test plan name, obtain the features and user stories under the release version based on the version number, and establish the relationship between the features, test cases and user stories of the release version based on the feature number;

[0059] In this step, the version number is extracted from the system test plan name. For example, in the system test plan name EHIS-POS3.29.0, the extracted version number is 3.29.0. Based on this version number, the feature interface of the R&D management platform is called to obtain all feature numbers under this version number. Then, the feature numbers are used to call the user story interface of the R&D management platform. The JSON data returned by the user story interface is parsed to obtain all user stories under this version number and the feature number corresponding to each user story, and stored in a map. It's understandable that the JSON data returned by the user story interface contains a `parent` field (pointing to the parent process), which corresponds to the feature to which the user story belongs. For example, if the obtained user story and feature number are: EHIS-NBS#123 = HLW-GXXB#7125, EHIS-NBS#124 = HLW-GXXB#7125, it means that the feature number corresponding to the two user stories EHIS-NBS#123 and EHIS-NBS#124 is HLW-GXXB#7125. The association between features, test cases, and user stories is established based on this feature number. Taking the above data as an example, EHIS-POS#12345 = EHIS-NBS#123, EHIS-POS#12345 = EHIS-NBS#124, EHIS-POS#12346 = EHIS-NBS#123, EHIS-POS#12346 = EHIS-NBS#124, thus ensuring that all test cases under the same feature correspond one-to-one with user stories.

[0060] S260: Based on the relationships between the features, test cases, and user stories of the release, test cases under the same feature are cyclically bound to the user stories associated with that test case;

[0061] In this step, after obtaining the relationship between features, test cases, and user stories, the test cases under a feature are bound to the associated user stories by calling the interface of the R&D management platform. This can greatly reduce the manual operation of testers and significantly improve testing efficiency.

[0062] S270: After binding all user stories and test cases, execute the system test plan.

[0063] Based on the above, the method for improving testing efficiency in the second embodiment of this application sets a feature ID that is consistent with the feature number in the test case, establishes an association between the feature and the test case based on the feature ID, and establishes an association between the feature, test case and user story of the version to be released based on the feature number, thereby completing the binding of test cases and user stories with one click, saving manual operation time and greatly improving testing efficiency.

[0064] In an alternative implementation, the results of the method for improving testing efficiency may also be uploaded to the blockchain.

[0065] Specifically, based on the results of the method for improving testing efficiency, corresponding digest information is obtained. More specifically, the digest information is obtained by hashing the results of the method, for example, using the SHA256 algorithm. Uploading the digest information to the blockchain ensures its security and fairness to users. Users can download the digest information from the blockchain to verify whether the results of the method for improving testing efficiency have been tampered with. The blockchain referred to in this example is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and encryption algorithms. A blockchain is essentially a decentralized database, a chain of data blocks linked using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and generate the next block. A blockchain can include a blockchain underlying platform, a platform product service layer, and an application service layer.

[0066] Please see Figure 3 This is a schematic diagram of the structure of a device for improving testing efficiency according to an embodiment of this application. The device 40 for improving testing efficiency according to an embodiment of this application includes:

[0067] Test Case Setting Module 41: Used to write test cases for the version to be released, and to set a corresponding feature ID for each test case. The feature ID is the feature number of the feature corresponding to the test case in the version to be released. Specifically, by adding a feature ID field to the custom attribute tag of the test case, when writing the test case, the feature number of the feature corresponding to the test case in the version to be released is entered in the feature ID field to complete the setting of the test case feature ID.

[0068] Test Case Addition Module 42: Used to obtain each feature under the version to be released, and add the test cases corresponding to the version to be released to the system test plan according to the feature number of the feature;

[0069] Test Case Association Module 43: Used to obtain test cases under the system test plan and the feature ID of each test case, and to obtain each feature under the release version and the user stories under the features, and to establish the association relationship between the features, test cases, and user stories based on the feature IDs; wherein, the test case association module obtains test cases under the system test plan and the feature ID of each test case, and obtains each feature under the release version and the user stories under the features, and establishes the association relationship between the features, test cases, and user stories based on the feature IDs, including: inputting the system test plan name and system name, calling the test case interface based on the system test plan name and system name, parsing the JSON data returned by the test case interface, obtaining all test cases under the system test plan and the feature ID of each test case, and establishing the association relationship between the features and test cases based on the feature IDs; specifically, testers input the system test plan name and system name on the associated test case page, such as EHIS-POS3.29.0, EHIS-POS, call the test case interface to improve testing efficiency based on the system test plan name and system name, and parse the JSON (JavaScript) returned by the test case interface. This involves using ObjectNotation (JS object notation) data to retrieve all test cases under the system's test plan, along with the feature ID of each test case, and storing them in a map. For example, if the retrieved test cases and feature IDs are: EHIS-POS#12345 = HLW-GXXB#7125, EHIS-POS#12346 = HLW-GXXB#7125, it means that the two test cases EHIS-POS#12345 and EHIS-POS#12346 both correspond to the feature with feature ID HLW-GXXB#7125.

[0070] The test case association module obtains test cases and feature IDs for each test case under the system test plan, and obtains various features and user stories under the release version. Establishing the association between features, test cases, and user stories based on the feature IDs also includes: obtaining the version number of the release version based on the system test plan name; calling the feature interface based on the version number to obtain all feature numbers under the version number; using the feature numbers to call the user story interface; parsing the JSON data returned by the user story interface to obtain all user stories under the version number and the feature number corresponding to each user story; and establishing the association between features, test cases, and user stories based on the feature numbers. Specifically, by extracting the version number from the system test plan name (e.g., in the system test plan name EHIS-POS3.29.0, the extracted version number is 3.29.0), calling the feature interface of the R&D management platform based on this version number to obtain all feature numbers under this version number, and using the feature numbers to call the user story interface of the R&D management platform to parse the JSON data returned by the user story interface to obtain all user stories under this version number and the feature number corresponding to each user story, and storing them in a map. It's understandable that the JSON data returned by the user story interface contains a `parent` field (pointing to the parent process), which corresponds to the feature to which the user story belongs. For example, if the obtained user story and feature number are: EHIS-NBS#123 = HLW-GXXB#7125, EHIS-NBS#124 = HLW-GXXB#7125, it means that the feature number corresponding to the two user stories EHIS-NBS#123 and EHIS-NBS#124 is HLW-GXXB#7125. The association between features, test cases, and user stories is established based on this feature number. Taking the above data as an example, EHIS-POS#12345 = EHIS-NBS#123, EHIS-POS#12345 = EHIS-NBS#124, EHIS-POS#12346 = EHIS-NBS#123, EHIS-POS#12346 = EHIS-NBS#124, thus ensuring that all test cases under the same feature correspond one-to-one with user stories.

[0071] Relationship binding module 44: is used to cyclically bind test cases under the same feature to user stories associated with the test cases based on the relationship between the features, test cases and user stories, and execute the system test plan.

[0072] The apparatus for improving testing efficiency in this application sets a feature ID that is consistent with the feature number in the test case, establishes an association between the feature and the test case based on the feature ID, and establishes an association between the feature, test case and user story of the version to be released based on the feature number, thereby completing the binding of test cases and user stories with one click, saving manual operation time and greatly improving testing efficiency.

[0073] Please see Figure 4 This is a schematic diagram of a computer device structure according to an embodiment of this application. The computer device 50 includes:

[0074] Memory 51 storing executable program instructions;

[0075] Processor 52 connected to memory 51;

[0076] The processor 52 is used to call the executable program instructions stored in the memory 51 and perform the following steps: write test cases for the version to be released, set a corresponding feature ID for each test case, the feature ID being the feature number of the test case corresponding to the feature in the version to be released; obtain each feature in the version to be released, and add the test cases corresponding to the version to be released to the system test plan according to the feature number of the feature; obtain the test cases and the feature ID of each test case in the system test plan, and obtain each feature in the version to be released and the user stories under the feature, and establish the association relationship between the feature, test cases and user stories according to the feature ID; according to the association relationship between the feature, test cases and user stories, bind the test cases under the same feature to the user stories associated with the test cases in a loop, and execute the system test plan.

[0077] The processor 52 can also be referred to as a CPU (Central Processing Unit). The processor 52 may be an integrated circuit chip with signal processing capabilities. The processor 52 can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor.

[0078] The computer device in this application sets a feature ID that is consistent with the feature number in the test case, establishes an association between the feature and the test case based on the feature ID, and establishes an association between the feature, test case and user story of the version to be released based on the feature number, thereby completing the binding of test cases and user stories with one click, saving manual operation time and greatly improving testing efficiency.

[0079] Please see Figure 5 , Figure 5 This is a schematic diagram of the structure of the storage medium according to an embodiment of this application. The storage medium of this embodiment stores program instructions 61 capable of implementing the following steps: writing test cases for the version to be released, setting a corresponding feature ID for each test case, where the feature ID is the feature number of the feature corresponding to the test case in the version to be released; obtaining each feature in the version to be released, adding the test cases corresponding to the version to be released to the system test plan according to the feature number of the feature; obtaining the test cases and the feature ID of each test case in the system test plan, and obtaining each feature in the version to be released and the user stories under the feature, establishing the association relationship between the feature, test cases, and user stories according to the feature ID; and, according to the association relationship between the feature, test cases, and user stories, cyclically binding test cases under the same feature to the user stories associated with the test cases, and executing the system test plan. The program instructions 61 can be stored in the storage medium in the form of a software product, including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of various embodiments of this application. The aforementioned storage media include: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program instructions, or computer devices such as computers, servers, mobile phones, and tablets. Servers can be standalone servers or cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0080] The storage medium in this application sets a feature ID that is consistent with the feature number in the test case, establishes an association between the feature and the test case based on the feature ID, and establishes an association between the feature, test case and user story of the version to be released based on the feature number, thereby completing the binding of test cases and user stories with one click, which can save manual operation time and greatly improve testing efficiency.

[0081] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, apparatuses, or units, and may be electrical, mechanical, or other forms.

[0082] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units. The above are merely embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made based on the description and drawings of this application, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method for improving testing efficiency, characterized in that, include: Write test cases for the version to be released, and set a corresponding feature ID for each test case. The feature ID is the feature number of the feature corresponding to the test case in the version to be released. Obtain all features of the version to be released, and add the test cases corresponding to the version to be released to the system test plan according to the feature number of the feature; Obtain the test cases under the system test plan and the feature ID of each test case, and obtain the features under the release version and the user stories under the features. Establish the association between the features, test cases, and user stories based on the feature IDs, including: Input the system test plan name and system name, call the test case interface according to the system test plan name and system name, parse the JSON data returned by the test case interface, obtain all test cases under the system test plan and the feature ID of each test case, and establish the association between the feature and the test case according to the feature ID; Obtain the version number of the version to be released based on the system test plan name, call the feature interface based on the version number to obtain all feature numbers under the version number, and call the user story interface using the feature numbers to parse the JSON data returned by the user story interface to obtain all user stories under the version number and the feature number corresponding to each user story. Establish the association between the feature, test case and user story based on the feature number. Based on the relationships between the features, test cases, and user stories, test cases under the same feature are cyclically bound to the user stories associated with the test cases, and the system test plan is executed.

2. The method for improving testing efficiency according to claim 1, characterized in that, Before writing test cases for the release version, the following also applies: Create a new version to be released, and create a system test plan based on the version number of the version to be released, and generate a system test plan name; the system test plan name includes the system name and version number.

3. The method for improving testing efficiency according to claim 1 or 2, characterized in that, The specific steps for setting a corresponding feature ID for each test case are as follows: Add a Feature ID field to the custom attribute tag of the test case. When writing the test case, enter the feature number of the corresponding feature of the test case in the version to be released in the Feature ID field to complete the feature ID setting of the test case.

4. A device for improving testing efficiency, characterized in that, include: Test Case Setting Module: Used to write test cases for the version to be released, and to set a corresponding feature ID for each test case. The feature ID is the feature number of the feature corresponding to the test case in the version to be released. Test Case Addition Module: Used to obtain each feature under the version to be released, and add the test cases corresponding to the version to be released to the system test plan according to the feature number of the feature; Test Case Association Module: Used to obtain test cases under the system test plan and the feature ID of each test case, and to obtain each feature under the release version and the user stories under the feature, and to establish the association relationship between the feature, test case and user story based on the feature ID; The test case association module obtains the test cases under the system test plan and the feature ID of each test case, and obtains each feature under the release version and the user stories under the features. The association relationship between the features, test cases, and user stories is established based on the feature IDs as follows: Input the system test plan name and system name, call the test case interface according to the system test plan name and system name, parse the JSON data returned by the test case interface, obtain all test cases under the system test plan and the feature ID of each test case, and establish the association between the feature and the test case according to the feature ID; Obtain the version number of the version to be released based on the system test plan name, call the feature interface based on the version number to obtain all feature numbers under the version number, and call the user story interface using the feature numbers to parse the JSON data returned by the user story interface to obtain all user stories under the version number and the feature number corresponding to each user story. Establish the association between the feature, test case and user story based on the feature number. Relationship Binding Module: Based on the relationships between the features, test cases, and user stories, this module cyclically binds test cases under the same feature to user stories associated with the test cases and executes the system test plan.

5. A computer device, characterized in that, The computer device includes: A memory that stores executable program instructions; The processor connected to the memory; The processor invokes the executable program instructions stored in the memory to execute the method for improving testing efficiency as described in any one of claims 1-3.

6. A storage medium storing processor-executable program instructions, characterized in that, The program instructions are used to execute the method for improving testing efficiency as described in any one of claims 1 to 3.

Images