An automated testing method and system for an intelligent command and control system at a container terminal.

Abstract

An automated testing method for a container terminal intelligent command and control system includes: displaying an attribute verification interactive interface; determining whether a front-end element node verification request has been received; if so, retrieving first verification data corresponding to the front-end element node verification request from the cache database and the front-end interface corresponding to the front-end element node; retrieving second verification data corresponding to the front-end node verification request from the system database of the terminal operating system; displaying the front-end display interface corresponding to the front-end element node; specifying the display element node corresponding to the front-end element node in the front-end display interface; obtaining the attributes of the display element node to generate third verification data; determining whether the first verification data, second verification data, and third verification data are the same; if they are the same, the attribute verification is considered successful; and a system is also provided. This invention can ensure the data consistency of the terminal operating system.

Description

Technical Field

[0001] This invention belongs to the field of automated terminal technology, specifically, it relates to an automated testing method and an automated testing system for an intelligent command and control system for container terminals. Background Technology

[0002] An automated terminal is a container terminal that can achieve fully automated control of container pickup, storage, loading, and unloading operations. A container terminal includes at least four functional areas, arranged sequentially from the roadside to the seaside: a gate, a container yard, an area for in-yard transfer vehicles, and a gantry crane operation area. Operations within the container yard are carried out by a combination of Automated Guided Vehicles (AGVs), container trucks, and rail-mounted gantry cranes.

[0003] The management and scheduling of automated terminals are implemented by the terminal operating system. This system collects various information and physical parameters within the automated terminal, configures rail-mounted gantry cranes to interact with container trucks entering the container yard on the landside, and automatically executes container retrieval or storage operations based on target locations provided by the terminal operating system. It also automatically stacks containers in the stacking area and interacts with transfer vehicles within the yard in the seaside interaction area, automatically executing loading or unloading operations based on the stacking positions of containers awaiting shipment. Due to the massive throughput and handling volume of automated terminals, the terminal operating system typically uses a cached database to improve system performance and reduce the pressure on the database server, especially in high-concurrency scenarios. However, given the various complex yard states and container attributes, issues such as data loss and inconsistencies between the cached database and the system database can arise during operation. Failure to identify these issues in a timely manner can disrupt the entire automated terminal operation process, reduce loading and unloading efficiency, and cause significant economic losses.

[0004] The information disclosed in this background section is only intended to enhance the understanding of the background technology of this application, and therefore may include prior art that is not known to those skilled in the art. Summary of the Invention

[0005] In response to the problems that may arise in the terminal operating system of automated terminals under high-concurrency scenarios, such as missing data (including yard status and container attributes) and inconsistencies between cached database and system database, if these problems are not identified in time, the entire operation process of the automated terminal may be disrupted, loading and unloading efficiency may be reduced, or incorrect manual intervention may occur. The first aspect of this invention provides an automated testing method for an intelligent command and control system for container terminals.

[0006] An automated testing method for an intelligent command and control system for container terminals includes the following steps:

[0007] Display an attribute verification interactive interface; wherein, the attribute verification interactive interface is configured to input a front-end element node verification request, the front-end element node verification request corresponds to a front-end element node, and the front-end element node includes at least one container attribute, and / or at least one vehicle attribute, and / or at least one spreader attribute;

[0008] Determine whether at least one front-end element node verification request has been received;

[0009] If so, then the first verification data corresponding to the front-end element node verification request is obtained from the cache database and the front-end interface corresponding to the front-end element node according to the front-end element node verification request.

[0010] Based on the front-end element node verification request, the second verification data corresponding to the front-end node verification request is obtained from the system database of the dock operating system.

[0011] Display the front-end interface corresponding to the front-end element nodes;

[0012] Specify the display element node in the front-end display interface that corresponds to the front-end element node;

[0013] Obtain the attributes of the displayed element node to generate third verification data;

[0014] Determine whether the first verification data, the second verification data, and the third verification data are the same;

[0015] If they are the same, the attribute validation is considered successful.

[0016] A second aspect of the present invention provides an automated testing system for an intelligent command and control system of a container terminal, comprising: a first display module, the first display module being configured to display an attribute verification interactive interface; wherein, the attribute verification interactive interface is configured to input a front-end element node verification request, the front-end element node verification request corresponding to a front-end element node, the front-end element node including at least one container attribute, and / or at least one vehicle attribute, and / or at least one spreader attribute;

