A flowchart automation testing method and device for a DCS control system

Abstract

The application discloses a flowchart automation testing method and device for a DCS control system, and the method comprises the following steps: importing a preset flowchart template in a flowchart configuration interface of the DCS control system, and multiple cells with the same size are divided in the flowchart template; receiving an input instruction, adding graphics in each cell based on the input instruction, and setting characteristic data for each graphic based on the input instruction, wherein the characteristic data comprises dynamic characteristic data and static characteristic data; determining a test case according to the characteristic category of each characteristic data, testing the characteristic data based on the test case, and generating a flowchart test result. The application can automatically test and verify the dynamic characteristics and static characteristics of each graphic in the constructed flowchart, the test process does not need manual participation, the test efficiency is high, and the test result is more accurate.

Description

Technical Field

[0001] This application relates to the field of software testing technology, and more specifically, to an automated testing method and apparatus for flowcharts of a DCS control system. Background Technology

[0002] Distributed Control Systems (DCS) are comprehensive control systems that have emerged with the rise of automation in modern large-scale industrial production and the increasing complexity of process control requirements. Flowcharts are one of the most important monitoring and operation screens in a DCS control system, used to display the overall process flow and operating status of the controlled equipment, and to manipulate related data. They contain various graphics and controls. After the flowchart is constructed, it needs to be tested. Currently, the testing method is manual testing, which involves manually building different test scenarios and manually testing the combination of dynamic and static characteristics of each graphic. This often consumes a lot of testing resources and has low testing efficiency. Summary of the Invention

[0003] To address the aforementioned issues, this application provides an automated testing method and apparatus for flowcharts of a DCS control system.

[0004] In a first aspect, embodiments of this application provide an automated testing method for flowcharts of a DCS control system, the method comprising:

[0005] Import a preset flowchart template into the flowchart configuration interface of the DCS control system. The flowchart template is divided into multiple cells of the same size.

[0006] Receive input instructions, add graphics to each of the cells based on the input instructions, and set characteristic data for each graphic based on the input instructions, the characteristic data including dynamic characteristic data and static characteristic data;

[0007] Test cases are determined based on the characteristic categories of each characteristic data, and the characteristic data is tested based on the test cases to generate flowchart test results.

[0008] Preferably, before importing the preset flowchart template into the flowchart configuration interface of the DCS control system, the method further includes:

[0009] Receive the first operation instruction, and set multiple boundary lines in the blank template according to the first operation instruction to obtain the flowchart template.

[0010] Preferably, the flowchart template is further divided into button cells, and each cell is further divided into a description area for describing the characteristic data;

[0011] After setting characteristic data for each of the graphics based on the input instructions, the method further includes:

[0012] Based on the input command, set response action data for each button cell;

[0013] Obtain the descriptive text information of the characteristic data and display the descriptive text information in the description area.

[0014] Preferably, the method further includes:

[0015] The cell coordinates of each cell are determined based on the boundary lines in the flowchart template, and a cell number is assigned to each cell coordinate.

[0016] Based on the boundary lines in the flowchart template, determine the button grid coordinates of each button grid and assign a button grid number to each button grid coordinate.

[0017] Preferably, the step of determining test cases based on the characteristic categories of each of the characteristic data, and testing the characteristic data based on the test cases, includes:

[0018] Test cases are determined based on the characteristic categories of each of the aforementioned characteristic data;

[0019] Identify the minimum bounding rectangle of each of the aforementioned shapes, and determine the graphic parameter data of the shapes based on the minimum bounding rectangle;

[0020] The characteristic data is tested based on the test cases and graphical parameter data.

[0021] Preferably, the flowchart test results include a first flowchart test result and a second flowchart test result;

[0022] The generated flowchart test results include:

[0023] When the test result of the graphical parameter data does not match the preset result of the test case, a first flowchart test result is generated, and the first flowchart test result indicates that the test has failed.

[0024] When the test result of the graphical parameter data matches the preset result of the test case, a second flowchart test result is generated, and the second flowchart test result indicates that the test was successful.

[0025] Secondly, embodiments of this application provide an automated testing device for flowcharts of a DCS control system, the device comprising:

[0026] The import module is used to import a preset flowchart template into the flowchart configuration interface of the DCS control system. The flowchart template is divided into multiple cells of the same size.

