Drive testing methods, apparatus and computer equipment

Abstract

This application relates to a driver testing method, apparatus, and computer device. The method includes: obtaining a driver testing request; the driver testing request includes a driver to be tested and a test type; obtaining corresponding driver test cases in a target test method based on the test type; the target test method includes at least one pre-stored driver test case, which includes a performance test method, an interface test method, and a runtime state test method; performing driver testing on the driver to be tested based on the driver test cases, and obtaining the driver test results for the driver to be tested. This method can effectively improve driver testing efficiency and quality.

Description

Technical Field

[0001] This application relates to the field of testing technology, and in particular to a driving testing method, apparatus, and computer equipment. Background Technology

[0002] With the development of computer technology, driver testing methods for control software have become an important part of control software.

[0003] Traditional driver testing methods not only require significant manpower to write driver testing documentation, but also necessitate a substantial time commitment to understanding the key aspects of driver testing. Furthermore, the repetitive nature of some driver testing tasks and the difficulty for new testers to grasp the core concepts lead to low efficiency and poor test quality in traditional methods. Summary of the Invention

[0004] Therefore, it is necessary to provide a driver testing method, apparatus, and computer equipment that can effectively improve driver testing efficiency and enhance driver testing quality in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a driver testing method. The method includes:

[0006] Obtain a driver test request; the driver test request includes the driver to be tested and the test type.

[0007] Based on the test type, obtain the corresponding driver test cases in the target test method; the target test method includes at least one pre-stored driver test case, and the driver test case includes a performance test method, an interface test method, and a runtime status test method.

[0008] Based on the driver test cases, driver testing is performed on the driver under test to obtain the driver test results.

[0009] In one embodiment, the performance testing method includes the following steps:

[0010] Acquire driver test data; the driver test data includes multiple driver test parameters, the driver test parameters include the current bit number value of the driver under test and the write value information corresponding to each current bit number value;

[0011] Determine whether each driver test parameter in the driver test data conforms to the preset parameter setting rules, and obtain the determination result;

[0012] The alarm status of the tag number is determined based on the judgment result, and the drive performance test results are obtained based on the alarm status of the tag number.

[0013] In one embodiment, the operational status testing method includes the following steps:

[0014] The current operating period of the monitoring and control device is obtained; the current operating period is either the configuration period or the monitoring period; the monitoring and control device is used to perform drive testing on the driver to be tested.

[0015] If the current running period is the configuration period, then check whether the driver configuration has been saved; if not, output an alarm message.

[0016] If the current running period is a monitoring period, then the system checks whether the current tag value data of the driver under test is correct and whether the current running status of the driver under test is normal, and outputs the detection results.

[0017] In one embodiment, the operational status testing method further includes:

[0018] Obtain the current redundancy status, which includes network redundancy status and device redundancy status;

[0019] If there is no network redundancy or device redundancy in the current redundancy status, then obtain the number of drivers to be tested running during the monitoring period and the current tag number value of the drivers to be tested, and determine the tag number alarm status based on the number of drivers to be tested and the corresponding current tag number value.

[0020] If only network redundancy exists in the current redundancy state, then the preset first redundancy configuration program is executed and the current bit number value of the driver to be tested is obtained, and the bit number alarm state is determined based on the current bit number value; the first redundancy configuration program includes the network redundancy configuration program;

[0021] If only device redundancy exists in the current redundancy state, then a preset second redundancy configuration program is executed and the current tag number value of the driver to be tested is obtained, and the tag number alarm state is determined based on the current tag number value; the second redundancy configuration program includes a device redundancy configuration program;

[0022] If the current redundancy status includes both network redundancy and device redundancy, then a preset third redundancy configuration program is executed and the current tag number value of the driver to be tested is obtained. Based on the current tag number value, the tag number alarm status is determined. The third redundancy configuration program includes a network redundancy configuration program and a device redundancy configuration program.

[0023] In one embodiment, the interface testing method includes: modifying the testing method so that the step of performing driver testing on the driver to be tested based on the driver test cases, and obtaining the driver test results of the driver to be tested, includes:

[0024] Get at least one modified object;

[0025] Obtain the modification test method corresponding to the modified object in the interface test method, and perform driver testing on the driver to be tested according to the modification test method to obtain the driver test result of the driver to be tested; the modification test method includes a control station modification test method, wherein the control station modification test method includes a parameter verification method, a redundancy test method, and a network test method.

[0026] In one embodiment, the redundancy testing method includes the following steps:

[0027] Obtain the redundancy test signal, and obtain the redundancy configuration status based on the redundancy test signal;

[0028] Obtain a device interrupt signal and obtain the device operating status based on the device interrupt signal; the device operating status includes the on or off status of at least one computer device;

[0029] Obtain the current tag number value and the current tag number alarm status, and obtain the redundancy test results based on the current tag number value, the current tag number alarm status, the redundancy configuration status, and the device operating status.

[0030] In one embodiment, the modification test method further includes a bit number modification test method, which includes the following steps:

[0031] Obtain the current driver configuration and import it.

[0032] Refresh the configuration status and tag number status;

[0033] Obtain the current bit number and store it as the bit number under the current drive configuration.

[0034] In one embodiment, when the driver test request includes at least two drivers to be tested, the runtime state test method further includes:

[0035] Obtain the initial driver test data of the second driver to be tested; the initial driver test data includes the initial tag number value and the initial tag number alarm status of the second driver to be tested;

[0036] Modify the driver configuration of the first driver to be tested, and obtain the current driver test data of the second driver to be tested and other drivers to be tested; the current driver test data includes the current bit number value and current bit number alarm status of the second driver to be tested; the drivers to be tested include the first driver to be tested and the second driver to be tested.

[0037] Based on the initial driver test data and the current driver test data of the second driver to be tested, obtain the running status test results.

[0038] Secondly, this application also provides a drive testing device. The device includes:

[0039] The first acquisition module is used to acquire driver test requests; the driver test request includes the driver to be tested and the test type.

[0040] The second acquisition module is used to acquire the corresponding driver test cases in the target test method based on the test type; the target test method includes at least one pre-stored driver test case, and the driver test case includes a performance test method, an interface test method, and a runtime status test method;

[0041] The driver testing module is used to perform driver testing on the driver under test based on the driver test cases, and obtain the driver test results of the driver under test.

[0042] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement any of the aforementioned driver testing methods.

