Automatic instrument testing method, device and equipment, storage medium and program product

Abstract

The invention relates to an automatic instrument testing method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: configuring a test task for a to-be-tested instrument to obtain a configured test task; issuing the configured test task to target test execution software; receiving test data corresponding to a test task uploaded by the target test execution software; and displaying the test data corresponding to the test task. Therefore, the problems that the testing workload of various types of instruments and meters is large and the testing modes cannot be unified are solved. For instruments and meters supporting the HART communication protocol, the equipment descriptor files of different equipment are imported, so that different types of instruments can be efficiently tested while the visual configuration of the test case is realized, and the test efficiency and accuracy are remarkably improved.

Description

Technical Field

[0001] This application relates to the technical field of instruments and meters, and particularly to an instrument automation testing method, device, computer device, computer-readable storage medium, and computer program product. Background Art

[0002] For manufacturers that produce various types of instruments and meters (such as transmitters, flow meters, positioners, etc.), a large number of tests need to be carried out on various types of equipment during the R & D process.

[0003] In traditional technologies, test cases are generally written separately for each type of instrument. However, this processing method not only takes a huge amount of time, but also requires a large amount of repeated testing work during version iteration. Even with the assistance of an automated testing program, a dedicated program still needs to be developed for each type of instrument, which undoubtedly brings a heavy workload to testers and R & D personnel.

[0004] In addition, the current testing methods, testing processes, and test results lack centralized management, resulting in low efficiency. Summary of the Invention

[0005] Based on this, in view of the above technical problems, it is necessary to provide an instrument automation testing method, device, computer device, computer-readable storage medium, and computer program product that can reduce the testing workload of various types of instruments and meters and unify the testing method.

[0006] In a first aspect, this application provides an instrument automation testing method, including: Configuring a test task for the instrument to be tested to obtain a configured test task; Sending the configured test task to a target test execution software; Receiving test data corresponding to the test task uploaded by the target test execution software; Displaying the test data corresponding to the test task.

[0007] In one embodiment, the configuring a test task for the instrument to be tested to obtain a configured test task includes: Assembling test cases corresponding to the instrument to be tested; Performing parameter configuration and method configuration on each step of the test case based on at least one device descriptor file; Batch importing each step with completed parameter configuration according to a preset template to obtain a configured test task.

[0008] In one embodiment, the performing parameter configuration and method configuration on each step of the test case based on at least one device descriptor file includes: For each step, select at least one parameter from the device descriptor file to set the parameter information; wherein, the setting types of the parameter information include any one of: fixed value, random value, and formula value; For each step, select at least one method from the device descriptor file to configure the method information; For each step, set the test expected value to a fixed value or reference the result value of the previous step.

[0009] In one embodiment, after the configured test task is sent to the target test execution software, the method further includes: Parse the test cases corresponding to the configured test task through the target test execution software to obtain the specific content of each step in the test cases; Generate test step instructions through the target test execution software according to the specific content of each step in the test cases; Send the test step instructions to the HART communication hand-held controller through the target test execution software for execution; Receive the test task execution result feedback by the HART communication hand-held controller through the target test execution software.

[0010] In one embodiment, before receiving the test data corresponding to the test task uploaded by the target test execution software, the method further includes: Judge the test task execution result feedback by the HART communication hand-held controller through the target test execution software according to the set test expected value to determine whether the corresponding test step passes the test; Record the test data corresponding to each test step through the target test execution software, and the test data includes: execution time, execution result, and whether the test passes.

[0011] In one embodiment, before receiving the test task execution result feedback by the HART communication hand-held controller through the target test execution software, the method further includes: Construct a HART command through the HART communication hand-held controller according to the parameter information and method information in the test cases; Send the HART command to the specified HART instrument based on the HART communication line through the HART communication hand-held controller to control the HART instrument to execute the test; Receive the reply command returned by the HART instrument based on the HART communication line through the HART communication hand-held controller; The HART communication handheld device parses the reply command and performs data format conversion according to the format specifications described in the device descriptor file to obtain the test task execution result in a standardized format; When an exception occurs during the test, the HART communication handheld device returns the information corresponding to the exception to the target test execution software.

[0012] In a second aspect, the present application also provides an instrument automation test management platform, including: A configuration module for configuring test tasks for the instrument to be tested to obtain the configured test tasks; A distribution module for distributing the configured test tasks to the target test execution software; A receiving module for receiving the test data corresponding to the test tasks uploaded by the target test execution software; A display module for displaying the test data corresponding to the test tasks.