[0027] A receiving module is used to receive input instructions, add graphics to each of the cells based on the input instructions, and set characteristic data for each graphic based on the input instructions, wherein the characteristic data includes dynamic characteristic data and static characteristic data;

[0028] The testing module is used to determine test cases based on the characteristic categories of each characteristic data, test the characteristic data based on the test cases, and generate flowchart test results.

[0029] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the method provided as in the first aspect or any possible implementation of the first aspect.

[0030] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method provided as in the first aspect or any possible implementation thereof.

[0031] The beneficial effects of this invention are: it can automatically test and verify the dynamic and static characteristics of each graphic in the constructed flowchart, the testing process does not require manual intervention, the testing efficiency is high, and the test results are more accurate. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 A flowchart illustrating an automated testing method for a DCS control system provided in this application embodiment;

[0034] Figure 2 This application provides a schematic diagram of the structure of an automated testing device for a DCS control system flowchart.

[0035] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0036] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0037] In the following description, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance. The following description provides multiple embodiments of this application, which can be substituted or combined with each other. Therefore, this application can also be considered to include all possible combinations of the same and / or different embodiments described. Thus, if one embodiment includes features A, B, and C, and another embodiment includes features B and D, then this application should also be considered to include embodiments containing one or more other possible combinations of A, B, C, and D, even if such embodiments are not explicitly described in the following text.

[0038] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the described elements without departing from the scope of this application. Various processes or components may be appropriately omitted, substituted, or added to the examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into other examples.

[0039] See Figure 1 , Figure 1 This is a flowchart illustrating an automated testing method for a DCS control system provided in an embodiment of this application. In this embodiment, the method includes:

[0040] S101. Import a preset flowchart template into the flowchart configuration interface of the DCS control system. The flowchart template is divided into multiple cells of the same size.

[0041] The entity executing this application may be the cloud server corresponding to the DCS control system.

[0042] In one embodiment of this application, a flowchart template is pre-created in the DCS control system. When a new flowchart needs to be created, the cloud server first imports the pre-set flowchart template into the flowchart configuration interface. At this time, the flowchart template only contains cells that are divided to place different graphics. The specific graphics and corresponding data within it need to be imported in a subsequent process.

[0043] In one possible implementation, before importing the preset flowchart template into the flowchart configuration interface of the DCS control system, the method further includes:

[0044] Receive the first operation instruction, and set multiple boundary lines in the blank template according to the first operation instruction to obtain the flowchart template.

[0045] In one embodiment of this application, the user will perform settings on the displayed blank template through the operation on the terminal, thereby generating a first operation instruction. After receiving the first operation instruction, the cloud server will respond to the first operation instruction and set the boundary lines in the blank template according to the first operation instruction, so that the blank template is divided into multiple cells by the boundary lines, and finally a flowchart template is obtained and saved.

[0046] S102. Receive input instructions, add graphics to each of the cells based on the input instructions, and set characteristic data for each graphic based on the input instructions. The characteristic data includes dynamic characteristic data and static characteristic data.

[0047] In one embodiment of this application, the user will place graphics in the flowchart template according to the specific needs of the newly created flowchart through operations on the terminal. The user's operation will generate input instructions. After receiving the input instructions, the cloud server will respond to the input instructions and add and set the corresponding graphics in each cell according to the input instructions, and assign characteristic data to each graphic.

[0048] In one possible implementation, the flowchart template is further divided into button cells, and each cell is further divided into a description area for describing the characteristic data.

[0049] After setting characteristic data for each of the graphics based on the input instructions, the method further includes:

[0050] Based on the input command, set response action data for each button cell;

[0051] Obtain the descriptive text information of the characteristic data and display the descriptive text information in the description area.

[0052] In one embodiment of this application, the final flowchart should be a graphical user tool that a user can directly operate and execute correct response actions. Therefore, the flowchart template will also include button cells, and each cell will have a description area, so that after the final flowchart is built, the user can perform actions such as writing values ​​and turning pages through the button cells. After setting the characteristic data for the graphic according to the input instructions, the response action data for the button cells will also be set according to the input instructions, and the descriptive text information of the characteristic data will be displayed in the description area.

[0053] In one possible implementation, the method further includes:

[0054] The cell coordinates of each cell are determined based on the boundary lines in the flowchart template, and a cell number is assigned to each cell coordinate.