[0043] The aforementioned driver testing method, apparatus, and computer equipment include: acquiring a driver testing request; the driver testing request including a driver to be tested and a test type; acquiring corresponding driver test cases in a target test method based on the test type; the target test method including at least one pre-stored driver test case, the driver test case including a performance test method, an interface test method, and a runtime state test method; performing driver testing on the driver to be tested based on the driver test cases to obtain the driver test results. This application determines the target test method based on the test type in the driver testing request, thereby enabling the determination of suitable and technically mature driver test cases according to specific driver testing needs. This allows for focusing on key aspects of driver testing, avoiding blind testing, and improving driver testing quality. When some driver testing work is repetitive, pre-stored driver test cases can be directly called for driver testing, eliminating the need for significant manpower to write extensive driver testing documentation, saving driver testing time and improving driver testing efficiency. Attached Figure Description

[0044] Figure 1 This is a flowchart illustrating the driving test method in one embodiment;

[0045] Figure 2 This is a flowchart illustrating a performance testing method in one embodiment;

[0046] Figure 3 This is a flowchart illustrating the runtime state testing method in one embodiment. Figure 1 ;

[0047] Figure 4 This is a flowchart illustrating the runtime state testing method in one embodiment. Figure 2 ;

[0048] Figure 5 This is a flowchart illustrating a redundancy testing method in one embodiment;

[0049] Figure 6 This is a flowchart illustrating the runtime state testing method in one embodiment. Figure 3 ;

[0050] Figure 7 This is a structural block diagram of the driving test device in one embodiment;

[0051] Figure 8 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0053] The driver testing method provided in this application can be applied, but is not limited to, devices or systems consisting of a single node, a single server, a server and an operator station, server redundancy and an operator station, a large library and an operator station, or a large library redundancy and an operator station. The aforementioned devices and systems refer to devices and systems formed by different computer deployment modes, and the driver to be tested is a component installed on the computer and attached to the control software.

[0054] In one embodiment, Figure 1 This is a flowchart illustrating the driving test method in one embodiment, such as... Figure 1 As shown, the driver testing method provided in this embodiment includes the following steps:

[0055] Step 110: Obtain the driver test request; the driver test request includes the driver to be tested and the test type.

[0056] The driver test request is generated based on the user's specific driver testing requirements. The driver test request includes the name and attribute parameters of the driver to be tested.

[0057] Step 120: Obtain the corresponding driver test cases in the target test method based on the test type; the target test method includes at least one pre-stored driver test case, which includes performance test methods, interface test methods, and runtime status test methods.

[0058] Performance testing methods can be used, but are not limited to, testing the performance of the driver under test. Interface testing methods can be used, but are not limited to, testing operations such as adding, deleting, and modifying the driver under test. Runtime testing methods can be used, but are not limited to, testing the runtime status of the driver under test.

[0059] Driver test cases represent testing methods for common test points in driver testing, derived by summarizing and analyzing past driver testing experience and data. These test cases can serve as a reference manual and can be widely applied to driver testing of numerous industrial software applications. Because they are supported by a large amount of driver testing data, the reliability of the test results is guaranteed, thus improving the quality of driver testing.

[0060] Step 130: Perform driver testing on the driver to be tested based on the driver test cases to obtain the driver test results.

[0061] The aforementioned driver testing method includes: obtaining a driver testing request; the driver testing request includes the driver to be tested and the test type; obtaining the corresponding driver test cases in the target test method based on the test type; the target test method includes at least one pre-stored driver test case, which includes performance testing methods, interface testing methods, and runtime status testing methods; and performing driver testing on the driver to be tested based on the driver test cases to obtain the driver test results. This application determines the target test method based on the test type in the driver testing request, thereby enabling the identification of suitable and technically mature driver test cases according to specific driver testing requirements. This allows for focusing on the key aspects of driver testing, avoiding blind testing, and improving driver testing quality. When some driver testing work is repetitive, pre-stored driver test cases can be directly called for driver testing, eliminating the need for significant manpower to write driver testing documentation, saving driver testing time, and improving driver testing efficiency.

[0062] In one embodiment, Figure 2 This is a flowchart illustrating a performance testing method in one embodiment, such as... Figure 2 As shown, the performance testing method includes the following steps.

[0063] Step 210: Obtain driver test data; the driver test data includes multiple driver test parameters, which include the current bit value of the driver under test and the write value information corresponding to each current bit value.

[0064] In the field of industrial automation, tag numbers are a combination of Chinese, English, and numbers to represent a specific channel, facilitating monitoring of each channel. In this application, a tag number can refer to an industrial production parameter to be monitored, such as temperature or water level. The tag number value represents the actual value of this parameter, while the point tag number indicates the quantity of this parameter. For example, if the tag number represents temperature, then a 20,000-point tag number indicates that 20,000 temperature data points have been collected, and the tag number value represents the specific numerical value of the temperature.

[0065] The write-value information includes the test symbol assigned to each current bit value by the driver tester and the latency information for each test symbol displayed on the driver interface. The test symbol can be a number, a letter, or other symbol; this application does not impose any restrictions. The latency information represents the time elapsed from when the driver tester inputs the test symbol to when the test symbol is displayed on the driver interface.

[0066] Specifically, the tag number data is obtained by the driver under test from a data acquisition device in the industrial environment. Therefore, the tag number can be used as a performance parameter of the driver under test to obtain the performance test results. Additionally, the data acquisition device can be a sensor or other acquisition device used to collect tag number data from the industrial environment and transmit the collected tag number data to the driver under test.

[0067] Step 220: Determine whether each driver test parameter in the driver test data conforms to the preset parameter setting rules, and obtain the judgment result.

[0068] Among them, the preset parameter setting rules represent the parameter value range or parameter value rules for each driver test parameter.

[0069] Step 230: Determine the tag number alarm status based on the judgment result, and obtain the drive performance test results based on the tag number alarm status.

[0070] It is understandable that if each driver test parameter in the driver test data is within the range of the parameter values ​​or conforms to the parameter value rules, then the driver test data can be determined to be normal, and the tag number alarm status can be further determined to be no alarm signal. Thus, the driver performance test result shows that the working state of the driver under test is normal.

[0071] In this embodiment, driver test data is acquired as a parameter to measure driver performance. The driver performance test result of the driver under test is determined by judging whether each driver test parameter in the driver test data meets the preset parameter setting rules. Since the driver test data is collected from the actual industrial environment, the data source is reliable, which makes the driver test results more reliable and further improves the quality of driver testing.