[0013] In a third aspect, the present application also provides an instrument automation test system, including the instrument automation test management platform described in the second aspect, as well as a target test execution software and a HART communication handheld device; The target test execution software is used to parse the test cases corresponding to the configured test tasks to obtain the specific content of each step in the test cases, and generate test step instructions according to the specific content of each step in the test cases, and send the test step instructions to the HART communication handheld device for execution; The HART communication handheld device is used to control the HART instrument to perform the test and feedback the test task execution result to the target test execution software; The target test execution software is also used to generate the test data corresponding to the test tasks according to the test task execution result and upload the test data corresponding to the test tasks to the instrument automation test management platform.

[0014] In a fourth aspect, the present application also provides a computer device, including a memory and a processor, where the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented: Configure test tasks for the instrument to be tested to obtain the configured test tasks; Send the configured test tasks to the target test execution software; Receive the test data corresponding to the test tasks uploaded by the target test execution software; Display the test data corresponding to the test tasks.

[0015] Fifth aspect, the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented: Configure a test task for the instrument to be tested to obtain a configured test task; Send the configured test task to the target test execution software; Receive the test data corresponding to the test task uploaded by the target test execution software; Display the test data corresponding to the test task.

[0016] Sixth aspect, the present application also provides a computer program product, including a computer program, and when the computer program is executed by a processor, the following steps are implemented: Configure a test task for the instrument to be tested to obtain a configured test task; Send the configured test task to the target test execution software; Receive the test data corresponding to the test task uploaded by the target test execution software; Display the test data corresponding to the test task.

[0017] The above-mentioned instrument automation test method, device, computer device, computer-readable storage medium and computer program product configure a test task for the instrument to be tested to obtain a configured test task; send the configured test task to the target test execution software; receive the test data corresponding to the test task uploaded by the target test execution software; display the test data corresponding to the test task. Thereby solving the problems of large test workload and inability to unify test methods for various types of instruments and meters. For instruments and meters that support the HART communication protocol, the embodiments of the present application can efficiently test different types of instruments while realizing the visual configuration of test cases by importing device descriptor (DD) files of different devices, significantly improving the test efficiency and accuracy. Description of the Drawings

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the following will briefly introduce the drawings required for use in the description of the embodiments of the present application or related technologies. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0019] Figure 1 It is a schematic flowchart of the instrument automation test method in an embodiment; Figure 2Schematic diagram of the process of the instrument automation test method in another embodiment; Figure 3 Schematic diagram of the process of the instrument automation test method in yet another embodiment; Figure 4 Schematic diagram of the data interaction principle of the instrument automation test method in one embodiment; Figure 5 In one embodiment, the fusion Figures 1 to 3 Schematic diagram of the process of the instrument automation test method shown; Figure 6 Schematic diagram of the display interface for configuring test cases in one embodiment; Figure 7 Schematic diagram of the display interface for executing the test process in one embodiment. Detailed implementation manners

[0020] In order to make the objectives, technical solutions and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0021] In order to more clearly illustrate the technical solutions of the present application, the following brief descriptions are made on the technical terms appearing in the present application: 1) Device Descriptor (DD) file: used to describe information such as the model, manufacturer, device functions and parameters of HART devices, so as to facilitate the host software to identify, configure and operate the devices.

[0022] 2) The HART communication protocol is a digital communication protocol used to transmit digital information on a 4 - 20 mA current loop. Through the HART protocol, the device can transmit analog signals and digital information simultaneously, realizing functions such as remote monitoring, parameter configuration, diagnosis and management of the device, and improving the reliability and usage efficiency of the device.

[0023] Exemplarily, as Figure 1 shown, an instrument automation test method is provided, which is applied to an automation test management platform. The method in this embodiment may include the following steps: Step S101, configure a test task for the instrument to be tested to obtain a configured test task.

[0024] In this embodiment, the automation test management platform has the function of pre - importing DD files of multiple instruments. When configuring an automation test task for a new instrument, the primary step is to establish test cases based on this instrument. These test cases are composed of multiple test steps, and each step allows the tester to select one or more parameters and methods from the DD file.