[0055] Based on the boundary lines in the flowchart template, determine the button grid coordinates of each button grid and assign a button grid number to each button grid coordinate.

[0056] In one embodiment of this application, the boundary lines in the flowchart template are set according to the first operation instruction. The coordinates corresponding to each boundary line are determinable. Therefore, based on the position and coordinates of these boundary lines, the cell coordinates corresponding to each cell can be determined. The cell coordinates can be the coordinates of the cell's center point or the coordinate range of the cell area. After distinguishing each cell based on its coordinates, a different cell number can be assigned to each cell, so that in subsequent testing and use, only the number needs to be entered to determine the corresponding cell, without relying on coordinates. The same applies to button cell numbers.

[0057] S103. Determine test cases based on the characteristic categories of each characteristic data, and test the characteristic data based on the test cases to generate flowchart test results.

[0058] In one embodiment of this application, the characteristic data is categorized into different characteristics based on their meanings, such as horizontal movement, vertical movement, scaling, and filling. The data and operational steps required for testing differ depending on the characteristic category. The cloud server pre-stores multiple pre-defined test cases. Based on the characteristic category, the test case to be used in this test can be determined from these pre-defined test cases. A test case is a set of inputs, expected results, and operational steps, including the required input data, expected results, and execution steps. Based on the determined test cases, the user-defined characteristic data can be verified to determine if errors or anomalies exist, ultimately generating a flowchart test result.

[0059] In one possible implementation, step S103 includes:

[0060] Test cases are determined based on the characteristic categories of each of the aforementioned characteristic data;

[0061] Identify the minimum bounding rectangle of each of the aforementioned shapes, and determine the graphic parameter data of the shapes based on the minimum bounding rectangle;

[0062] The characteristic data is tested based on the test cases and graphical parameter data.

[0063] In one embodiment of this application, a minimum bounding rectangle public function can be set in the cloud server. This function can identify the minimum bounding rectangle of each graphic within a cell, thereby determining the specific coordinates and other graphic parameter data of the graphics in the 3x3 grid. This creates the prerequisites for verifying the static and dynamic attributes of the graphics. Finally, testing and verification will be performed based on test cases and graphic parameter data to determine whether the characteristic data is normal.

[0064] For example, the common functions that can be set in the flowchart script and their functions are shown in Table 1:

[0065]

[0066]

[0067] Table 1 shows the dynamic characteristics of the test cases and their verification methods, as shown in Table 2.

[0068]

[0069]

[0070]

[0071]

[0072] Table 2 shows the static characteristics of the test cases and their verification methods.

[0073]

[0074]

[0075]

[0076]

[0077]

[0078] Table 3

[0079] In one possible implementation, the flowchart test results include a first flowchart test result and a second flowchart test result;

[0080] The generated flowchart test results include:

[0081] When the test result of the graphical parameter data does not match the preset result of the test case, a first flowchart test result is generated, and the first flowchart test result indicates that the test has failed.

[0082] When the test result of the graphical parameter data matches the preset result of the test case, a second flowchart test result is generated, and the second flowchart test result indicates that the test was successful.

[0083] In one embodiment of this application, if the test result obtained by the graphical parameter data in the operation steps of the test case does not match the preset result of the test case, it is considered that there is an error in the flowchart setting, the test fails, and a first flowchart test result will be generated to inform the user that the test has failed; otherwise, it will be considered that the test has succeeded, and a second flowchart test result will be generated.

[0084] The following will be combined with the appendix Figure 2 This application provides a detailed description of the automated testing device for the DCS control system flowchart provided in its embodiments. It should be noted that the appendix... Figure 2 The flowchart of the DCS control system shown is used for the automated testing device to perform the test of this application. Figure 1 The methods shown in the embodiments are for illustrative purposes only, illustrating the parts relevant to the embodiments of this application. For specific technical details not disclosed, please refer to this application. Figure 1 The example shown.

[0085] Please see Figure 2 , Figure 2 This is a schematic diagram of the structure of an automated testing device for a DCS control system, as provided in an embodiment of this application. Figure 2 As shown, the device includes:

[0086] Import module 201 is used to import a preset flowchart template into the flowchart configuration interface of the DCS control system. The flowchart template is divided into multiple cells of the same size.