[0017] The first determination module is configured to determine whether at least one front-end element node verification request has been received.

[0018] The first acquisition module is configured to, after the first determination module determines that at least one front-end element node verification request has been received, acquire first verification data corresponding to the front-end element node verification request from the cache database and the front-end interface corresponding to the front-end element node according to the front-end node verification request.

[0019] The second acquisition module is configured to, after the first determination module determines that at least one front-end element node verification request has been received, acquire second verification data corresponding to the front-end node verification request from the system database of the dock operating system according to the front-end element node verification request.

[0020] The second display module is configured to display the front-end display interface corresponding to the front-end element node after the first determination module determines that at least one front-end element node verification request has been received.

[0021] A specified module is configured to specify the display element node in the front-end display interface that corresponds to the front-end element node.

[0022] The third acquisition module is configured to acquire the attributes of the display element node to generate third verification data; and

[0023] The second determination module is configured to determine whether the first verification data, the second verification data, and the third verification data are the same; if they are the same, the attribute verification is determined to be successful.

[0024] Compared with the prior art, the advantages and positive effects of the present invention are:

[0025] The automated testing method for an intelligent command and control system of a container terminal provided by this invention offers an automated testing approach that performs one-click detection of complex container, vehicle, and spreader attributes in automated terminals. This accurately and efficiently detects data inconsistencies, ensuring data consistency between the cache database, the front-end display interface, and the system database under high-concurrency scenarios. It also identifies missing data, avoids inconsistencies between the cache and system databases, prevents disruptions to the automated terminal's operational processes, and guarantees loading and unloading efficiency. Furthermore, it prevents the front-end display interface from showing incorrect data, thus avoiding erroneous manual intervention. The automated testing method for an intelligent command and control system of a container terminal provided by this invention can improve the operational stability of automated terminals.

[0026] Other features and advantages of the present invention will become clearer after reading the detailed embodiments of the invention in conjunction with the accompanying drawings. Attached Figure Description

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

[0028] Figure 1A flowchart of the first embodiment of the automated testing method for the intelligent command and control system of container terminals provided by the present invention;

[0029] Figure 2 A flowchart of some steps in the second embodiment of the automated testing method for the intelligent command and control system of a container terminal provided by the present invention;

[0030] Figure 3 A flowchart of some steps in the third embodiment of the automated testing method for the intelligent command and control system of a container terminal provided by the present invention;

[0031] Figure 4 A schematic block diagram of the first embodiment of the automated testing system for the intelligent command and control system of container terminals provided by the present invention;

[0032] Figure 5 This is a schematic block diagram of the second embodiment of the automated testing system for the intelligent command and control system of container terminals provided by the present invention. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments.

[0034] It should be noted that in the description of this invention, the terms "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," which indicate directional or positional relationships, are based on the directional or positional relationships shown in the accompanying drawings. These are merely for ease of description and do not indicate or imply that the device or element must have a specific orientation, or be constructed and operated in a specific orientation; therefore, they should not be construed as limitations on this invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0035] To address issues that arise in automated terminal operating systems under high-concurrency scenarios, such as missing data (including yard status and container attributes) and inconsistencies between cached and system databases, failure to promptly identify these problems can disrupt the entire automated terminal's operational flow, lead to erroneous manual intervention, and reduce loading and unloading efficiency. One embodiment of this invention provides an automated testing method for an intelligent command and control system for container terminals. This method includes, for example, the following... Figure 1 The steps are shown.

[0036] Step S101: Display the attribute verification interactive interface.

[0037] The verification interface is configured to interact with users (usually operators) and receive verification requests for front-end element nodes input by the user. The verification interface is preferably configured on a server, a computer running at least one application of the terminal operating system, or other intelligent terminals capable of performing the same function. The verification interface may be configured with button elements, input box elements, or other similar elements to receive user-input verification requests for front-end element nodes. The terminal operating system is configured with a system database and a cache database to handle high-concurrency system requirements. The container terminal intelligent command and control system can be a subsystem of the terminal operating system or an independent system.