[0025] It should be understood that in the above step S101, a test case set can be pre-constructed based on multiple test cases. When configuring a test task, test cases can be searched for or referenced from these pre-established test case sets to combine and obtain the test task. Thus, unified management of test cases is achieved, and the configuration efficiency of test tasks is improved.

[0026] Exemplarily, the test cases corresponding to the instrument to be tested can be described by the automated test management platform component; based on at least one device descriptor file, parameter configuration and method configuration are performed on each step of the test case; each step with parameter configuration completed is batch-imported according to a preset template to obtain a configured test task.

[0027] In this embodiment, for each step, at least one parameter is selected from the device descriptor file for parameter information setting; wherein, the setting types of the parameter information include any one of a fixed value, a random value, and a formula value; for each step, at least one method is selected from the device descriptor file for method information configuration; for each step, the test expected value is set to a fixed value or the result value of a previous step is referenced.

[0028] It should be noted that when configuring parameters, the parameter value can be set to a fixed value, a random value, or a formula value, providing a high degree of flexibility.

[0029] In addition, the test expected value can also be set to a fixed value or the result value of a previous step is referenced, enhancing the diversity and relevance of the test. To further improve efficiency, the automated test management platform also supports batch-importing test steps through a template, simplifying the configuration process of complex test scenarios.

[0030] Step S102: Send the configured test task to the target test execution software.

[0031] In this embodiment, when configuring a test task, the tester can select and combine existing test cases, and each test task is flexibly composed of multiple test case groups. The configured test task will be sent to the test execution software with a specific serial number.

[0032] Step S103: Receive the test data corresponding to the test task uploaded by the target test execution software.

[0033] In this embodiment, after the execution software completes the task, it will upload the test result back to the automated test management platform.

[0034] Step S104: Display the test data corresponding to the test task.

[0035] In this embodiment, the automated test management platform will intuitively display the execution results of these test tasks, facilitating the viewing and analysis by testers.

[0036] In this embodiment, by configuring test tasks for the instruments to be tested, the configured test tasks are obtained; the configured test tasks are sent to the target test execution software; the test data corresponding to the test tasks uploaded by the target test execution software is received; and the test data corresponding to the test tasks is displayed. Thereby, the problems of large test workload and non-unified test methods for various types of instruments are solved. For the instruments supporting the HART communication protocol, in the embodiment of the present application, by importing the device descriptor files of different devices, while realizing the visual configuration of test cases, different types of instruments can be efficiently tested, significantly improving the test efficiency and accuracy.

[0037] Exemplarily, as Figure 2 shown, another instrument automated test method is provided, which is applied to the target test execution software. After the configured test tasks are sent to the target test execution software, the method in this embodiment may include the following steps: Step S201: Analyze the test cases corresponding to the configured test tasks to obtain the specific content of each step in the test cases.

[0038] In this embodiment, after receiving the test execution task, the target test execution software will first analyze the test cases and detail the specific content of each test step.

[0039] Step S202: Generate test step instructions according to the specific content of each step in the test cases.

[0040] In this embodiment, the target test execution software processes the specific content of each step to generate test step instructions.

[0041] Step S203: Send the test step instructions to the HART communication handheld controller for execution.

[0042] In this embodiment, the target test execution software sends the generated test step instructions to the HART communication handheld controller for execution. After receiving the instructions, the HART communication handheld controller will execute the corresponding test steps as required and feedback the execution results to the test execution software in real time.

[0043] Step S204: Receive the test task execution results feedback by the HART communication handheld controller.

[0044] Optionally, before receiving the test data corresponding to the test task uploaded by the target test execution software, the method further includes: using the target test execution software to judge the execution result of the test task fed back by the HART communication handheld terminal according to the set test expectation value, and determining whether the corresponding test step passes the test; using the target test execution software to record the test data corresponding to each test step, where the test data includes: execution time, execution result, and whether the test passes.

[0045] In this embodiment, after receiving the result returned by the HART communication handheld terminal, the test execution software will judge the execution result of the test step according to the preset test expectation value (such as a fixed value, the value of the foregoing step, etc.) to determine whether the step passes the test. At the same time, the test execution software will also record in detail the test data of each step, including but not limited to information such as the execution time, execution result, and whether it passes of the test step, so as to facilitate subsequent data analysis and problem tracking.

[0046] In addition, for abnormal situations or failed steps that occur during the test, the test execution software will also make special marks and records to ensure the accuracy and integrity of the test results.