[0072] In one embodiment, the specifications of the monitoring and control equipment are obtained; based on the specifications, a first quantity of control equipment and a second quantity of corresponding tag numbers of the control equipment are obtained; based on the second quantity, the current tag number value of the driver to be tested and the write value information of each current tag number value are obtained; it is determined whether each current tag number value and its corresponding write value information conform to the preset parameter setting rules, and a judgment result is obtained, wherein the preset parameter setting rules include the tag number value range and the write value setting rules; based on the judgment result, the tag number alarm status is determined, and the driver performance test result is obtained based on the tag number alarm status.

[0073] The control equipment includes control stations and controllers. The control equipment is a prerequisite for adding the driver under test and is located within the driver under test. It can be used to represent the data source of the tag value data; for example, control equipment number one corresponds to tag value data collected from factory number one.

[0074] Specifically, the tag number range can be set to a number from 1 to 100. If a symbol outside the range, such as a "hash" or "question mark," appears in the current tag number value, it indicates that the current tag number value is abnormal, and a tag number alarm signal will be issued. In this case, the driver under test may have some faults, and relevant maintenance personnel should be notified for troubleshooting and further repair. If a symbol outside the range, such as a "hash" or "question mark," appears in the current tag number value, it can be interpreted as the current tag number value not being displayed.

[0075] Additionally, the write value information includes the test symbol assigned to each current tag value by the driver tester and the corresponding delay time for each test symbol. The delay time represents the duration from when the driver tester inputs the test symbol to when the test symbol appears on the driver interface. For example, if the tester inputs the number "1" as the test symbol for the current tag value, and the duration from when the driver tester inputs the number "1" to when the number "1" appears on the driver interface is 2 seconds, and the preset delay time range is 1-10 seconds, this indicates that the write value corresponding to the current tag value can be successfully written, and the write delay time is within a reasonable range. Therefore, it can be inferred that the write value information for the current tag value is normal.

[0076] It should be noted that the delay time of the aforementioned test symbols can measure the performance of the driver under test or the overall performance of the entire control software. Thus, by testing whether the delay time is within the preset parameter range, the performance of the driver under test can be detected. Therefore, the performance of the driver under test can be comprehensively tested by combining the current tag value, the test symbol and its delay time, thereby further improving the test effect and test quality of the driver test.

[0077] In one embodiment, when there is only one control device, the tag number data comes from a single data source. If all 20,000 tag number values ​​collected are normal and the test symbol corresponding to each current tag number value can be successfully written without delay, then the tag number alarm status is normal (no alarm will sound), and the performance of the driver under test is also normal. When there are multiple control devices, for example, five control devices, if all 50,000 tag number values ​​collected are normal and the test symbol corresponding to each current tag number value can be successfully written without delay, then the tag number alarm status is normal (no alarm will sound), and the performance of the driver under test is also normal. Here, "successful writing" means the test symbol can be successfully displayed on the driver interface, and "no writing delay" means the delay time experienced by the test symbol to be displayed on the driver interface is within a preset range.

[0078] In one embodiment, Figure 3 This is a flowchart illustrating the runtime state testing method in one embodiment. Figure 1 ,like Figure 3 As shown, the runtime status test method includes the following steps:

[0079] Step 310: Obtain the current operating period of the monitoring and control equipment; the current operating period is either the configuration period or the monitoring period; the monitoring and control equipment is used to perform driver testing on the driver to be tested.

[0080] The monitoring and control equipment includes configuration software and monitoring software. The configuration period refers to the operational period of the configuration software, and the monitoring period refers to the operational period of the monitoring software. The configuration software is used to import the driver to be tested and configure parameters, etc. The monitoring software is used to detect and analyze tag value data, etc.

[0081] Step 320: If the current running period is the configuration period, check whether the drive configuration has been saved. If not, output an alarm message.

[0082] Step 330: If the current running period is the monitoring period, check whether the current tag number value data of the driver under test is correct and whether the current running status of the driver under test is normal, and output the detection results.

[0083] Among them, "Is the current tag number value data correct?" indicates whether the current tag number value is within the preset tag number value range, and "Current running status of the driver to be tested" indicates whether the driver to be tested has run successfully or whether the tag number status is normal.

[0084] In addition, the operational status test includes operational status testing processes under different software deployment modes. These software deployment modes include in-system deployment and out-of-system deployment. In-system deployment refers to the software deployment mode where the engineering configuration software and the driver configuration software are installed on the same computer device; the out-of-system deployment mode is the opposite. Since the difference between in-system and out-of-system deployment modes lies only in whether the software is deployed on the same computer device and does not affect the final operational status test results, they will not be described separately. The engineering configuration software can be a data acquisition device, monitoring software, or other configuration software.

[0085] In one embodiment, Figure 4 This is a flowchart illustrating the runtime state testing method in one embodiment. Figure 2 ,like Figure 4 As shown, the runtime status testing method also includes:

[0086] Step 410: Obtain the current redundancy status, which includes network redundancy status and device redundancy status.

[0087] Network redundancy refers to providing users with a backup network connection to prevent the entire network from stopping due to a problem in any part of the network. It achieves network redundancy through backup, ensuring uninterrupted network operation. Network redundancy can be either enabled or disabled.

[0088] Equipment redundancy refers to providing backup service equipment to users in case of power outages or machine failures that cause the entire service to stop operating. Equipment redundancy status includes two states: equipment redundancy function enabled and equipment redundancy function disabled.

[0089] Step 420: If there is no network redundancy or device redundancy in the current redundancy status, obtain the number of drivers to be tested running during the monitoring period and the current tag number value of the drivers to be tested, and determine the tag number alarm status based on the number of drivers to be tested and the corresponding current tag number value.

[0090] Specifically, "No network redundancy or device redundancy exists in the current redundancy state" means that both network redundancy and device redundancy functions are disabled. In this state, only one network link and one service device are available for user use. When there are one or more drivers to be tested, as long as the current tag number value is normal, it indicates that the network connection is normal and the service device is operating normally, and no tag number alarm signal is issued at this time; if the current tag number value is abnormal, it indicates that the network connection is interrupted or the service device is operating abnormally, and a tag number alarm signal is issued at this time.

[0091] Step 430: If only network redundancy exists in the current redundancy state, execute the preset first redundancy configuration program and obtain the current tag number value of the driver to be tested, and determine the tag number alarm state based on the current tag number value; the first redundancy configuration program includes the network redundancy configuration program.