[0038] Each front-end element node verification request corresponds to a front-end element node, which includes at least one container attribute, and / or at least one vehicle attribute, and / or at least one spreader attribute. For example, an operator can generate a first front-end element node verification request using a first button element to verify the container attribute, or generate a second front-end element node verification request using a second button element to verify the vehicle attribute, or generate a third front-end element node verification request using a third button element to verify the spreader attribute.

[0039] The following is an illustrative description of the operation of an automated container terminal. An automated container terminal is configured with gates, container yards, in-yard transfer vehicle operating areas, and gantry crane operating areas arranged sequentially from the land side to the sea side. Gates determine whether off-yard transport vehicles, typically container trucks, are allowed to enter or leave the yard. Gates verify parameters for entering and leaving vehicles and containers, including but not limited to the vehicle's physical license plate number, electronic license plate number, container number, container type, number of containers, container position on the pallet, door orientation, whether the container is damaged, driver identification (via RFID), and vehicle weight. The container yard comprises multiple parallel sub-yards. Each sub-yard includes a land-side interaction area, a stacking operation area, and a sea-side interaction area, arranged sequentially from the land side to the sea side. Rail-mounted gantry cranes traverse the sub-yards and move back and forth along their length, performing container pickup, storage, and stacking operations at target locations. Rail-mounted gantry cranes typically include land-side and sea-side cranes. For example, if a land-side crane receives a container storage task, its empty spreader travels to the target location, picks up the container from an off-site transport vehicle, and places it in the designated stacking position, completing the storage operation. In the sea-side interaction area, the sea-side rail-mounted crane interacts with automated guided vehicles (AGVs) (yard transfer vehicles). For example, the sea-side rail-mounted crane retrieves the container to be loaded onto the ship from the container yard and places it in the target location. The yard transfer vehicle automatically travels to the target location, lifts the container, and travels within the yard transfer vehicle's operating area until it transfers the container to the gantry crane's operating area. The gantry crane then loads the container from the AVT onto the ship.

[0040] As can be seen from the exemplary operation process of the automated terminal described above, the automatic control largely relies on the comparison results of sensor detection data and target data retrieved from the system database and / or cache database. For example, it determines the identity of containers, the legitimacy of vehicle identities, whether spreaders have reached the target location, and whether container trucks and automated guided vehicles have reached the target location. Operators, on the other hand, determine the correctness of attributes based on the data displayed on the terminal operating system's front-end interface and actively intervene in control. If the data in the system database and / or cache database is incorrect, or the data on the front-end display interface is incorrect, there is a high risk of erroneous control. To ensure that the data in the system database, cache database, and displayed interface are identical and correct, the attribute verification method for the automated terminal provided by this invention can automatically verify any one of the front-end element nodes. It is easy to understand that multiple front-end element nodes can also be automatically verified sequentially, meaning that operators can actively choose to automatically verify one or more front-end element nodes.

[0041] Step S102: Determine whether at least one front-end element node verification request has been received.

[0042] Step S103: If a front-end element node verification request is received, the first verification data corresponding to the front-end element node verification request is obtained from the cache database and the front-end interface corresponding to the front-end element node according to the front-end element node verification request.

[0043] Step S104: On the other hand, if a front-end element node verification request is received, the second verification data corresponding to the front-end node verification request is obtained from the system database of the dock operating system according to the front-end element node verification request.

[0044] Step S105: Display the front-end display interface corresponding to the front-end element node.

[0045] Step S106: Automatically specify the display element node corresponding to the front-end element node in the front-end display interface.

[0046] Step S107: Obtain the attributes of the displayed element node to generate third verification data.

[0047] The above steps will be further explained using the container attribute as an example of a front-end element node. Container attributes include one or more of the following: category attribute, release attribute, port of discharge attribute, dangerous goods container attribute, oversized container attribute, tank container attribute, container type attribute, high cube container attribute, refrigerated container attribute, prohibited movement attribute, and bay allocation attribute; among which the category attribute includes: storage or retrieval.

[0048] Based on the front-end element node verification request, the first verification data corresponding to the front-end element node verification request is obtained from the cache database and the front-end interface corresponding to the front-end element node. That is, the container attribute data (such as the corresponding bits in the control command) is read from the cache database using the read command, which is the first verification data.