[0087] The receiving module 202 is used to receive input instructions, add graphics to each of the cells based on the input instructions, and set characteristic data for each graphic based on the input instructions, wherein the characteristic data includes dynamic characteristic data and static characteristic data;

[0088] The testing module 203 is used to determine test cases based on the characteristic categories of each characteristic data, test the characteristic data based on the test cases, and generate flowchart test results.

[0089] In one possible implementation, the device further includes:

[0090] The setting module is used to receive the first operation instruction and set multiple boundary lines in the blank template according to the first operation instruction to obtain the flowchart template.

[0091] In one possible implementation, the flowchart template is further divided into button cells, and each cell is further divided into a description area for describing the characteristic data.

[0092] The receiving module 202 also includes:

[0093] The first setting unit is used to set response action data for each button grid based on the input command;

[0094] The second acquisition unit is used to acquire the descriptive text information of the characteristic data and display the descriptive text information in the description area.

[0095] In one possible implementation, the device further includes:

[0096] The first sequence number allocation module is used to determine the cell coordinates of each cell based on the boundary lines in the flowchart template, and to assign a cell sequence number to each cell coordinate;

[0097] The second sequence number allocation module is used to determine the button grid coordinates of each button grid based on the boundary lines in the flowchart template, and to assign a button grid sequence number to each button grid coordinate.

[0098] In one possible implementation, the test module 203 includes:

[0099] The first determining unit is used to determine test cases based on the characteristic categories of each of the characteristic data.

[0100] The identification unit is used to identify the minimum bounding rectangle of each of the graphics and determine the graphic parameter data of the graphics based on the minimum bounding rectangle;

[0101] The test unit is used to test the characteristic data based on the test cases and graphical parameter data.

[0102] In one possible implementation, the flowchart test results include a first flowchart test result and a second flowchart test result;

[0103] Test module 203 also includes:

[0104] The first judgment unit is used to generate a first flowchart test result when the test result of the graphical parameter data does not match the preset result of the test case. The first flowchart test result indicates that the test has failed.

[0105] The second judgment unit is used to generate a second flowchart test result when the test result of the graphical parameter data matches the preset result of the test case. The second flowchart test result indicates that the test was successful.

[0106] Those skilled in the art will clearly understand that the technical solutions of the embodiments of this application can be implemented by means of software and / or hardware. In this specification, "unit" and "module" refer to software and / or hardware capable of independently completing or cooperating with other components to complete a specific function, wherein the hardware may be, for example, a Field-Programmable Gate Array (FPGA), an Integrated Circuit (IC), etc.

[0107] Each processing unit and / or module in the embodiments of this application can be implemented by an analog circuit that implements the functions described in the embodiments of this application, or by software that executes the functions described in the embodiments of this application.

[0108] See Figure 3 It shows a schematic diagram of the structure of an electronic device according to an embodiment of this application, which can be used to implement... Figure 1 The method in the illustrated embodiment. (As shown) Figure 3 As shown, the electronic device 300 may include: at least one central processing unit 301, at least one network interface 304, user interface 303, memory 305, and at least one communication bus 302.

[0109] The communication bus 302 is used to enable communication between these components.

[0110] The user interface 303 may include a display screen and a camera. Optionally, the user interface 303 may also include a standard wired interface and a wireless interface.

[0111] The network interface 304 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface).

[0112] The central processing unit 301 may include one or more processing cores. The central processing unit 301 connects to various parts within the electronic device 300 using various interfaces and lines. It executes various functions of the terminal 300 and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 305, and by calling data stored in the memory 305. Optionally, the central processing unit 301 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The central processing unit 301 may integrate one or a combination of several of the following: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content required for display on the screen; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the central processing unit 301 and may be implemented as a separate chip.

[0113] The memory 305 may include random access memory (RAM) or read-only memory. Optionally, the memory 305 may include a non-transitory computer-readable storage medium. The memory 305 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 305 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory 305 may also be at least one storage device located remotely from the aforementioned central processing unit 301. Figure 3 As shown, the memory 305, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and program instructions.

[0114] exist Figure 3In the illustrated electronic device 300, the user interface 303 is mainly used to provide an input interface for the user and to acquire user input data; while the central processing unit 301 can be used to call the flowchart automation test application of the DCS control system stored in the memory 305, and specifically perform the following operations:

[0115] Import a preset flowchart template into the flowchart configuration interface of the DCS control system. The flowchart template is divided into multiple cells of the same size.

[0116] Receive input instructions, add graphics to each of the cells based on the input instructions, and set characteristic data for each graphic based on the input instructions, the characteristic data including dynamic characteristic data and static characteristic data;

[0117] Test cases are determined based on the characteristic categories of each characteristic data, and the characteristic data is tested based on the test cases to generate flowchart test results.

[0118] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, DVDs, CD-ROMs, microdrives, as well as magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), or any type of medium or device suitable for storing instructions and / or data.

[0119] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0120] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

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

[0122] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0123] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0124] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0125] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0126] The foregoing description is merely an exemplary embodiment of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Those skilled in the art will readily conceive of embodiments of this disclosure upon considering the specification and practicing the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described herein. The specification and embodiments are to be considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.

Claims

1. An automated testing method for flowcharts of a DCS control system, characterized in that, The method includes: Import a preset flowchart template into the flowchart configuration interface of the DCS control system. The flowchart template is divided into multiple cells of the same size. Receive input instructions, add graphics to each of the cells based on the input instructions, and set characteristic data for each graphic based on the input instructions, the characteristic data including dynamic characteristic data and static characteristic data; Test cases are determined based on the characteristic categories of each characteristic data, and the characteristic data is tested based on the test cases to generate flowchart test results; Before importing the preset flowchart template into the flowchart configuration interface of the DCS control system, the method further includes: Receive the first operation instruction, and set multiple boundary lines in the blank template according to the first operation instruction to obtain the flowchart template; The flowchart template is also divided into button grids, and each cell is further divided into a description area for describing the characteristic data. After setting characteristic data for each of the graphics based on the input instructions, the method further includes: Based on the input command, set response action data for each button cell; Obtain descriptive text information of the characteristic data and display the descriptive text information in the description area; The method further includes: The cell coordinates of each cell are determined based on the boundary lines in the flowchart template, and a cell number is assigned to each cell coordinate. Based on the boundary lines in the flowchart template, determine the button grid coordinates of each button grid and assign a button grid number to each button grid coordinate.

2. The method according to claim 1, characterized in that, The step of determining test cases based on the characteristic categories of each characteristic data, and testing the characteristic data based on the test cases, includes: Test cases are determined based on the characteristic categories of each of the aforementioned characteristic data; Identify the minimum bounding rectangle of each of the aforementioned shapes, and determine the graphic parameter data of the shapes based on the minimum bounding rectangle; The characteristic data is tested based on the test cases and graphical parameter data.

3. The method according to claim 2, characterized in that, The flowchart test results include the first flowchart test results and the second flowchart test results; The generated flowchart test results include: When the test result of the graphical parameter data does not match the preset result of the test case, a first flowchart test result is generated, and the first flowchart test result indicates that the test has failed. When the test result of the graphical parameter data matches the preset result of the test case, a second flowchart test result is generated, and the second flowchart test result indicates that the test was successful.

4. An automated testing device for flowcharts of a DCS control system, characterized in that, The device includes: The import module is used to import a preset flowchart template into the flowchart configuration interface of the DCS control system. The flowchart template is divided into multiple cells of the same size. A receiving module is configured to receive input instructions, add graphics to each of the cells based on the input instructions, and set characteristic data for each graphic based on the input instructions, wherein the characteristic data includes dynamic characteristic data and static characteristic data; The testing module is used to determine test cases based on the characteristic categories of each characteristic data, test the characteristic data based on the test cases, and generate flowchart test results; The device also includes: The setting module is used to receive the first operation instruction and set multiple boundary lines in the blank template according to the first operation instruction to obtain the flowchart template. The flowchart template is also divided into button grids, and each cell is further divided into a description area for describing the characteristic data. The receiving module also includes: The first setting unit is used to set response action data for each button grid based on the input command; The second acquisition unit is used to acquire descriptive text information of the characteristic data and display the descriptive text information in the description area. The device also includes: The first sequence number allocation module is used to determine the cell coordinates of each cell based on the boundary lines in the flowchart template, and to assign a cell sequence number to each cell coordinate; The second sequence number allocation module is used to determine the button grid coordinates of each button grid based on the boundary lines in the flowchart template, and to assign a button grid sequence number to each button grid coordinate.

5. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1-3.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1-3.

Images