[0092] Specifically, "Only network redundancy exists in the current redundancy state" means that the network redundancy function is enabled and the device redundancy function is disabled. At this time, network redundancy needs to be configured, and there is a backup network link for users. If the current tag number value is normal, it means that the network connection is normal and the service device is operating normally, and a tag number alarm signal is issued. If the current tag number value is abnormal, it means that the network connection is interrupted or the service device is operating abnormally, and a tag number alarm signal is issued.

[0093] Step 440: If only the device redundancy state exists in the current redundancy state, then execute the preset second redundancy configuration program and obtain the current tag number value of the driver to be tested, and determine the tag number alarm state based on the current tag number value; the second redundancy configuration program includes the device redundancy configuration program.

[0094] Specifically, "Only device redundancy exists in the current redundancy state" means that the device redundancy function is enabled and the network redundancy function is disabled. At this time, device redundancy configuration is required, and there are backup service devices available for users. If the current tag number value is normal, it means that the network connection is normal and the service device is operating normally, and no tag number alarm signal will be issued at this time. If the current tag number value is abnormal, it means that the network connection is interrupted or the service device is operating abnormally, and a tag number alarm signal will be issued at this time.

[0095] Step 450: If there are network redundancy and device redundancy in the current redundancy status, execute the preset third redundancy configuration program and obtain the current tag number value of the driver to be tested, and determine the tag number alarm status based on the current tag number value; the third redundancy configuration program includes the network redundancy configuration program and the device redundancy configuration program.

[0096] Specifically, "The current redundancy status includes both network redundancy and device redundancy" means that both network redundancy and device redundancy functions are enabled. At this time, network redundancy and device redundancy configuration is required, and there are backup network links and backup service devices available for users. If the current tag number value is normal, it means that the network connection is normal and the service device is operating normally, and no tag number alarm signal will be issued at this time. If the current tag number value is abnormal, it means that the network connection is interrupted or the service device is operating abnormally, and a tag number alarm signal will be issued at this time.

[0097] In one embodiment, step 430 includes steps 431 to 436, wherein:

[0098] Step 431: Configure network redundancy, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0099] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0100] Step 432: Disconnect the first network cable, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0101] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0102] Step 433: Connect the first network cable, unplug the second network cable, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0103] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0104] Step 434: Disconnect the first and second network cables simultaneously, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0105] It should be noted that if the current tag number value is displayed abnormally, then the alarm status of the current tag number will be confirmed to have disappeared.

[0106] Step 435: Connect either the first network cable or the second network cable, obtain the current tag number value and tag number recovery time of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value and tag number recovery time.

[0107] It should be noted that if the current tag number value is normal, the test symbol corresponding to the current tag number value is written normally without delay, and the tag number value recovery time is within the preset threshold range, then the current tag number alarm status is determined to be normal.

[0108] Step 436: Modify the network cycle and network retry count multiple times to obtain the current tag number value and tag number recovery time of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value and tag number recovery time.

[0109] It should be noted that if the current tag number value is normal, the test symbol corresponding to the current tag number value is written normally without delay, and the tag number value recovery time is within the preset threshold range, then the current tag number alarm status is determined to be normal.

[0110] Generally, the current tag value remains unchanged after modifying the network cycle and the number of network retries. Scenarios in which the current tag value changes from an abnormal value to a normal value include: network disconnection and recovery, server failure and recovery, and device power failure and recovery.

[0111] The embodiments provided in this application cover all test points when configuring network redundancy and device redundancy, resulting in more comprehensive driver testing coverage and more reliable driver testing results, thereby further improving the quality and effectiveness of driver testing.

[0112] In one embodiment, step 440 includes steps 441 to 446, wherein:

[0113] Step 441: Configure device redundancy, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0114] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0115] Step 442: Disconnect from the first device, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0116] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0117] Step 443: Connect the first device, disconnect the second device, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0118] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0119] Step 444: Simultaneously disconnect the first and second devices, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0120] It should be noted that if the current tag number value is displayed abnormally, then the alarm status of the current tag number will be confirmed to have disappeared.

[0121] Step 445: Connect either the first device or the second device, obtain the current tag number value and tag number recovery time of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value and tag number recovery time.

[0122] It should be noted that if the current tag number value is normal, the test symbol corresponding to the current tag number value is written normally without delay, and the tag number value recovery time is within the preset threshold range, then the current tag number alarm status is determined to be normal.

[0123] Step 446: Modify the network cycle and network retry count multiple times to obtain the current tag number value and tag number recovery time of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value and tag number recovery time.

[0124] It should be noted that if the current tag number value is normal, the test symbol corresponding to the current tag number value is written normally without delay, and the tag number value recovery time is within the preset threshold range, then the current tag number alarm status is determined to be normal.

[0125] In one embodiment, step 450 includes steps 451 to 459, wherein:

[0126] Step 451: Simultaneously configure network and device redundancy, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0127] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0128] Step 452: Disconnect the first network cable, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0129] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0130] Step 453: Connect the first network cable, unplug the second network cable, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0131] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0132] Step 454: Disconnect the first and second network cables simultaneously, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0133] It should be noted that if the current tag number value is normal and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal; if the current tag number value is displayed abnormally, then the alarm status of the current tag number is determined to be gone.

[0134] Step 455: Disconnect from the first device, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0135] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0136] Step 456: Connect the first device, disconnect the second device, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0137] It should be noted that if the current tag number value is normal, and the test symbol corresponding to the current tag number value is written normally without delay, then the alarm status of the current tag number is determined to be normal.

[0138] Step 457: Simultaneously disconnect the two network cables and the two devices, obtain the current tag number value of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value.

[0139] It should be noted that if the current tag number value is displayed abnormally, then the alarm status of the current tag number will be confirmed to have disappeared.

[0140] Step 458: Connect either of the two devices or connect either of the two network cables to obtain the current tag number value and tag number recovery time of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value and tag number recovery time.

[0141] It should be noted that if the current tag number value is normal, the test symbol corresponding to the current tag number value is written normally without delay, and the tag number value recovery time is within the preset threshold range, then the current tag number alarm status is determined to be normal.

[0142] Step 459: Modify the network cycle and network retry count multiple times to obtain the current tag number value and tag number recovery time of the driver to be tested during the monitoring period, and determine the tag number alarm status based on the current tag number value and tag number recovery time.

[0143] It should be noted that if the current tag number value is normal, the test symbol corresponding to the current tag number value is written normally without delay, and the tag number value recovery time is within the preset threshold range, then the current tag number alarm status is determined to be normal.