[0047] Exemplarily, as Figure 3 shown, another instrument automation test method is provided, which is applied to the HART communication handheld terminal. Before receiving the test task execution result fed back by the HART communication handheld terminal through the target test execution software, the method in this embodiment may include the following steps: Step S301: Construct a HART command according to the parameter information and method information in the test case.

[0048] In this embodiment, multiple instrument DD files are pre-installed inside the HART communication handheld terminal, which enables it to intelligently select and parse the corresponding DD file according to the device type specified in the test case. During the test, the HART communication handheld terminal will accurately construct a HART command according to the parameter information and method information configured in the test case.

[0049] Step S302: Send the HART command to the specified HART instrument via the HART communication line to control the HART instrument to execute the test.

[0050] In this embodiment, the HART commands generated in step S301 are then sent to the specified HART instrument via the HART communication line to perform corresponding test operations.

[0051] Step S303: Receive the reply command returned by the HART instrument via the HART communication line.

[0052] In this embodiment, after the HART instrument receives and finishes executing a command, it returns a corresponding reply command through the HART communication line. Among them, the HART instrument refers to an instrument that supports HART communication. When the instrument supporting HART communication receives a relevant HART command, it performs relevant actions.

[0053] Step S304: According to the format specifications described in the device descriptor file, parse the reply command and perform data format conversion to obtain the test task execution result in a standardized format.

[0054] In this embodiment, after the HART communication handheld device receives these reply commands, it will again use the format specifications described in the DD file to accurately parse the reply commands. After completion of the parsing, the HART communication handheld device will return the converted data to the test execution software in a standardized format.

[0055] Optionally, when an exception occurs during the test, the information corresponding to the exception is returned to the target test execution software through the HART communication handheld device.

[0056] In this embodiment, the test execution software can accurately evaluate these test task execution results and generate corresponding test results. In addition, if any exceptions or errors are encountered during the test, the HART communication handheld device will also return this information to the test execution software for subsequent problem analysis and processing.

[0057] Exemplarily, as Figure 4 shown, the data interaction principle among the automated test management platform, the test execution software, the HART communication handheld device, and the HART instrument is given.

[0058] Exemplarily, as Figure 5 shown, integrating the instrument automated test method shown above Figures 1 to 3 can include the following steps: 1) Import the device DD file on the automated test management platform; 2) Configure the test cases of the device; 3) Configure the test tasks of the device; 4) The test execution software obtains the test tasks; 5) Execute the test tasks; 6) Send the test step content to the HART communication handheld device; 7) The HART communicator packets the HART commands; 8) Send the commands to the device (instrument); 9) The instrument replies with the HART commands after execution; 10) The HART communicator parses the HART commands; 11) The execution result of the test step is sent back to the test execution software; 12) Whether the test steps included in the test task are completed. If not, return to step 5); if so, execute step 13); 13) Upload the test results to the automated test management platform; 14) Store the test results; 15) Display the test results.

[0059] Exemplarily, Figure 6 shows the display interface for configuring test cases, Figure 7 shows the display interface for executing the test process.

[0060] This embodiment solves the problems of large test volume and difficult-to-unify test methods existing in the test work of various instruments and meters. By importing the DD file of the device, the visual configuration of test cases and test tasks for multiple different types of instruments is realized; the unified management of test cases is realized.

[0061] The method in this embodiment can repeatedly run the configured test cases in the iterative tests of multiple versions; automatically record the feedback data during the test process, and visually display the test results. These features together ensure the efficiency, accuracy, and convenience of the entire test process, significantly saving time and labor costs.

[0062] It should be understood that although the steps in the flowcharts involved in the above-described embodiments are sequentially shown according to the arrows, these steps do not necessarily need to be executed in the order indicated by the arrows. Unless there is a clear description in this article, there is no strict order limit for the execution of these steps, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages do not necessarily need to be executed at the same moment, but can be executed at different moments, and the execution order of these steps or stages does not necessarily need to be sequential, but can be executed alternately or in turn with at least a part of other steps or steps or stages in other steps.

[0063] Based on the same inventive concept, the embodiments of the present application also provide an instrument automated test device for implementing the above-mentioned instrument automated test method. The implementation solutions for solving problems provided by this device are similar to those recorded in the above method. Therefore, the specific limitations in one or more embodiments of the instrument automated test device provided below can refer to the limitations on the instrument automated test method in the above text, and will not be repeated here.