[0049] Retrieving the second verification data corresponding to the front-end node verification request from the system database of the dock operating system based on the front-end element node verification request may include the following steps:

[0050] The system uses a filter algorithm to select all containers in the yard from the system database and then retrieves the container attributes of each container to generate second verification data. A container in the yard refers to a container located in any sub-yard within the yard. The filter algorithm can be a mature algorithm from the existing technology, which is not the focus of this invention and will not be further described here.

[0051] The front-end display interface corresponding to the front-end element nodes is displayed. For example, it displays the front-end display interface generated and displayed by the terminal operating system during normal operation, corresponding to the container yard. This interface can show any front-end element node within the yard, such as the container attributes of containers in the yard that can be viewed directly, clicked, or paused. The front-end display interface can be a bay view window. In this embodiment, the Selenium framework is used to specify each container in the yard as a corresponding display element node in the front-end display interface, and the front-end category attributes of each display element node are obtained to generate third-party verification data. In this step, Selenium, as a tool for element manipulation, simulates manual operation, automatically obtaining the container attributes of the containers in the yard that are displayed as display element nodes, and using the obtained front-end category attributes of each display element node as third-party verification data. The entire process is executed automatically without manual intervention.

[0052] Step S108: Determine whether the first verification data, the second verification data, and the third verification data are the same. For example, a comparison verification can be performed between the front-end display interface and the database to check whether the second verification data and the third verification data are the same, and obtain the inconsistent data; further, a comparison verification can be performed between the cache database and the front-end display interface to check whether the first verification data and the third verification data are the same, such as the container release attributes, type attributes (placement or removal), and bay allocation attributes, and obtain the inconsistent data.

[0053] Step S109: If they are the same, the attribute verification is considered successful, indicating that the attributes and the front-end and back-end databases have good consistency and the data interaction is accurate, which can ensure the smooth execution of subsequent related control processes of the automated terminal.

[0054] The automated testing method for an intelligent command and control system of a container terminal provided by this invention, also known as an attribute verification method for automated terminals, offers an automated testing approach. This method performs one-click detection of complex container, vehicle, and spreader attributes in automated terminals, accurately and efficiently detecting data inconsistencies. It ensures data consistency between the cache database, the front-end display interface, and the system database under high-concurrency scenarios, promptly identifying missing data and avoiding inconsistencies between the cache and system databases. This prevents disruptions to the automated terminal's operational processes and reduces loading and unloading efficiency. It also avoids displaying incorrect personnel on the front-end display interface, preventing erroneous manual intervention. The automated testing method for an intelligent command and control system of a container terminal provided by this invention can improve the operational stability of automated terminals.

[0055] See Figure 2In a preferred embodiment of the present invention, a further design is made for the processing method when there are at least two different verification data among the first verification data, the second verification data and the third verification data.

[0056] Step S201: Determine that at least two of the first verification data, second verification data, and third verification data are different. For example, the release attributes of the same bin in the system database, cache database, and front-end display interface are different, with one being "allowed to release" and the other two being "disallowed to release". For example, the difference in release attributes can be reflected in the different values ​​of the corresponding flag bits in the first verification data, second verification data, and third verification data.

[0057] Step S202: Save the first verification data, the second verification data, and the third verification data.

[0058] Step S203: Keep the front-end element node validation request unchanged.

[0059] Step S204: Repeat the steps from obtaining the first verification data corresponding to the front-end element node verification request from the cache database and the front-end interface corresponding to the front-end element node according to the front-end element node verification request, to obtaining the attributes of the display element node to generate the third verification data.

[0060] Step S205: Determine whether the first verification data, the second verification data, and the third verification data obtained again are the same.

[0061] Step S206: If the first verification data, the second verification data, and the third verification data obtained again are the same, the attribute verification is determined to be successful, and the initial determination of momentary inconsistency is recorded.