[0144] In one embodiment, the interface testing method includes: modifying the testing method to perform driver testing on the driver to be tested based on the driver test cases, and obtaining the driver test results of the driver to be tested, i.e., step 120 includes steps 121 and 122, wherein:

[0145] Step 121: Obtain at least one modified object.

[0146] Step 122: Obtain the modification test method corresponding to the modified object in the interface test method, and perform driver testing on the driver to be tested according to the modification test method to obtain the driver test result of the driver to be tested; the modification test method includes the control station modification test method, which includes parameter verification method, redundancy test method and network test method.

[0147] In one embodiment, Figure 5 This is a flowchart illustrating a redundancy testing method in one embodiment, such as... Figure 5 As shown, the redundancy testing method includes the following steps:

[0148] Step 510: Obtain the redundancy test signal and obtain the redundancy configuration status based on the redundancy test signal.

[0149] The redundancy test signal indicates the start of the redundancy test. Configuring redundancy means configuring multiple computer devices as server devices simultaneously; not configuring redundancy means only one computer device is used as a server device. The redundancy configuration status indicates whether redundancy is configured.

[0150] Step 520: Obtain the device interrupt signal and obtain the device operating status based on the device interrupt signal; the device operating status includes the on or off status of at least one computer device.

[0151] Among them, the device interruption signal indicates that the power supply or network of the computer device is disconnected.

[0152] Step 530: Obtain the current tag number value and the current tag number alarm status, and obtain the redundancy test results based on the current tag number value, the current tag number alarm status, the redundancy configuration status, and the device operating status.

[0153] Specifically, if the redundancy configuration status is "redundancy enabled," it indicates that multiple computer devices are acting as service devices. Theoretically, when the device operating status includes one computer device being disconnected and others being turned on, it means that while one computer device is disconnected, other computer devices are operating normally as service devices. Therefore, if the current tag number value is normal and the current tag number alarm status is "no tag number alarm signal," the redundancy test result is normal; if the current tag number value is empty and the current tag number alarm status is not displayed, the redundancy test result is abnormal. When the device operating status includes all computer devices being disconnected, it means that no computer device is operating normally as a service device. Therefore, if the current tag number value is empty and the current tag number alarm status is not displayed, the redundancy test result is normal.

[0154] If the redundancy configuration status is "redundancy disabled," it means that one computer device is acting as a service device. Theoretically, when the device is running with one computer device disconnected and no computer device is operating normally as a service device, if the current tag number value is empty and the current tag number alarm status is not displayed, the redundancy test result is normal. When the device is running with one computer device enabled, it means that one computer device is operating normally as a service device. Therefore, if the current tag number value is normal and the current tag number alarm status is "no tag number alarm signal," the redundancy test result is normal.

[0155] In one embodiment, the parameter verification method includes the following steps: obtaining device parameter information of the control device; the device parameter information includes the name, model, IP address, configuration path, communication path, and tag number of the control device; verifying the device parameter information based on preset control device parameters to obtain the parameter verification result.

[0156] Specifically, if any of the device parameters—name, model, IP address, configuration path, communication path, or tag number—does not conform to the preset range setting rules for the control device parameters, the parameter verification result will be abnormal. In this case, an alarm message can be issued to remind the relevant driver testing personnel to handle the issue promptly. The name information includes the name and description of the control device. The name of the control device can be displayed with a maximum of 128 characters; exceeding 128 characters will result in a failed verification. The description of the control device displays its description content, with a maximum of 64 characters; exceeding 64 characters will also result in a failed verification. The configuration path of the control device displays the configuration path of the driver under test, which can be modified to other path configurations. The communication path of the control device is the communication path from the destination control device to the direct-connect communication module.

[0157] In one embodiment, the modification test method further includes a tag number modification test method, which includes the following steps: obtaining the current driver configuration and importing the current driver configuration; refreshing the configuration status and tag number status; obtaining the current tag number and storing the current tag number as the tag number under the current driver configuration.

[0158] Specifically, the process involves obtaining a driver configuration import request and then obtaining the current driver configuration based on the request; importing the current driver configuration and refreshing the configuration status and tag number status; obtaining the current tag number and storing it as the tag number under the current driver configuration.

[0159] It should be noted that the stored current tag number includes tag number information such as name, type, I / O address, partition, description, and range, but does not include the tag number value. By storing the current tag number as the tag number under the current driver configuration, a mapping is established between the current tag number and the current driver configuration. When the driver tester modifies the tag number name or other information, the modified tag number name or other information can be immediately seen on the configuration end. After the configuration is saved, the modified tag number name or other information can also be seen on the monitoring end.

[0160] In one embodiment, the network testing method includes the following steps: acquiring network test information of a control device; the network test information includes multiple network parameters of the control device; the network parameters include network cycle, tag value recovery time, network retry count, and network timeout time; determining whether each network parameter in the network test information is within the corresponding preset network parameter range, and obtaining the network test result.

[0161] Specifically, the network cycle includes the first network cycle and the second network cycle, both representing the description cycle of the control station. Their values ​​are generally set between 10ms and 86,400,000ms, with a default value of 1000ms when not modified. The tag number recovery time represents the time it takes for the tag number value to return to normal after modification of the first or second network cycle during configuration and subsequent publication. Its theoretical maximum value is the first or second network cycle plus the number of network retries multiplied by the network timeout.

[0162] Network timeout includes a first network timeout and a second network timeout, both representing the control station's timeout period. Their values ​​are typically set between 10ms and 86,400,000ms, with a default of 1000ms when not modified. Network retries include a first network retries count and a second network retries count, both representing the number of times packets are retransmitted after a timeout. Their values ​​are typically set between 1 and 30, with a default of 3 when not modified.

[0163] In one embodiment, the interface testing method includes: adding a test method, which includes the following steps: obtaining the current driver name displayed on the driver interface; comparing the current driver name with the actual driver name of the pre-stored driver to be tested to obtain a comparison result; and determining whether the driver to be tested has been successfully added based on the comparison result.

[0164] Specifically, when the monitoring and control device receives a driver addition request, it retrieves the current driver name displayed on the driver interface from the software database or the data collector, and compares the current driver name with the actual driver name to be tested in the driver addition request. If the current driver name matches the actual driver name, it is determined that the driver to be tested has been successfully added.

[0165] The data acquisition unit is a standalone software application that functions similarly to monitoring software, collecting data. However, it lacks a graphical monitoring interface and only displays the data values. The database, on the other hand, is the database within the monitoring and control equipment. It has a graphical configuration interface that shows the names and descriptions of the data, but not their values.