[0064] Exemplarily, an embodiment of the present application further provides an instrument automation test device, and the device includes: A configuration module, configured to configure a test task for an instrument to be tested to obtain a configured test task; A distribution module, configured to distribute the configured test task to a target test execution software; A receiving module, configured to receive test data corresponding to the test task uploaded by the target test execution software; A display module, configured to display the test data corresponding to the test task.

[0065] Exemplarily, the configuration module is specifically configured to: assemble test cases corresponding to the instrument to be tested; perform parameter configuration and method configuration on each step of the test cases based on at least one device descriptor file; and batch import each step with completed parameter configuration according to a preset template to obtain a configured test task.

[0066] Exemplarily, the configuration module is specifically configured to: for each step, select at least one parameter from the device descriptor file for parameter information setting; wherein the setting type of the parameter information includes any one of a fixed value, a random value, and a formula value; for each step, select at least one method from the device descriptor file for method information configuration; and set the test expected value to a fixed value or reference the result value of a previous step.

[0067] Exemplarily, in the above device: the target test execution software parses the test cases corresponding to the configured test task to obtain the specific content of each step in the test cases; the target test execution software generates test step instructions according to the specific content of each step in the test cases; the target test execution software distributes the test step instructions to a HART communication handheld device for execution; and the target test execution software receives the test task execution result feedback by the HART communication handheld device.

[0068] Exemplarily, in the above device: the target test execution software determines whether the corresponding test step passes the test by judging the test task execution result feedback by the HART communication handheld device according to the set test expected value; and the target test execution software records the test data corresponding to each test step, where the test data includes: execution time, execution result, and whether the test passes.

[0069] Exemplarily, in the above device: the HART communication handheld operator constructs a HART command according to the parameter information and method information in the test case; the HART communication handheld operator sends the HART command to a specified HART instrument based on the HART communication line to control the HART instrument to execute the test; the HART communication handheld operator receives a reply command returned by the HART instrument based on the HART communication line; the HART communication handheld operator parses and converts the data format of the reply command according to the format specification described in the device descriptor file to obtain a test task execution result in a standardized format; when an exception occurs during the test, the HART communication handheld operator returns information corresponding to the exception to the target test execution software.

[0070] Each module in the above instrument automation test device can be implemented in whole or in part by software, hardware, and their combination. Each of the above modules can be embedded in or independent of a processor in a computer device in the form of hardware, or stored in a memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0071] In an exemplary embodiment, an instrument automation test system is provided, including the above instrument automation test management platform, as well as a target test execution software and a HART communication handheld operator; The target test execution software is used to parse the test case corresponding to the configured test task, obtain the specific content of each step in the test case, generate a test step instruction according to the specific content of each step in the test case, and send the test step instruction to the HART communication handheld operator for execution; The HART communication handheld operator is used to control the HART instrument to execute the test and feedback the test task execution result to the target test execution software; The target test execution software is further used to generate test data corresponding to the test task according to the test task execution result and upload the test data corresponding to the test task to the instrument automation test management platform.

[0072] Exemplarily, the target test execution software is specifically used to judge whether the corresponding test step passes the test according to the set test expectation value for the test task execution result fed back by the HART communication handheld operator; record the test data corresponding to each test step, where the test data includes: execution time, execution result, and whether the test passes.

[0073] Exemplarily, the HART communication handheld terminal is specifically configured to construct a HART command according to the parameter information and method information in the test case; send the HART command to a specified HART instrument via a HART communication line to control the HART instrument to execute the test; receive a reply command returned by the HART instrument via the HART communication line; parse and perform data format conversion on the reply command according to the format specification described in the device descriptor file to obtain a test task execution result in a standardized format. When an exception occurs during the test, information corresponding to the exception is returned to the target test execution software.

[0074] In an exemplary embodiment, a computer device is provided, and the computer device may be a server. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O), and a communication interface. Among them, the processor, the memory, and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The input / output interface of the computer device is used to exchange information between the processor and external devices. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, it implements an instrument automation test method.

[0075] In an exemplary embodiment, a computer device is provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, the steps in the above method embodiments are implemented.

[0076] In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0077] In an embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the steps in the above method embodiments are implemented.

[0078] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant regulations.

