Static data testing method and system based on case driving
Through the use case-driven static data testing method, static testing is carried out for specific test scenarios, which solves the problem of insufficient test coverage in the existing technology and achieves more efficient and accurate testing.
Patent Information
- Application Number
- CN202411640183.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-15
- Publication Date
- 2025-03-21
AI Technical Summary
The existing static data testing methods lack review for specific test scenarios, and insufficient test coverage, which affects testing efficiency and accuracy.
The static data testing method based on use case-driven is adopted, and the main program of the test system is run through the basic framework module, the display module is initialized, and the test case information corresponding to the target test item selected by the user is obtained, and sent to the core processing module for static testing.
It improves the reusability of data tests with the same logic between different projects, reduces development time, and improves the targetedness, efficiency and accuracy of testing.
Smart Images

Figure CN119669050A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of static data testing, and in particular to a static data testing method and system based on use case driving. Background Art
[0002] CBTC systems and vehicle-to-vehicle systems contain a large amount of data, and the logic between these data is complex. White-box testing of software focuses on software functionality. Before the white-box phase, static logic checks on the data to verify that the logic inputs are compatible with the current software can reduce bug rates during white-box testing, shorten regression time, improve testing efficiency, and conserve resources. Existing static data testing methods perform indiscriminate analysis of the entire codebase, lacking specific review scenarios and resulting in insufficient test coverage, which impacts test efficiency and accuracy. Summary of the Invention
[0003] The present disclosure provides a static data testing method and system, device, and storage medium based on use case driving.
[0004] According to a first aspect of the present disclosure, a use case-driven static data testing method is provided. The method comprises:
[0005] The basic framework module runs the basic functions of the test system main program and loads other modules;
[0006] The display module is initialized to display the target test items and receive a user's check operation on the target test items;
[0007] The basic framework module obtains the test case information corresponding to the target test item selected by the user from the standard test case template, obtains the corresponding test case from the test case loading module based on the test case information, and sends it to the core processing module;
[0008] The core processing module performs static testing on the test data in the test case, obtains the test results and sends them to the display module through the basic framework module.
[0009] In some implementations of the first aspect, the test case information includes:
[0010] Script identification, script header information, script grouping, running interface information, configuration information and running condition information.
[0011] In some implementations of the first aspect, obtaining a corresponding test case from a test case loading module according to the test case information includes:
[0012] Obtain the script case corresponding to the script identifier from the test case loading module according to the script identifier;
[0013] Determine the test data in the script use case according to the script header information;
[0014] Determine the group where the script use case is located according to the script grouping;
[0015] Determine the running condition of the script use case according to the running interface information and the running condition information;
[0016] Determine configuration information of the script use case according to the configuration information;
[0017] Obtain the corresponding test cases based on the script cases with determined test data, grouping, running conditions and configuration information.
[0018] In some implementations of the first aspect, performing a static test on the test data in the test case includes:
[0019] Load the configuration data of the test case according to the configuration information in the test case information;
[0020] If the operating condition information satisfies the static test environment, the single point data check array corresponding to each test point in the test data of the test case is initialized according to the script header information, a static logic point test is performed on each test point, and the test results are stored in the corresponding initialized single point data check array;
[0021] A two-dimensional array is generated based on each single-point data inspection array storing the test results, and the final test results of the test data are represented by the two-dimensional array.
[0022] In some implementations of the first aspect, performing a static logic point test on each test point and storing the test result in a corresponding initialized single-point data check array includes:
[0023] Perform static logic point testing on the elements in each test point according to the preset logic point checking rules;
[0024] The test results of the elements in each test point are stored in the corresponding position of the initialized single point data check array;
[0025] Perform logical operations on the test results of each element in each test point, obtain the comprehensive test results corresponding to each test point, and store them in the last item of the corresponding initialized single-point data check array.
[0026] In some implementations of the first aspect, the method further includes:
[0027] The core processing module obtains the script running status and exception handling information during the static test process, and sends the script running status and exception handling information to the display module through the basic framework module.
[0028] In some implementations of the first aspect, the method further includes:
[0029] When the export report button of the display module is triggered, the test report generation module generates and exports a corresponding test report according to the test results, script running status and exception handling information.
[0030] According to a second aspect of the present disclosure, a use case-driven static data testing system is provided. The testing system includes:
[0031] A core processing module, a standard test case template, a test case loading module, a basic framework module and a display module connected in sequence; wherein the core processing module is also connected to the basic framework module;
[0032] The basic framework module is used to run the basic functions of the test system main program and load other modules. It is also used to obtain the test case information corresponding to the target test item selected by the user from the standard test case template, obtain the corresponding test case from the test case loading module based on the test case information, and send it to the core processing module;
[0033] A core processing module is used to perform static testing on the test data in the test case, obtain the test results and send them to the display module through the basic framework module;
[0034] A display module is used to initialize so as to display target test items and receive a user's check operation on the target test items; and is also used to display test results;
[0035] Standard test case template, used to store test case information corresponding to the target test item;
[0036] The test case loading module is used to store the test cases corresponding to the target test items.
[0037] In some implementations of the second aspect, the core processing module is further configured to obtain the script running status and exception handling information during the static test process, and send the script running status and exception handling information to the display module through the basic framework module.
[0038] In some implementations of the second aspect, the system further includes:
[0039] A test report generation module connected to the display module; wherein,
[0040] The test report generation module is used to generate and export a corresponding test report according to the test results, script running status and exception handling information when the export report button of the display module is triggered.
[0041] According to a third aspect of the present disclosure, an electronic device is provided. The electronic device includes: at least one processor; and a memory communicatively connected to the at least one processor; the memory storing instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method described above.
[0042] According to a fourth aspect of the present disclosure, a non-transitory computer-readable storage medium storing computer instructions is provided, where the computer instructions are used to cause a computer to execute the method described above.
[0043] In the present disclosure, the basic framework module runs the basic functions of the test system main program and loads other modules; the display module is initialized to display the target test items and receive the user's check operation on the target test items; the basic framework module obtains the test case information corresponding to the target test items checked by the user from the standard test case template, obtains the corresponding test case from the test case loading module based on the test case information, and sends it to the core processing module; the core processing module performs static testing on the test data in the test case, obtains the test results, and sends them to the display module through the basic framework module. In this way, the reusability of data testing of the same logic between different projects can be improved, development time can be reduced, and the test targeting, efficiency, and accuracy can be improved.
[0044] It should be understood that the contents described in the Summary of the Invention section are not intended to limit the key or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0045] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. The accompanying drawings are provided for a better understanding of the present disclosure and do not constitute a limitation of the present disclosure. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, among which:
[0046] Figure 1 A flowchart of a static data testing method based on use case drive provided by an embodiment of the present disclosure is shown;
[0047] Figure 2 A structural diagram of a use case driven static data testing system provided by an embodiment of the present disclosure is shown;
[0048] Figure 3 A block diagram of an exemplary electronic device capable of implementing embodiments of the present disclosure is shown. DETAILED DESCRIPTION
[0049] To make the purpose, technical solutions, and advantages of the embodiments of the present disclosure more clear, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts are within the scope of protection of the present disclosure.
[0050] In this document, the term "and / or" simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.
[0051] In response to the problems arising from the background technology, the embodiments of the present disclosure provide a static data testing method and system based on use case driving. Specifically, the basic framework module runs the basic functions of the test system main program and loads other modules; the display module is initialized to display the target test items and receive the user's check operation on the target test items; the basic framework module obtains the test case information corresponding to the target test items checked by the user from the standard test case template, obtains the corresponding test case from the test case loading module according to the test case information, and sends it to the core processing module; the core processing module performs static testing on the test data in the test case, obtains the test results and sends them to the display module through the basic framework module. In this way, the reusability of data testing of the same logic between different projects can be improved, development time can be reduced, and the test targeting, efficiency and accuracy can be improved.
[0052] The following describes in detail the use case driven static data testing method and system provided by the embodiments of the present disclosure through specific embodiments in conjunction with the accompanying drawings.
[0053] Figure 1 A flowchart of a use case driven static data testing method provided by an embodiment of the present disclosure is shown. The method 100 includes the following steps:
[0054] S110, the basic framework module runs the basic functions of the test system main program and loads other modules.
[0055] S120: The display module is initialized to display the target test items and receive a user's check operation on the target test items.
[0056] In some embodiments, the target test items include alarm data checking, system parameter and fixed value checking.
[0057] S130, the basic framework module obtains the test case information corresponding to the target test item selected by the user from the standard test case template, obtains the corresponding test case from the test case loading module according to the test case information, and sends it to the core processing module.
[0058] In some embodiments, the test case information includes:
[0059] Script identification, script header information, script grouping, running interface information, configuration information and running condition information;
[0060] Furthermore, the script header information includes basic information of the test case and test data in the test case.
[0061] In some embodiments, obtaining a corresponding test case from a test case loading module according to the test case information includes:
[0062] Obtain the script case corresponding to the script identifier from the test case loading module according to the script identifier;
[0063] Determine the test data in the script use case according to the script header information;
[0064] Determine the group where the script use case is located according to the script grouping;
[0065] Determine the running condition of the script use case according to the running interface information and the running condition information;
[0066] Determine the configuration information of the script use case according to the configuration information, for example, identify the +json data structure in the configuration information and make it the configuration information of the script use case;
[0067] Obtain the corresponding test cases based on the script use cases with determined test data, grouping, running conditions and configuration information;
[0068] Furthermore, according to the script use cases with determined test data, grouping, operating conditions and configuration information, a binary search iterative algorithm is used to generate corresponding test cases.
[0069] S140, the core processing module performs a static test on the test data in the test case, obtains the test result, and sends it to the display module through the basic framework module.
[0070] In some embodiments, performing static testing on the test data in the test case includes:
[0071] Load the configuration data of the test case according to the configuration information in the test case information;
[0072] If the operating condition information satisfies the static test environment, the single point data check array corresponding to each test point in the test data of the test case is initialized according to the script header information, a static logic point test is performed on each test point, and the test results are stored in the corresponding initialized single point data check array;
[0073] Generating a two-dimensional array based on each single-point data inspection array storing the test results, and using the two-dimensional array to represent the final test results of the test data;
[0074] Furthermore, a static logic point test is performed on each test point and the test results are stored in the corresponding initialized single point data check array, including:
[0075] Perform static logic point testing on the elements in each test point according to the preset logic point checking rules;
[0076] The test results of the elements in each test point are stored in the corresponding position of the initialized single point data check array;
[0077] Perform logical operations on the test results of each element in each test point, obtain the comprehensive test results corresponding to each test point, and store them in the last item of the corresponding initialized single-point data check array;
[0078] For example, there are three test points in a test case, namely test point 1, test point 2, and test point 3. The single-point data check arrays corresponding to these three test points are initialized according to the script header information. Then, static logic point tests are performed on these three test points and the test results are stored in the initialized single-point data check arrays corresponding to the test points. Taking test point 1 with 5 elements and the array consisting of 5 elements as [1,2,3,4,5] as an example, how static logic point tests are performed on each test point is further explained:
[0079] The initialized single-point data check array corresponding to test point 1 is ['','','','','','']. According to the preset logic point check rules, static logic point tests are performed on the elements in the array [1,2,3,4,5]. Assuming that the test results are element 1 test success, element 2 test success, element 3 test success, element 4 test success, and element 2 test failure, then according to the logical operation rules, the comprehensive test result of the array [1,2,3,4,5] is test failure. The above test results are stored in the array ['','','','','',''] as [element 1 test success, element 2 test success, element 3 test success, element 4 test failure, comprehensive test result failure].
[0080] In some embodiments, when static testing is performed on the test data in the test case, special characters are used to identify abnormal test results, for example, "@invalid" indicates that the test result is invalid.
[0081] In some embodiments, the method 100 further includes:
[0082] The core processing module obtains the script running status and exception handling information during the static test process, and sends the script running status and exception handling information to the display module through the basic framework module;
[0083] Furthermore, the display module will also display script header information and script grouping.
[0084] In some embodiments, the method 100 further includes:
[0085] When the export report button of the display module is triggered, the test report generation module generates and exports the corresponding test report according to the test results, script running status and exception handling information;
[0086] Furthermore, the test report is generally an Excel table, the header of which contains the script header information. In the Excel table, some information that needs to be reminded of the user's attention is marked with color or font. For example, in the Excel table, the test points where the test results fail are highlighted in bold font, such as the test results of test points 1 to test points 3 in the test case shown in Table 1.
[0087] Table 1
[0088]
[0089] According to an embodiment of the present disclosure, the basic framework module runs the basic functions of the test system main program and loads other modules; the display module is initialized to display the target test items and receive the user's check operation on the target test items; the basic framework module obtains the test case information corresponding to the target test items checked by the user from the standard test case template, obtains the corresponding test case from the test case loading module based on the test case information, and sends it to the core processing module; the core processing module performs static testing on the test data in the test case, obtains the test results, and sends them to the display module through the basic framework module. In this way, the reusability of data testing of the same logic between different projects can be improved, development time can be reduced, and the test targeting, efficiency, and accuracy can be improved.
[0090] It should be noted that for the aforementioned method embodiments, for simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present disclosure is not limited by the order of the actions described, because according to the present disclosure, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present disclosure.
[0091] The above is an introduction to the method embodiment. The following is a further explanation of the solution disclosed in the present disclosure through an apparatus embodiment.
[0092] Figure 2 The following is a structural diagram of a use case driven static data testing system provided by an embodiment of the present disclosure. The testing system 200 includes:
[0093] The core processing module 210, the standard test case template 220, the test case loading module 230, the basic framework module 240 and the display module 250 are connected in sequence; wherein the core processing module 210 is also connected to the basic framework module 240;
[0094] The core processing module 210 is used to perform static testing on the test data in the test case, obtain the test results and send them to the display module through the basic framework module.
[0095] In some embodiments, the core processing module 210 is specifically configured to:
[0096] Performing static testing on the test data in the test case, including:
[0097] Load the configuration data of the test case according to the configuration information in the test case information;
[0098] If the operating condition information satisfies the static test environment, the single point data check array corresponding to each test point in the test data of the test case is initialized according to the script header information, a static logic point test is performed on each test point, and the test results are stored in the corresponding initialized single point data check array;
[0099] A two-dimensional array is generated based on each single-point data inspection array storing the test results, and the final test results of the test data are represented by the two-dimensional array.
[0100] In some embodiments, the core processing module 210 is further configured to:
[0101] Perform static logic point tests on each test point and store the test results in the corresponding initialized single point data check array, including:
[0102] Perform static logic point testing on the elements in each test point according to the preset logic point checking rules;
[0103] The test results of the elements in each test point are stored in the corresponding position of the initialized single point data check array;
[0104] Perform logical operations on the test results of each element in each test point, obtain the comprehensive test results corresponding to each test point, and store them in the last item of the corresponding initialized single-point data check array.
[0105] In some embodiments, the core processing module 210 is further configured to:
[0106] The script running status and exception handling information during the static test process are obtained, and the script running status and exception handling information are sent to the display module through the basic framework module.
[0107] The standard test case template 220 is used to store the test case information corresponding to the target test item.
[0108] In some embodiments, the standard test case template 220 is specifically used to:
[0109] Test case information, including:
[0110] Script identification, script header information, script grouping, running interface information, configuration information and running condition information.
[0111] The test case loading module 230 is used to store the test cases corresponding to the target test items.
[0112] The basic framework module 240 is used to run the basic functions of the test system main program and load other modules; it is also used to obtain the test case information corresponding to the target test item checked by the user from the standard test case template, obtain the corresponding test case from the test case loading module according to the test case information, and send it to the core processing module.
[0113] In some embodiments, the basic framework module 240 is specifically configured to:
[0114] Obtaining a corresponding test case from a test case loading module according to the test case information includes:
[0115] Obtain the script case corresponding to the script identifier from the test case loading module according to the script identifier;
[0116] Determine the test data in the script use case according to the script header information;
[0117] Determine the group where the script use case is located according to the script grouping;
[0118] Determine the running condition of the script use case according to the running interface information and the running condition information;
[0119] Determine configuration information of the script use case according to the configuration information;
[0120] Obtain the corresponding test cases based on the script cases with determined test data, grouping, running conditions and configuration information.
[0121] The display module 250 is used to perform initialization to display target test items and receive a user's check operation on the target test items; and is also used to display test results.
[0122] In some embodiments, the test system 200 further includes:
[0123] A test report generating module 260 connected to the display module; wherein,
[0124] The test report generation module 260 is used to generate and export a corresponding test report according to the test results, script running status and exception handling information when the export report button of the display module is triggered.
[0125] It is understandable that Figure 2 Each module / unit in the test system 200 shown has the function of implementing each step in the detection method 100 provided in the embodiment of the present disclosure and can achieve its corresponding technical effect. For the sake of brevity, it will not be described in detail here.
[0126] Figure 3 A block diagram of an exemplary electronic device capable of implementing embodiments of the present disclosure is shown. Electronic device 300 is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. Electronic device 300 may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are provided as examples only and are not intended to limit the implementation of the present disclosure described and / or claimed herein.
[0127] like Figure 3As shown, the electronic device 300 includes a computing unit 301, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 302 or a computer program loaded from a storage unit 308 into a random access memory (RAM) 303. Various programs and data required for the operation of the electronic device 300 can also be stored in the RAM 303. The computing unit 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An I / O interface 305 is also connected to the bus 304.
[0128] Multiple components in the electronic device 300 are connected to the I / O interface 305, including an input unit 306, such as a keyboard, a mouse, etc.; an output unit 307, such as various types of displays, speakers, etc.; a storage unit 308, such as a magnetic disk, an optical disk, etc.; and a communication unit 309, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 309 allows the electronic device 300 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.
[0129] The computing unit 301 can be a variety of general-purpose and / or specialized processing components with processing and computing capabilities. Some examples of the computing unit 301 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The computing unit 301 performs the various methods and processes described above, such as method 100. For example, in some embodiments, method 100 can be implemented as a computer software program that is tangibly contained in a machine-readable medium, such as a storage unit 308. In some embodiments, part or all of the computer program can be loaded and / or installed on the electronic device 300 via ROM 302 and / or communication unit 309. When the computer program is loaded into RAM 303 and executed by the computing unit 301, one or more steps of the method 100 described above can be performed. Alternatively, in other embodiments, the computing unit 301 can be configured to perform method 100 in any other appropriate manner (e.g., by means of firmware).
[0130] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0131] The program code for implementing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device so that when the program code is executed by the processor or controller, the functions / operations specified in the flow chart and / or block diagram are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.
[0132] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, device or equipment. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium can include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0133] It should be noted that the present disclosure also provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute method 100 and achieve the corresponding technical effect achieved by executing the method in the embodiment of the present disclosure. For the sake of concise description, they will not be repeated here.
[0134] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0135] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.
[0136] A computer system may include a client and a server. The client and server are generally remote from each other and typically interact through a communication network. The client-server relationship arises through computer programs running on the respective computers and having a client-server relationship with each other. The server may be a cloud server, a server in a distributed system, or a server integrated with a blockchain.
[0137] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in this disclosure can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solutions disclosed in this disclosure can be achieved. This is not limited herein.
[0138] The above specific embodiments do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure shall be included within the scope of protection of this disclosure.
Claims
1. A static data testing method based on use case drive, characterized in that: include: The basic framework module runs the basic functions of the test system main program and loads other modules; The display module is initialized to display the target test items and receive a user's check operation on the target test items; The basic framework module obtains the test case information corresponding to the target test item selected by the user from the standard test case template, obtains the corresponding test case from the test case loading module according to the test case information, and sends it to the core processing module; The core processing module performs static testing on the test data in the test case, obtains the test result and sends it to the display module through the basic framework module.
2. The method according to claim 1, characterized in that The test case information includes: Script identification, script header information, script grouping, running interface information, configuration information and running condition information.
3. The method according to claim 2, characterized in that The obtaining a corresponding test case from a test case loading module according to the test case information includes: Obtain the script case corresponding to the script identifier from the test case loading module according to the script identifier; Determine the test data in the script use case according to the script header information; Determine the group to which the script use case belongs according to the script grouping; Determine the running condition of the script use case according to the running interface information and the running condition information; Determine the configuration information of the script use case according to the configuration information; Obtain the corresponding test cases based on the script cases with determined test data, grouping, operating conditions and configuration information.
4. The method according to claim 2, characterized in that: The static testing of the test data in the test case includes: Load the configuration data of the test case according to the configuration information in the test case information; If the operating condition information satisfies the static test environment, the single point data check array corresponding to each test point in the test data of the test case is initialized according to the script header information, a static logic point test is performed on each test point and the test result is stored in the corresponding initialized single point data check array; A two-dimensional array is generated according to each single-point data inspection array storing the test results, and the final test results of the test data are represented by the two-dimensional array.
5. The method according to claim 4, characterized in that The step of performing a static logic point test on each test point and storing the test result in a corresponding initialized single point data check array includes: Perform static logic point testing on the elements in each test point according to preset logic point checking rules; The test results of the elements in each test point are stored in the corresponding position of the corresponding initialized single point data check array; The test results of each element in each test point are respectively logically operated to obtain the comprehensive test results corresponding to each test point and store them in the last item of the corresponding initialized single-point data check array.
6. The method according to claim 1, characterized in that The method further comprises: The core processing module obtains the script running status and exception handling information during the static test process, and sends the script running status and exception handling information to the display module through the basic framework module.
7. The method according to claim 6, characterized in that The method further comprises: When the export report button of the display module is triggered, the test report generation module generates and exports a corresponding test report according to the test results, script running status and exception handling information.
8. A static data testing system based on use case drive, characterized in that: include: A core processing module, a standard test case template, a test case loading module, a basic framework module and a display module connected in sequence; wherein the core processing module is also connected to the basic framework module; The basic framework module is used to run the basic functions of the main program of the test system and load other modules; it is also used to obtain the test case information corresponding to the target test item selected by the user from the standard test case template, obtain the corresponding test case from the test case loading module according to the test case information, and send it to the core processing module; A core processing module, used to perform static testing on the test data in the test case, obtain the test results and send them to the display module through the basic framework module; A display module is used for initialization so as to display target test items and receive a user's check operation on the target test items; and is also used for displaying test results; Standard test case template, used to store the test case information corresponding to the target test item; The test case loading module is used to store the test cases corresponding to the target test items.
9. The system according to claim 8, characterized in that The core processing module is also used to obtain the script running status and exception handling information during the static test process, and send the script running status and exception handling information to the display module through the basic framework module.
10. The system according to claim 9, characterized in that The system further comprises: A test report generation module connected to the display module; wherein, The test report generation module is used to generate and export a corresponding test report according to the test results, script running status and exception handling information when the export report button of the display module is triggered.