[0166] In one embodiment, Figure 6 This is a flowchart illustrating the runtime state testing method in one embodiment. Figure 3 ,like Figure 6 As shown, when a driver test request includes at least two drivers to be tested; the runtime state test method also includes:

[0167] Step 610: Obtain the initial driver test data of the second driver to be tested; the initial driver test data includes the initial tag number value and the initial tag number alarm status of the second driver to be tested.

[0168] The initial driver test data refers to the driver test data obtained before modifying the driver configuration of the first driver to be tested.

[0169] Step 620: Modify the driver configuration of the first driver to be tested, and obtain the current driver test data of the second driver to be tested and other drivers to be tested; the current driver test data includes the current tag number value and current tag number alarm status of the second driver to be tested; the drivers to be tested include the first driver to be tested and the second driver to be tested.

[0170] The current driver test data refers to the driver test data obtained after modifying the driver configuration of the first driver under test. The driver configuration includes multiple driver attribute parameters, especially the attribute parameters related to the tag number, such as the tag number description and range value, but the value of the tag number is not modified.

[0171] Step 630: Obtain the running status test results based on the initial driver test data and the current driver test data of the second driver to be tested.

[0172] If both the initial driver test data and the current driver test data are normal, it means that modifying the driver configuration of the first driver under test will not affect the driver test data of the second driver under test. In other words, the first and second drivers under test will not affect each other's bit values, and the runtime test results are normal. If the initial driver test data is normal, but the current driver test data is abnormal, it means that modifying the driver configuration of the first driver under test will affect the driver test data of the second driver under test. In other words, the first and second drivers under test will affect each other's bit values, and the runtime test results are abnormal. This method of using controlled variables to detect anomalies can scientifically and effectively detect anomalies when multiple drivers under test are running simultaneously, effectively improving the quality of driver testing.

[0173] In one specific embodiment, a driver test request is obtained; the driver test request includes the driver to be tested and the test type. Based on the test type, corresponding driver test cases in the target test method are obtained; the target test method includes at least one pre-stored driver test case, which includes performance testing methods, interface testing methods, and runtime status testing methods. Based on the driver test cases, driver testing is performed on the driver to be tested to obtain the driver test results.

[0174] The performance testing method includes the following steps: acquiring driver test data; the driver test data includes multiple driver test parameters, which include the current bit number value of the driver under test and the write value information corresponding to each current bit number value; determining whether each driver test parameter in the driver test data conforms to the preset parameter setting rules, and obtaining the judgment result; determining the bit number alarm status based on the judgment result, and obtaining the driver performance test result based on the bit number alarm status.

[0175] The operational status testing method includes the following steps: obtaining the current operational period of the monitoring and control equipment; whether the current operational period is the configuration period or the monitoring period; the monitoring and control equipment is used to perform driver testing on the driver under test; if the current operational period is the configuration period, it checks whether the driver configuration is saved, and outputs an alarm message if it is not saved; if the current operational period is the monitoring period, it checks whether the current tag number value data of the driver under test is correct and whether the current operational status of the driver under test is normal, and outputs the test results.

[0176] The operational status testing method further includes: obtaining the current redundancy status, which includes network redundancy status and device redundancy status; if there is no network redundancy status or device redundancy status in the current redundancy status, obtaining the number of drivers under test running during the monitoring period and the current tag number value of the drivers under test, and determining the tag number alarm status based on the number of drivers under test and the corresponding current tag number value; if there is only network redundancy status in the current redundancy status, executing a preset first redundancy configuration program and obtaining the current tag number value of the drivers under test, and determining the tag number alarm status based on the current tag number value; the first redundancy configuration program includes a network redundancy configuration program; if there is only device redundancy status in the current redundancy status, executing a preset second redundancy configuration program and obtaining the current tag number value of the drivers under test, and determining the tag number alarm status based on the current tag number value; the second redundancy configuration program includes a device redundancy configuration program; if there are both network redundancy status and device redundancy status in the current redundancy status, executing a preset third redundancy configuration program and obtaining the current tag number value of the drivers under test, and determining the tag number alarm status based on the current tag number value; the third redundancy configuration program includes a network redundancy configuration program and a device redundancy configuration program.

[0177] The interface testing methods include: modifying the test methods, then performing driver testing on the driver to be tested based on the driver test cases, and obtaining the driver test results of the driver to be tested, including: obtaining at least one modified object; obtaining the modified test methods of the corresponding modified objects in the interface test methods, and performing driver testing on the driver to be tested according to the modified test methods, and obtaining the driver test results of the driver to be tested; the modified test methods include control station modified test methods, wherein the control station modified test methods include parameter verification methods, redundancy test methods, and network test methods.

[0178] The redundancy testing method includes the following steps: acquiring a redundancy test signal and acquiring a redundancy configuration status based on the redundancy test signal; acquiring a device interrupt signal and acquiring a device operating status based on the device interrupt signal; the device operating status includes the on or off status of at least one computer device; acquiring the current tag number value and the current tag number alarm status, and acquiring the redundancy test result based on the current tag number value, the current tag number alarm status, the redundancy configuration status, and the device operating status.

[0179] The test method also includes a tag number modification test method, which includes the following steps: obtaining the current driver configuration and importing the current driver configuration; refreshing the configuration status and tag number status; obtaining the current tag number and storing the current tag number as the tag number under the current driver configuration.

[0180] When the driver test request includes at least two drivers to be tested, the runtime test method further includes: obtaining the initial driver test data of the second driver to be tested; the initial driver test data includes the initial tag number value and the initial tag number alarm status of the second driver to be tested; modifying the driver configuration of the first driver to be tested, and obtaining the current driver test data of the other drivers to be tested; the current driver test data includes the current tag number value and the current tag number alarm status of the second driver to be tested; the drivers to be tested include the first driver to be tested and the second driver to be tested; and obtaining the runtime test results based on the initial driver test data and the current driver test data of the second driver to be tested.

[0181] The embodiments provided in this application have the following technical effects:

[0182] (1) The driver testing method provided in this application can greatly improve the accuracy and coverage of driver testing, enabling more targeted driver testing, improving driver testing efficiency, and reducing the blindness of driver testing.

[0183] (2) The driving test method provided in this application can reuse the driving test cases provided in this application for driving test, and can carry out driving test tasks for important test points in a targeted manner. There is no need for manual writing of test materials, which can reduce the entry threshold of driving test, save human resources, and improve the efficiency and quality of driving test.