[0079] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, database, or other medium used in the embodiments provided in this application can include at least one of non-volatile memory 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), magnetoresistive 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 be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The databases involved in the embodiments provided in this application can include at least one of relational databases and non-relational databases. Non-relational databases can include distributed databases based on blockchain, etc., and are not limited thereto. The processors involved in the embodiments provided in this application can be general-purpose processors, central processors, graphics processors, digital signal processors, programmable logic devices, data processing logics based on quantum computing, artificial intelligence (AI) processors, etc., and are not limited thereto.

[0080] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, 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, it should be considered as the scope recorded in this application.

[0081] The above-described embodiments merely represent several implementation manners of this application. The description is relatively specific and detailed, but it should not be construed as a limitation on the patent scope of this application. It should be noted that for those of ordinary skill in the art, without departing from the concept of this application, several modifications and improvements can still be made, and these all belong to the protection scope of this application. Therefore, the protection scope of this application should be subject to the appended claims.

Claims

1. An instrument automation testing method, characterized in that: The method comprises: Configure the test task for the instrument to be tested and obtain the configured test task; Sending the configured test task to the target test execution software; Receiving test data corresponding to the test task uploaded by the target test execution software; The test data corresponding to the test task is displayed.

2. The method according to claim 1, characterized in that The step of configuring a test task for the instrument to be tested to obtain a configured test task includes: The test cases corresponding to the instrument to be tested described in the component; Performing parameter configuration and method configuration on each step of the test case based on at least one device descriptor file; Import all steps of parameter configuration in batches according to the preset template to obtain the configured test tasks.

3. The method according to claim 2, characterized in that The performing parameter configuration and method configuration on each step of the test case based on at least one device descriptor file includes: For each step, at least one parameter is selected from the device descriptor file to set parameter information; wherein the setting type of the parameter information includes: any one of a fixed value, a random value, and a formula value; For each step, at least one method is selected from the device descriptor file to configure method information; for each step, the test expected value is set as a fixed value or a result value of a previous step is referenced.

4. The method according to any one of claims 1 to 3, characterized in that: After sending the configured test task to the target test execution software, the method further includes: Parsing the test case corresponding to the configured test task through the target test execution software to obtain the specific content of each step in the test case; Generate test step instructions according to the specific content of each step in the test case through the target test execution software; The test step instructions are sent to the HART communication handheld operator for execution through the target test execution software; The test task execution result fed back by the HART communication handheld operator is received through the target test execution software.

5. The method according to claim 4, characterized in that Before receiving the test data corresponding to the test task uploaded by the target test execution software, the method further includes: The target test execution software judges the test task execution result fed back by the HART communication handheld operator according to the set test expectation value to determine whether the corresponding test step passes the test; The target test execution software records the test data corresponding to each test step, and the test data includes: execution time, execution result, and whether the test is passed.

6. The method according to claim 4, characterized in that Before receiving the test task execution result fed back by the HART communication handheld operator through the target test execution software, the method further includes: Constructing a HART command according to the parameter information and method information in the test case through the HART communication handheld operator; The HART communication handheld operator sends the HART command to a designated HART instrument based on a HART communication line to control the HART instrument to perform a test; Receiving, through the HART communication handheld operator, a reply command returned by the HART instrument based on the HART communication line; The HART communication handheld operator parses and converts the reply command into a data format according to the format specification described in the device descriptor file to obtain the test task execution result in a standardized format; When an abnormality occurs during the test, information corresponding to the abnormality is returned to the target test execution software through the HART communication manual.

7. An instrument automated test management platform, characterized in that: include: Configuration module, used to configure test tasks for the instrument to be tested and obtain the configured test tasks; A sending module is used to send the configured test task to the target test execution software; A receiving module, used to receive test data corresponding to the test task uploaded by the target test execution software; The display module is used to display the test data corresponding to the test task.

8. An instrument automation test system, characterized in that: It includes the instrument automated test management platform as described in claim 7, as well as target test execution software and a HART communication handheld operator; The target test execution software is used to parse the test case corresponding to the configured test task, obtain the specific content of each step in the test case, generate a test step instruction according to the specific content of each step in the test case, and send the test step instruction to the HART communication handheld operator for execution; The HART communication handheld operator is used to control the HART instrument to perform the test and to feed back the test task execution result to the target test execution software; The target test execution software is also used to generate test data corresponding to the test task according to the test task execution result, and upload the test data corresponding to the test task to the instrument automation test management platform.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images