[0062] In an optional implementation, the number of instances of transient inconsistency is accumulated. If the accumulated number of transient inconsistencies exceeds a set number within a set detection period, it indicates that the current cache database update period is unreasonable, meaning that when data is retrieved, the data in the system database has not yet been updated in the cache database. Therefore, in a preferred implementation, when the accumulated number of transient inconsistencies exceeds a set number, the step of correcting the current cache database update period is automatically executed; and in the next set detection period, it is determined whether the accumulated number of transient inconsistencies exceeds a set number; if the accumulated number of transient inconsistencies is less than a set number, the corrected cache database update period is determined to be reasonable, and the cache database is updated according to the corrected cache database update period in subsequent control, realizing automatic system correction. If the accumulated number of transient inconsistencies still exceeds a set number, the cache database update period is corrected again until the accumulated number of transient inconsistencies is less than a set number. When adjusting the current cache database update period, a set time value can be invoked, and the sum of the original update period and the set time value is used as the corrected cache database update period. The set time value can be a positive or negative value.

[0063] Step S208: If at least two of the first, second, and third verification data obtained again are different, an error log is generated to prompt the operator to conduct a detailed investigation and processing.

[0064] In a preferred embodiment, after generating the error log, the following step is further included: disabling control flow based on front-end element nodes until the updated first verification data, second verification data, and third verification data are identical. For example, if the release attributes of containers at the same bay location differ in the system database, cache database, and front-end display interface—one being "release allowed" and the other two "release not allowed"—then container access operations at that bay location are temporarily prohibited until the updated first verification data, second verification data, and third verification data are identical after manual intervention, at which point the prohibition control is lifted.

[0065] In a preferred embodiment, the automated testing method for the intelligent command and control system of container terminals provided by the present invention can be adapted to different terminal operating systems. Specifically, such as... Figure 3 As shown, optionally, before displaying the attribute verification interactive interface, the following steps are also included: obtaining the environment variable configuration of the dock operating system; determining whether the user's permissions meet the set verification permissions; if they do, displaying the attribute verification interactive interface, allowing interaction with the user (usually an operator), and receiving the front-end element node verification request input by the user; otherwise, prohibiting interaction with the user (usually an operator).

[0066] A second aspect of the present invention provides an automated testing system for an intelligent command and control system for container terminals. For example... Figure 4 As shown, the automated testing system for the intelligent command and control system of the container terminal includes:

[0067] The first display module 101 is configured to display an attribute verification interactive interface; wherein, the attribute verification interactive interface is configured to input a front-end element node verification request, the front-end element node verification request corresponds to a front-end element node, and the front-end element node includes at least one container attribute, and / or at least one vehicle attribute, and / or at least one spreader attribute;

[0068] The first determination module 102 is configured to determine whether at least one front-end element node verification request has been received.

[0069] The first acquisition module 103 is configured to, after the first determination module 102 determines that at least one front-end element node verification request has been received, obtain the first verification data corresponding to the front-end element node verification request from the cache database and the front-end interface corresponding to the front-end element node according to the front-end node verification request.

[0070] The second acquisition module 104 is configured to, after the first determination module 102 determines that at least one front-end element node verification request has been received, obtain the second verification data corresponding to the front-end node verification request from the system database of the dock operating system according to the front-end element node verification request.

[0071] The second display module 105 is configured to display the front-end display interface corresponding to the front-end element node after the first determination module 102 determines that at least one front-end element node verification request has been received.

[0072] Specify module 106, and configure module 106 to be the display element node in the specified front-end display interface that corresponds to the front-end element node;

[0073] The third acquisition module 107 is configured to acquire the attributes of the displayed element nodes to generate third verification data; and

[0074] The second determination module 108 is configured to determine whether the first verification data, the second verification data, and the third verification data are the same; if they are the same, the attribute verification is determined to be successful.

[0075] like Figure 5 As shown, in a preferred embodiment, the automated testing system for the intelligent command and control system of the container terminal further includes:

[0076] The re-verification module 209 is configured to, when the second determination module 108 determines that at least two of the first verification data, second verification data, and third verification data are different, save the first verification data, second verification data, and third verification data while keeping the front-end element node verification request unchanged, and then sequentially execute the steps from obtaining the first verification data corresponding to the front-end element node verification request from the cache database and the front-end interface corresponding to the front-end element node to obtaining the attributes of the display element node to generate the third verification data, and determine whether the first verification data, second verification data, and third verification data obtained again are the same; if they are the same, the attribute verification is determined to be successful.

[0077] The first recording module 210 records an initial determination of momentary inconsistency when the re-verification module 209 determines that the newly acquired first verification data, second verification data, and third verification data are identical; and