[0184] (3) The driver testing method provided in this application is a compilation of all previous driver testing methods, with mature supporting driver testing schemes, test points, and application experience in actual driver testing scenarios. Compared with traditional driver testing methods, the driver testing method provided in this application can not only improve the quality of driver testing but also be very familiar with targeted simulated test scenarios, thereby reducing the feedback and handling of on-site problems in the driver testing process, saving driver testing time, and improving driver testing efficiency.

[0185] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0186] Based on the same inventive concept, this application also provides a driver testing apparatus for implementing the driver testing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more driver testing apparatus embodiments provided below can be found in the limitations of the driver testing method described above, and will not be repeated here.

[0187] In one embodiment, Figure 7 Here is a structural block diagram of the driving test device in one embodiment, such as Figure 7 As shown, a drive testing device is provided, including: a first acquisition module 710, a second acquisition module 720, and a drive testing module 730, wherein:

[0188] The first acquisition module 710 is used to acquire driver test requests; the driver test request includes the driver to be tested and the test type.

[0189] The second acquisition module 720 is used to acquire the corresponding driver test cases in the target test method based on the test type; the target test method includes at least one pre-stored driver test case, and the driver test case includes performance test method, interface test method and runtime status test method.

[0190] The driver test module 730 is used to perform driver testing on the driver under test based on driver test cases, and obtain the driver test results of the driver under test.

[0191] In one embodiment, the driver testing module 730 includes a performance testing unit, which further includes a test data acquisition subunit, a test parameter judgment subunit, and a test result acquisition subunit, wherein:

[0192] The test data acquisition subunit is used to acquire driver test data. The driver test data includes multiple driver test parameters, which include the current bit value of the driver under test and the write value information corresponding to each current bit value.

[0193] The test parameter judgment subunit is used to determine whether each driver test parameter in the driver test data conforms to the preset parameter setting rules and obtain the judgment result.

[0194] The test result acquisition subunit is used to determine the tag number alarm status based on the judgment result, and to acquire the drive performance test results based on the tag number alarm status.

[0195] In one embodiment, the drive test module 730 includes a runtime status test unit, which comprises a runtime acquisition subunit, a configuration period detection subunit, and a monitoring period detection subunit, wherein:

[0196] The runtime acquisition subunit is used to acquire the current runtime of the monitoring and control equipment; the current runtime is either the configuration period or the monitoring period; the monitoring and control equipment is used to perform driver testing on the driver to be tested.

[0197] The configuration period detection subunit is used to detect whether the drive configuration has been saved if the current running period is the configuration period. If it has not been saved, an alarm message will be output.

[0198] The monitoring period detection subunit is used to detect whether the current tag number value data of the driver under test is correct and whether the current running status of the driver under test is normal if the current running period is the monitoring period, and output the detection results.

[0199] In one embodiment, the operational status testing unit further includes: a redundancy status acquisition subunit, a first status testing subunit, a second status testing subunit, a third status testing subunit, and a fourth status testing subunit, wherein:

[0200] The redundancy status acquisition subunit is used to acquire the current redundancy status, which includes network redundancy status and device redundancy status.

[0201] The first state test subunit is used to obtain the number of drivers under test and the current tag number value of the drivers under test during the monitoring period if there is no network redundancy state or device redundancy state in the current redundancy state, and determine the tag number alarm state based on the number of drivers under test and the corresponding current tag number value.

[0202] The second state test subunit is used to execute a preset first redundancy configuration program and obtain the current tag number value of the driver to be tested if only the network redundancy state exists in the current redundancy state, and determine the tag number alarm state based on the current tag number value; the first redundancy configuration program includes the network redundancy configuration program.

[0203] The third state test subunit is used to execute a preset second redundancy configuration program and obtain the current tag number value of the driver to be tested if only the device redundancy state exists in the current redundancy state, and determine the tag number alarm state based on the current tag number value; the second redundancy configuration program includes the device redundancy configuration program.

[0204] The fourth state test subunit is used to execute a preset third redundancy configuration program and obtain the current tag number value of the driver to be tested if there is a network redundancy state and a device redundancy state in the current redundancy state, and determine the tag number alarm state based on the current tag number value; the third redundancy configuration program includes a network redundancy configuration program and a device redundancy configuration program.

[0205] In one embodiment, the driver testing module 730 includes an interface testing unit, which includes: a modification testing subunit, used to obtain at least one modification object; obtain the modification testing method corresponding to the modification object in the interface testing method, and perform driver testing on the driver to be tested according to the modification testing method to obtain the driver testing result of the driver to be tested; the modification testing method includes a control station modification testing method, wherein the control station modification testing method includes a parameter verification method, a redundancy testing method, and a network testing method.

[0206] In one embodiment, the modified test subunit is further configured to acquire a redundant test signal and acquire a redundant configuration status based on the redundant test signal; acquire a device interrupt signal and acquire a device operating status based on the device interrupt signal; the device operating status includes the on or off status of at least one computer device; acquire the current tag number value and the current tag number alarm status, and acquire a redundant test result based on the current tag number value, the current tag number alarm status, the redundant configuration status, and the device operating status.

[0207] In one embodiment, the modified test subunit is also used to obtain the current drive configuration and import the current drive configuration; refresh the configuration status and tag number status; obtain the current tag number and store the current tag number as the tag number under the current drive configuration.

[0208] In one embodiment, when the driver test request includes at least two drivers to be tested; the runtime state test unit further includes an initial data acquisition subunit, a modification and acquisition subunit, and a runtime state test subunit, wherein:

[0209] The initial data acquisition subunit is used to acquire the initial driver test data of the second driver to be tested; the initial driver test data includes the initial tag number value and the initial tag number alarm status of the second driver to be tested.

[0210] The modification and acquisition sub-unit is used to modify the driver configuration of the first driver under test and acquire the current driver test data of the second driver under test and other drivers under test; the current driver test data includes the current tag number value and current tag number alarm status of the second driver under test; the drivers under test include the first driver under test and the second driver under test.

[0211] The runtime status test subunit is used to obtain runtime status test results based on the initial driver test data and the current driver test data of the second driver to be tested.

[0212] Each module in the aforementioned drive testing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0213] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 8 As shown, the computer device includes a processor, memory, and a network interface connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores driver test cases. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a driver test method.

[0214] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 8 As shown, the computer device includes a processor, memory, communication interface, display screen, and input device connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a driver testing method.

[0215] Those skilled in the art will understand that Figure 8 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0216] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0217] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0218] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0219] Those skilled in the art will understand that implementing all or part of the processes in the drive testing methods provided in the above embodiments can be accomplished by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0220] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0221] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A driving test method, characterized in that, The method includes: Obtain a driver test request; the driver test request includes the driver to be tested and the test type. Based on the test type, obtain the corresponding driver test cases in the target test method; the target test method includes at least one pre-stored driver test case, and the driver test case includes a performance test method, an interface test method, and a runtime status test method; Based on the driver test cases, driver testing is performed on the driver to be tested to obtain the driver test results of the driver to be tested; The performance testing method includes the following steps: Acquire driver test data; the driver test data includes multiple driver test parameters, the driver test parameters include the current bit number value of the driver under test and the write value information corresponding to each current bit number value; Determine whether each driver test parameter in the driver test data conforms to the preset parameter setting rules, and obtain the determination result; The alarm status of the tag number is determined based on the judgment result, and the drive performance test results are obtained based on the alarm status of the tag number. The operational status testing method also includes: Obtain the current redundancy status, which includes network redundancy status and device redundancy status; If there is no network redundancy or device redundancy in the current redundancy status, then obtain the number of drivers to be tested running during the monitoring period and the current tag number value of the drivers to be tested, and determine the tag number alarm status based on the number of drivers to be tested and the corresponding current tag number value. If only network redundancy exists in the current redundancy state, then the preset first redundancy configuration program is executed and the current bit number value of the driver to be tested is obtained, and the bit number alarm state is determined based on the current bit number value; the first redundancy configuration program includes the network redundancy configuration program; If only device redundancy exists in the current redundancy state, then a preset second redundancy configuration program is executed and the current tag number value of the driver to be tested is obtained, and the tag number alarm state is determined based on the current tag number value; the second redundancy configuration program includes a device redundancy configuration program; If the current redundancy status includes both network redundancy and device redundancy, then a preset third redundancy configuration program is executed and the current tag number value of the driver to be tested is obtained. Based on the current tag number value, the tag number alarm status is determined. The third redundancy configuration program includes a network redundancy configuration program and a device redundancy configuration program.

2. The method according to claim 1, characterized in that, The operational status testing method includes the following steps: The current operating period of the monitoring and control device is obtained; the current operating period is either the configuration period or the monitoring period; the monitoring and control device is used to perform drive testing on the driver to be tested. If the current running period is the configuration period, then check whether the driver configuration has been saved; if not, output an alarm message. If the current running period is a monitoring period, then the system checks whether the current tag value data of the driver under test is correct and whether the current running status of the driver under test is normal, and outputs the detection results.

3. The method according to claim 1, characterized in that, The interface testing method includes: modifying the testing method, wherein the driver testing based on the driver test cases to obtain the driver test results of the driver to be tested includes: Get at least one modified object; Obtain the modification test method corresponding to the modified object in the interface test method, and perform driver testing on the driver to be tested according to the modification test method to obtain the driver test result of the driver to be tested; the modification test method includes a control station modification test method, wherein the control station modification test method includes a parameter verification method, a redundancy test method, and a network test method.

4. The method according to claim 3, characterized in that, The redundancy testing method includes the following steps: Obtain the redundancy test signal, and obtain the redundancy configuration status based on the redundancy test signal; Obtain a device interrupt signal and obtain the device operating status based on the device interrupt signal; the device operating status includes the on or off status of at least one computer device; Obtain the current tag number value and the current tag number alarm status, and obtain the redundancy test results based on the current tag number value, the current tag number alarm status, the redundancy configuration status, and the device operating status.

5. The method according to claim 3, characterized in that, The modification test method also includes a bit number modification test method, which includes the following steps: Obtain the current driver configuration and import it. Refresh the configuration status and tag number status; Obtain the current bit number and store it as the bit number under the current drive configuration.

6. The method according to claim 1, characterized in that, When the driver test request includes at least two drivers to be tested, the runtime state test method further includes: Obtain the initial driver test data of the second driver to be tested; the initial driver test data includes the initial tag number value and the initial tag number alarm status of the second driver to be tested; Modify the driver configuration of the first driver to be tested, and obtain the current driver test data of the second driver to be tested and other drivers to be tested; the current driver test data includes the current bit number value and current bit number alarm status of the second driver to be tested; the drivers to be tested include the first driver to be tested and the second driver to be tested. Based on the initial driver test data and the current driver test data of the second driver to be tested, obtain the running status test results.

7. A driving test device, characterized in that, The device includes: The first acquisition module is used to acquire driver test requests; the driver test request includes the driver to be tested and the test type. The second acquisition module is used to acquire the corresponding driver test cases in the target test method based on the test type; the target test method includes at least one pre-stored driver test case, and the driver test case includes a performance test method, an interface test method, and a runtime status test method; The driver testing module is used to perform driver testing on the driver under test based on the driver test cases, and obtain the driver test results of the driver under test. The performance testing method includes the following steps: Acquire driver test data; the driver test data includes multiple driver test parameters, the driver test parameters include the current bit number value of the driver under test and the write value information corresponding to each current bit number value; Determine whether each driver test parameter in the driver test data conforms to the preset parameter setting rules, and obtain the determination result; The alarm status of the tag number is determined based on the judgment result, and the drive performance test results are obtained based on the alarm status of the tag number. The operational status testing method also includes: Obtain the current redundancy status, which includes network redundancy status and device redundancy status; If there is no network redundancy or device redundancy in the current redundancy status, then obtain the number of drivers to be tested running during the monitoring period and the current tag number value of the drivers to be tested, and determine the tag number alarm status based on the number of drivers to be tested and the corresponding current tag number value. If only network redundancy exists in the current redundancy state, then the preset first redundancy configuration program is executed and the current bit number value of the driver to be tested is obtained, and the bit number alarm state is determined based on the current bit number value; the first redundancy configuration program includes the network redundancy configuration program; If only device redundancy exists in the current redundancy state, then a preset second redundancy configuration program is executed and the current tag number value of the driver to be tested is obtained, and the tag number alarm state is determined based on the current tag number value; the second redundancy configuration program includes a device redundancy configuration program; If the current redundancy status includes both network redundancy and device redundancy, then a preset third redundancy configuration program is executed and the current tag number value of the driver to be tested is obtained. Based on the current tag number value, the tag number alarm status is determined. The third redundancy configuration program includes a network redundancy configuration program and a device redundancy configuration program.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

Images