[0078] The second recording module 211 and the first recording module 210 generate and record an error log when the re-verification module 209 determines that at least two of the first verification data, the second verification data, and the third verification data obtained again are different.

[0079] In a preferred embodiment, the automated testing system for the intelligent command and control system of the container terminal further includes a disabling module, which is configured to disable the control flow based on the front-end element node after the second recording module 211 generates and records the error log until the updated first verification data, second verification data and third verification data are the same.

[0080] In a preferred embodiment, the front-end element node is a container attribute, which includes one or more of the following: category attribute, release attribute, port of discharge attribute, dangerous goods container attribute, oversized container attribute, tank container attribute, container type attribute, high cube container attribute, refrigerated container attribute, prohibited movement attribute, and bay space allocation attribute.

[0081] The second acquisition module 104 is configured to call a filter algorithm to filter out all on-site containers from the system database, and obtain the container attributes of all on-site containers one by one to generate the second verification data;

[0082] The third acquisition module 107 is configured to use the Selenium framework to specify each present box as a corresponding display element node in the front-end display interface, and acquire the front-end category attribute of each display element node to generate the third verification data.

[0083] In a preferred embodiment, the automated testing system for the intelligent command and control system of the container terminal further includes: a permission verification module, which is configured to obtain the environment variable configuration of the terminal's operating system and determine whether the user's permissions meet the set verification permissions; if they do, the attribute verification interactive interface is displayed.

[0084] This application also provides a computer storage medium, wherein the computer storage medium stores an electronic data interchange computer program that causes a computer to perform some or all of the steps of any of the methods described in the above method embodiments.

[0085] 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 of other embodiments.

[0086] 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 system embodiments described above are merely illustrative; for instance, the division of units or modules described above is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical or other forms.

[0087] The units described above 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 physical space or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0088] 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.

[0089] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions claimed by the present invention.

Claims

1. A container wharf intelligent command management and control system automation test method, Characterized in that, It comprises the following steps: Display attribute verification interactive interface; wherein, the attribute verification interactive interface is configured to input the front-end element node verification request, the front-end element node verification request corresponds to a front-end element node, and the front-end element node comprises at least one container attribute, and / or at least one vehicle attribute, and / or at least one spreader attribute; Determine whether at least one front-end element node verification request is received; If yes, according to the front-end element node verification request, the first verification data corresponding to the front-end element node verification request is obtained from the cache database and the front-end interface corresponding to the front-end element node; According to the front-end element node verification request, the second verification data corresponding to the front-end element node verification request is obtained from the system database of the terminal operation system; Display the front-end display interface corresponding to the front-end element node; Assign the display element node corresponding to the front-end element node in the front-end display interface; Get the attribute of the display element node to generate the third verification data; Determine whether the first verification data, the second verification data and the third verification data are the same; If the same, it is determined that the attribute verification is successful.

2. The container terminal intelligent command control system automatic test method according to claim 1, characterized in that, After determining whether the first verification data, the second verification data and the third verification data are the same, the following steps are further included: If there are at least two different first verification data, second verification data and third verification data, save the first verification data, the second verification data and the third verification data; Keep the front-end element node verification request unchanged; Again, execute the steps of obtaining the first verification data, the second verification data and the third verification data from the cache database and the front-end interface corresponding to the front-end element node in turn according to the front-end element node verification request in sequence; Determine whether the first verification data, the second verification data and the third verification data obtained again are the same; If the first verification data, the second verification data and the third verification data obtained again are the same, it is determined that the attribute verification is successful, and the first determination is recorded as transient inconsistency; If there are at least two different first verification data, second verification data and third verification data obtained again, generate an error log.

3. The container terminal intelligent command control system automatic test method according to claim 2, characterized in that, After generating the error log, the following steps are further included: Prohibit the control flow based on the front-end element node until the updated first verification data, the second verification data and the third verification data are the same.

4. The container wharf intelligent command management and control system automation test method according to any one of claims 1 to 3, characterized in that, The front-end element node is a container attribute, and the container attribute comprises one or more of the following attributes: category attribute, release attribute, unloading port attribute, dangerous goods box attribute, oversize box attribute, tank box attribute, box type attribute, high box attribute, cold box attribute, prohibited movement attribute and berth allocation attribute; The second verification data corresponding to the front-end element node verification request is obtained from the system database of the terminal operating system according to the front-end element node verification request, and specifically includes the following steps: All present containers are filtered out from the system database by calling a filter algorithm, and the container properties of all present containers are obtained one by one to generate second verification data; The display element node corresponding to the front-end element node in the front-end display interface is specified, and the properties of the display element node are obtained to generate third verification data, specifically including the following steps: Each present container is specified as a corresponding display element node in the front-end display interface by using a selenium framework, and the front-end category properties of each display element node are obtained to generate third verification data.

5. The automatic testing method of the container terminal intelligent command control system according to claim 4, characterized in that, Before the attribute verification interaction interface is displayed, the following steps are further included: Obtaining the environment variable configuration of the terminal operating system; Determining whether the user's authority meets the set verification authority; If yes, the attribute verification interaction interface is displayed.

6. A container wharf intelligent command management and control system automatic test system, characterized in that, It includes: A first display module configured to display an attribute verification interaction interface; wherein the attribute verification interaction interface is configured to input a front-end element node verification request, the front-end element node verification request corresponds to a front-end element node, and the front-end element node includes at least one container property, and / or at least one vehicle property, and / or at least one spreader property; A first determination module configured to determine whether at least one front-end element node verification request is received; A first obtaining module configured to, after the first determination module determines that at least one front-end element node verification request is received, obtain first verification data corresponding to the front-end element node verification request from a front-end interface corresponding to the front-end element node in a cache database according to the front-end element node verification request; A second obtaining module configured to, after the first determination module determines that at least one front-end element node verification request is received, obtain second verification data corresponding to the front-end element node verification request from a system database of a terminal operating system according to the front-end element node verification request; A second display module configured to, after the first determination module determines that at least one front-end element node verification request is received, display a front-end display interface corresponding to the front-end element node; A specifying module configured to specify a display element node corresponding to the front-end element node in the front-end display interface; A third obtaining module configured to obtain the properties of the display element node to generate third verification data; and A second determination module configured to determine whether the first verification data, the second verification data, and the third verification data are the same; if yes, it is determined that the attribute verification is successful.

7. The container wharf intelligent command control system automatic test system according to claim 6, characterized in that, It further includes: a re-verification module, configured to, when the second determination module determines that there are at least two differences among the first verification data, the second verification data and the third verification data, save the first verification data, the second verification data and the third verification data and keep the front-end element node verification request unchanged, execute again the steps of sequentially obtaining the first verification data corresponding to the front-end element node verification request from the cache database and the front-end interface corresponding to the front-end element node, obtaining the display element node attribute to generate the third verification data, and determining whether the first verification data, the second verification data and the third verification data obtained again are the same; if yes, determining that the attribute verification is successful; a first recording module, configured to record that the first determination is transient inconsistency when the re-verification module determines that the first verification data, the second verification data and the third verification data obtained again are the same; and a second recording module, configured to generate and record an error log when the re-verification module determines that there are at least two differences among the first verification data, the second verification data and the third verification data obtained again.

8. The container wharf intelligent command control system automatic test system according to claim 7, characterized in that, Further comprising: a disabling module, configured to disable the control flow based on the front-end element node until the first verification data, the second verification data and the third verification data obtained again are the same after the second recording module generates and records the error log.

9. The automatic test system of the container wharf intelligent command control system according to any one of claims 6 to 8, characterized in that: the front-end element node is a container attribute, and the container attribute comprises one or more of a category attribute, a release attribute, an unloading port attribute, a dangerous goods container attribute, an oversize container attribute, a tank container attribute, a container type attribute, a high container attribute, a cold container attribute, a prohibited movement attribute and a berth allocation attribute; the second obtaining module is configured to call a filter algorithm to screen all present containers from the system database and obtain the container attributes of all the present containers to generate the second verification data; the third obtaining module is configured to use a selenium framework to specify each present container as a corresponding display element node in the front-end display interface, obtain the front-end category attribute of each display element node to generate the third verification data.

10. The container wharf intelligent command control system automatic test system according to claim 9, wherein, Further comprising: a permission verification module, configured to obtain an environment variable configuration of a wharf operating system, and determine whether a user permission meets a set verification permission; if yes, an attribute verification interactive interface is displayed.

Images