Automated testing method and system for intelligent command and control systems of container terminals

Abstract

An automated testing method for an intelligent command and control system of a container terminal includes the following steps: display an attribute verification interactive interface and determine whether a front-end element node verification request is received; if so, 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; 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; display a front-end display interface corresponding to the front-end element node; specify a display element node corresponding to the front-end element node in the front-end display interface; obtain attributes of the display element node to generate third verification data; determine whether the first verification data, second verification data, and third verification data are the same; and if they are the same, determine that the attribute verification is successful. An automated testing system is also provided. The present invention can ensure the consistency of data in a terminal operating system.

Description

[Technical Field]

[0001] The present invention relates to the technical field of automated terminals, and particularly to an automated testing method for an intelligent command and control system of a container terminal and an automated testing system for an intelligent command and control system of a container terminal. [Background technology]

[0002] An automated terminal is a container terminal that can achieve fully automated control of container unloading, storage, loading, and unloading operations. A container terminal includes at least four functional areas, in the order of gate, container yard, in-house guided vehicle operation area, and bridge crane work area, running from the road side to the sea side. Work within the container yard is completed through the cooperation of automated guided vehicles (AGVs), container trucks, and rail cranes.

[0003] The management and scheduling of automated terminals is achieved through a terminal operating system. It collects various information and physical parameters within the automated terminal, arranges rail cranes to interact with container trucks entering the container yard on the land side, automatically performs container unloading or storage operations according to the target positions provided by the terminal operating system, automatically loads containers in the loading area, and interacts with on-site transport vehicles in the seaside interaction area, automatically performing loading or unloading operations according to the loading positions of the containers being handled. Due to the large throughput and handling volume of automated terminals, terminal operating systems typically use cached databases to improve system performance and reduce the load on the database server, especially in scenarios with high concurrency. However, due to the diverse and complex nature of yard conditions and container attributes, problems such as missing data and data inconsistencies between the cache database and the system database can occur during use. If these problems are not identified in a timely manner, they can disrupt the overall operation of the automated terminal, reducing handling efficiency and causing serious economic losses.

[0004] The above information disclosed in this background art is intended only to deepen understanding of the background art of the present application, and may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] When the terminal operating system of an automated terminal is used in a situation where a large number of operations are being performed simultaneously, problems such as missing data (including yard status and container attributes) and inconsistencies in data between the cache database and the system database may occur. If these problems are not identified in a timely manner, they may disrupt the operation process of the entire automated terminal, reducing loading and unloading efficiency and causing incorrect manual intervention. In response to this, a first aspect of the present invention provides an automated testing method for an intelligent command and control system of a container terminal.

[0006] The automated test method for intelligent command and control systems of container terminals is displaying an attribute validation interactive interface configured to input a front-end element node validation request corresponding to one front-end element node, the front-end element node including at least one container attribute, at least one vehicle attribute, and / or at least one spreader attribute; determining whether at least one front-end element node validation request is received; If it is determined that the front-end element node verification request has been received, obtaining 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; According to the front-end element node verification request, obtaining second verification data corresponding to the front-end element node verification request from a system database of a terminal operating system; Displaying a front-end display interface corresponding to the front-end element node; specifying a display element node in the front-end display interface corresponding to the front-end element node; obtaining attributes of the display element nodes to generate third verification data; determining whether the first verification data, the second verification data, and the third verification data are the same; If they are the same, determining that the attribute verification was successful.

[0007] 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, a first determination module, a first acquisition module, a second acquisition module, a second display module, a designation module, a third acquisition module, and a second determination module, wherein the first display module is configured to display an attribute verification interactive interface, where the attribute verification interactive interface is configured to input a front-end element node verification request corresponding to one front-end element node, and the front-end element node includes at least one container attribute, at least one vehicle attribute, and / or at least one spreader attribute.

[0008] The first determination module is configured to determine whether at least one front-end element node validation request is received.

[0009] The first acquisition module is configured to acquire 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 after the first determination module determines that at least one front-end element node verification request has been received.

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

[0011] The second display module is configured to display a 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 is received.

[0012] The designation module is configured to designate a display element node in the front-end display interface corresponding to the front-end element node.

[0013] The third obtaining module is configured to obtain attributes of the display element node and generate third verification data.

[0014] The second determining module is configured to determine whether the first verification data, the second verification data, and the third verification data are the same, and if they are the same, determine that attribute verification is successful.

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

[0016] The automated testing method for an intelligent command and control system for a container terminal according to the present invention provides an automated testing method that can detect complex container attributes, vehicle attributes, and spreader attributes in an automated terminal with one click, accurately and efficiently detecting data inconsistencies. This ensures that the data in the cache database, front-end display interface, and system database are consistent in scenarios with a large number of concurrent executions, and identifies missing data. This avoids data inconsistencies between the cache database and the system database, preventing disruptions to the operation process of the automated terminal and ensuring cargo handling efficiency. It also prevents erroneous data from being displayed on the front-end display interface, which can lead to erroneous manual intervention. The automated testing method for an intelligent command and control system for a container terminal provided by the present invention can improve the operational stability of the automated terminal.

[0017] Other features and advantages of the present invention will become more apparent when the detailed description of the invention is read in conjunction with the accompanying drawings. [Brief explanation of the drawings]

[0018] In order to more clearly describe the technical solutions in the embodiments of the present invention, the drawings that need to be used in the embodiments are briefly described below. The drawings in the following description are only some embodiments of the present invention, and it is obvious to those skilled in the art that other drawings can be obtained based on these drawings without requiring creative efforts. [Figure 1] 1 is a flowchart of a first embodiment of an automated testing method for an intelligent command and control system of a container terminal provided by the present invention; [Figure 2] 1 is a flowchart illustrating some steps of a second embodiment of an automated testing method for an intelligent command and control system of a container terminal provided by the present invention; [Figure 3]10 is a flowchart illustrating some steps of a third embodiment of an automated testing method for an intelligent command and control system of a container terminal provided by the present invention. [Figure 4] 1 is a schematic block diagram of a first embodiment of an automated testing system for an intelligent command and control system of a container terminal provided by the present invention; FIG. [Figure 5] FIG. 2 is a schematic block diagram of a second embodiment of an automated testing system for an intelligent command and control system of a container terminal provided by the present invention; DETAILED DESCRIPTION OF THE INVENTION

[0019] To make the objectives, technical solutions and advantages of the present invention clearer, the present invention will be described in more detail below with reference to the drawings and embodiments.

[0020] In describing the present invention, it should be noted that terms indicating directions and positional relationships, such as "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," are based on the directions and positional relationships shown in the drawings, are for convenience of description only, and do not suggest or imply that devices or components have a particular orientation or are required to be constructed or operated in a particular orientation, and therefore should not be understood as limiting the present invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only, and should not be understood as suggesting or implying relative importance.

[0021] When the terminal operating system of an automated terminal is used in a highly concurrent environment, problems such as missing data (including yard status and container attributes) and data inconsistencies between the cache database and the system database may occur. If these problems are not identified in a timely manner, the entire operation process of the automated terminal may be disrupted, leading to incorrect manual intervention and reduced cargo handling efficiency. In response to this, one embodiment of the present invention provides an automated testing method for an intelligent command and control system of a container terminal, which includes multiple steps as shown in Figure 1.

[0022] Step S101: Display an attribute verification interactive interface.

[0023] Here, the verification interaction interface is configured to interact with a user (typically an operator) and receive a front-end element node verification request input by the user. The verification interaction interface is preferably configured on a server, a computer running at least one terminal operating system application, or other intelligent terminal capable of implementing similar functions. The verification interaction interface may include a button element, an input box element, or other similar element for receiving the front-end element node verification request input by the user. The terminal operating system is configured with a system database and a cache database to accommodate system requirements when a large number of concurrent executions are required. The container terminal intelligent command and control system may be a subsystem of the terminal operating system or an independent system.

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

[0025] The following describes the operation of an automated container terminal using an example. The automated container terminal is arranged, from land to sea, in the following order: a gate, a container yard, an on-site transport vehicle operation area, and a bridge crane work area. The gate is used to determine whether an off-site transport vehicle is allowed to enter or exit the yard. The off-site transport vehicle is typically a container truck. The parameters used by the gate to authenticate the entry and exit of vehicles and containers include, but are not limited to, the vehicle's physical license plate number, electronic license plate number, container number, container type, number of containers, position of the container on the pallet, orientation of the container door, whether the container is damaged, driver identity (identified by RFID), and vehicle weight. The container yard includes multiple parallel sub-yards, each of which includes a land-side interaction area, a loading work area, and a sea-side interaction area, arranged in this order from land to sea. A rail crane travels back and forth across and along the length of the sub-yards to unload, store, and load containers at target locations. Rail cranes generally include land-side rail cranes and sea-side rail cranes. For example, when the land-side rail crane receives a container storage task, its empty spreader travels to a target position, grabs a container from an off-site transport vehicle, and places the container at a designated loading position to complete the storage task. In the sea-side interaction area, the sea-side rail crane interacts with an automated guided vehicle (in-site transport vehicle). For example, the sea-side rail crane retrieves a container to be loaded from a container yard and places it at a target position. After automatically traveling to the target position, the in-site transport vehicle lifts the container and travels through the in-site transport vehicle operation area to transport the container to the bridge crane work area, where the container on the automated guided vehicle is loaded onto a ship by the bridge crane.

[0026] As can be seen from the above example workflow of an automated terminal, automatic control is often performed based on the comparison of sensor detection data with target data retrieved from the system database and / or cache database. For example, it determines whether a container identifier or vehicle identifier is legal, whether a spreader has reached its target position, or whether a container truck or automated guided vehicle has reached its target position. Meanwhile, an operator determines whether attributes are accurate based on data in the front-end display interface of the terminal operating system and actively intervenes to perform control. If the data in at least one of the system database and the cache database, or the data on the front-end display interface, is inaccurate, the risk of incorrect control increases. To ensure that the data in the system database, cache database, and displayed data are consistent and accurate, the attribute verification method of the automated terminal provided by the present invention can automatically verify any of the front-end element nodes. As can be easily understood, multiple front-end element nodes may be automatically verified in sequence. That is, the operator may actively select one or more front-end element nodes to be automatically verified.

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

[0028] Step S103: if one front-end element node verification request is received, obtain first verification data corresponding to the front-end element node verification request from the front-end interface corresponding to the front-end element node in the cache database according to the front-end element node verification request.

[0029] Step S104: In another embodiment, when receiving a front-end element node verification request, simultaneously obtain second verification data corresponding to the front-end element node verification request from the system database of the terminal operating system according to the front-end element node verification request.

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

[0031] Step S106: Automatically designate a display element node corresponding to the front-end element node in the front-end display interface.

[0032] Step S107: The attributes of the display element node are obtained to generate third verification data.

[0033] The above steps are further illustrated by taking the front-end element node as an example of a container attribute, which includes one or more of a category attribute, a transit attribute, a port of discharge attribute, a dangerous goods container attribute, an over-limit container attribute, a tank container attribute, a container type attribute, a tall container attribute, a reefer container attribute, a no-move attribute, and a bay assignment attribute, where the category attribute includes deposit or removal.

[0034] According to the front-end element node verification request, first verification data corresponding to the front-end element node verification request is obtained from the front-end interface corresponding to the front-end element node in the cache database, that is, the first verification data, which is the container attribute data (for example, the corresponding bit in the control instruction), is read from the cache database using a read command.

[0035] Obtaining second verification data corresponding to the front-end element node verification request from a system database of the terminal operating system according to the front-end element node verification request; The method may include calling a filter algorithm to screen all on-site containers from the system database, and obtaining container attributes of all on-site containers one by one to generate second verification data. The on-site container refers to a container located in any sub-yard within the yard. The filter algorithm may be a mature filter algorithm in the prior art, which is not the focus of the protection of the present invention and will not be further described here.

[0036] Displaying a front-end display interface corresponding to a front-end element node refers, for example, to the terminal operating system generating and displaying a front-end display interface corresponding to a yard during normal operation. Any front-end element node in the yard can be displayed, allowing the user to check the container attributes of the on-site container by, for example, directly displaying, clicking, or pausing. The front-end display interface may be a view window of the bay (where the container is located). In this embodiment, a Selenium frame is used to designate each on-site container 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 verification data. In this step, Selenium simulates manual operation as an element manipulation tool to automatically obtain the container attributes of the on-site container designated as a display element node, and generates the obtained front-end category attributes of each display element node as third verification data. The entire process is performed automatically without manual intervention.

[0037] Step S108: Determine whether the first verification data, the second verification data, and the third verification data are the same. For example, first compare and verify the front-end display interface with the database to determine whether the second verification data and the third verification data are the same, and obtain any mismatched data. Then, compare and verify the cache database with the front-end display interface to determine whether the first verification data and the third verification data are the same, such as the container transit attributes, type attributes (deposit or take-out), and bay allocation attributes, and obtain any mismatched data.

[0038] Step S109: If they are the same, it is determined that the attribute verification is successful, which indicates that the attributes are consistent with the front-end and back-end databases and the data exchange is accurate, and can ensure the smooth execution of the subsequent related control flows of the automation terminal.

[0039] The automated testing method for an intelligent command and control system for a container terminal (i.e., an attribute verification method for an automated terminal) of the present invention provides an automated testing method that allows one-click detection of complex container attributes, vehicle attributes, and spreader attributes in an automated terminal, accurately and efficiently detecting data inconsistencies. This ensures that the data in the cache database, front-end display interface, and system database are consistent in scenarios with a large number of concurrent executions, allowing data deficiencies to be identified in a timely manner, avoiding data inconsistencies between the cache database and the system database, preventing disruptions to the operation process of the automated terminal, and ensuring cargo handling efficiency. It also prevents the display of an incorrect person on the front-end display interface, which could lead to erroneous manual intervention. The automated testing method for an intelligent command and control system for a container terminal of the present invention can improve the operational stability of the automated terminal.

[0040] See Figure 2. In a preferred embodiment of the present invention, a processing method is further designed for the case where there are at least two different data in the first verification data, the second verification data, and the third verification data.

[0041] Step S201: Determine that there are at least two different data in the first verification data, the second verification data, and the third verification data. For example, the transit attributes of on-site containers in the same bay in the system database, the cache database, and the front-end display interface are different, one of which is "passing allowed" and the other two are "passing prohibited." Illustratively, the different transit attributes can be reflected as different values ​​of corresponding flag bits in the first verification data, the second verification data, and the third verification data.

[0042] Step S202: The first verification data, the second verification data, and the third verification data are stored.

[0043] Step S203: The front-end element node verification request is maintained as is.

[0044] Step S204: According to the front-end element node verification request, the steps from obtaining the first verification data corresponding to the front-end element node verification request from the front-end interface corresponding to the front-end element node in the cache database to obtaining the attributes of the display element node and generating the third verification data are executed again in order.

[0045] Step S205: It is determined whether the reacquired first verification data, second verification data, and third verification data are the same.

[0046] Step S206: If the reacquired first verification data, second verification data, and third verification data are the same, it is determined that the attribute verification is successful, and the initial determination of a temporary mismatch is recorded.

[0047] In an alternative embodiment, the number of times a temporary inconsistency is determined is accumulated. If the accumulated number of temporary inconsistencies is greater than the set number during a set detection period, this indicates that an unreasonable situation exists in the current cache database update period. That is, when data is retrieved, the data in the system database has not yet been updated to the cache database. Therefore, in a preferred embodiment, if the accumulated number of temporary inconsistencies is greater than the set number, a step of correcting the current cache database update period is automatically performed, and in the next set detection period, it is determined whether the accumulated number of temporary inconsistencies is greater than the set number. If the accumulated number of temporary inconsistencies is less than the set number, it is determined that the corrected cache database update period is reasonable, and the cache database is updated according to the corrected cache database update period in subsequent control, thereby achieving automatic system correction. If the accumulated number of temporary inconsistencies is still greater than the set number, the cache database update period is again corrected until the accumulated number of temporary inconsistencies is less than the set number. When adjusting the update period of the current cache database, a set amount of time can be called, and the sum of the original update period and the set amount of time can be the modified update period of the cache database, and the set amount of time can be a positive or negative value.

[0048] Step S208: If at least two of the reacquired first verification data, second verification data, and third verification data are different, an error log is generated, and an operator is prompted to conduct further investigation and processing.

[0049] In a preferred embodiment, after generating the error log, the method further includes disabling a control flow based on the front-end element node until the updated first verification data, second verification data, and third verification data become the same. Illustratively, if the transit attributes of on-site containers in the same bay in the system database, cache database, and front-end display interface are different, with one being "passing allowed" and the other two being "passing not allowed," the method temporarily prohibits deposit or retrieval operations for containers in the bay, and releases the control prohibition when the updated first verification data, second verification data, and third verification data become the same after manual intervention.

[0050] In a preferred embodiment, the automated testing method for an intelligent command and control system of a container terminal provided by the present invention can be adapted to various terminal operating systems. Specifically, as shown in FIG. 3, before displaying an attribute verification interactive interface, the method optionally further includes obtaining the environment variable configuration of the terminal operating system and determining whether the user authority satisfies the set verification authority. If yes, the attribute verification interactive interface is displayed, allowing interaction with the user (usually an operator), and receiving a front-end element node verification request entered by the user. If not, the method prohibits interaction with the user (usually an operator).

[0051] A second aspect of the present invention provides an automated testing system for an intelligent command and control system of a container terminal. As shown in Figure 4, the automated testing system for an intelligent command and control system of a container terminal includes a first display module 101, a first determination module 102, a first acquisition module 103, a second acquisition module 104, a second display module 105, a designation module 106, a third acquisition module 107 and a second determination module 108.

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

[0053] The first determination module 102 is configured to determine whether at least one front-end element node validation request is received.

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

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

[0056] The second display module 105 is configured to display a 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.

[0057] The designation module 106 is configured to designate a display element node in the front-end display interface that corresponds to the front-end element node.

[0058] The third obtaining module 107 is configured to obtain attributes of the display element nodes and generate third verification data.

[0059] 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, and if they are the same, determine that the attribute verification is successful.

[0060] As shown in FIG. 5 , in a preferred embodiment, the automated testing system for the intelligent command and control system of the container terminal further includes a re-verification module 209 , a first recording module 210 and a second recording module 211 .

[0061] If the second determination module 108 determines that there are at least two different data in the first verification data, the second verification data, and the third verification data, the re-verification module 209 stores the first verification data, the second verification data, and the third verification data, maintains the front-end element node verification request, and sequentially re-executes steps according to the front-end element node verification request, from obtaining the first verification data corresponding to the front-end element node verification request from the front-end interface corresponding to the front-end element node in the cache database to obtaining attributes of the display element node and generating third verification data, and determines whether the re-obtained first verification data, the second verification data, and the third verification data are the same. If they are the same, the re-verification module 209 determines that the attribute verification was successful.

[0062] The first recording module 210 is configured to record the initial determination of a temporary mismatch when the re-verification module 209 determines that the re-acquired first verification data, second verification data, and third verification data are the same.

[0063] The second recording module 211 is configured to generate and record an error log when the re-verification module 209 determines that there are at least two different data in the re-acquired first verification data, second verification data, and third verification data.

[0064] 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 a control flow based on the front-end element node until the updated first verification data, second verification data, and third verification data are the same after the error log is generated and recorded by the second recording module 211.

[0065] In a preferred embodiment, the front-end element node is a container attribute, and the container attributes include one or more of a category attribute, a transit attribute, a port of discharge attribute, a hazardous material container attribute, an over-limit container attribute, a tank container attribute, a container type attribute, a tall container attribute, a reefer container attribute, a no-move attribute, and a bay assignment attribute.

[0066] The second acquisition module 104 is configured to invoke a filter algorithm to screen all on-site containers from the system database, and acquire container attributes of all on-site containers one by one to generate second verification data.

[0067] The third acquisition module 107 is configured to use a selenium frame to designate each on-site container as a corresponding display element node in the front-end display interface, and acquire front-end category attributes of each display element node to generate third verification data.

[0068] In a preferred embodiment, the automated testing system for the intelligent command and control system of the container terminal further includes an authority verification module, which is configured to obtain an environment variable configuration of the terminal operating system, determine whether the user authority satisfies the set verification authority, and if so, display an attribute verification interactive interface.

[0069] An embodiment of the present application further provides a computer storage medium storing a computer program for electronic data exchange, the computer program causing a computer to perform part or all of any of the methods described in the method embodiments above.

[0070] In the above embodiments, the description of each embodiment is focused on each other, and for the parts not described in detail in one embodiment, please refer to the related descriptions of other embodiments.

[0071] It should be understood that in some embodiments provided in the present application, the disclosed devices may be realized in other ways. For example, the above-described system embodiments are merely exemplary, and the division of the above-described units or modules is merely a logical functional division, and actual implementation may be performed in other divisional manners. For example, multiple units or components may be combined or integrated into another system, and some functions may be ignored or not implemented. Furthermore, the illustrated or described couplings, direct couplings, or communication connections between each other may be indirect couplings or communication connections via electrical or other types of interfaces, devices, or units.

[0072] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, i.e., they may be located in one physical space or distributed across multiple network units, and some or all of the units may be selected according to actual needs to achieve the objectives of the solution of this embodiment.

[0073] Furthermore, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be realized in the form of hardware or in the form of a software functional unit.

[0074] The above embodiments are only for illustrating the technical solutions of the present invention, and are not intended to limit the same. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art may modify the technical solutions described in the above embodiments or make equivalent substitutions for some of the technical features thereof. These 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 for protection by the present invention.

Claims

1. 1. An automated testing method for an intelligent command and control system of a container terminal, comprising: displaying an attribute verification interactive interface configured to input a front-end element node verification request corresponding to one front-end element node, the front-end element node including at least one container attribute, at least one vehicle attribute, and / or at least one spreader attribute; determining whether at least one front-end element node validation request has been received; If it is determined that the front-end element node verification request has been received, obtaining 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; According to the front-end element node verification request, obtaining second verification data corresponding to the front-end element node verification request from a system database of a terminal operating system; Displaying a front-end display interface corresponding to the front-end element node; specifying a display element node in the front-end display interface corresponding to the front-end element node; obtaining attributes of the display element nodes to generate third verification data; determining whether the first verification data, the second verification data, and the third verification data are the same; and if they are the same, determining that the attribute verification was successful.

2. After determining whether the first verification data, the second verification data, and the third verification data are the same, storing the first verification data, the second verification data, and the third verification data when at least two different data exist in the first verification data, the second verification data, and the third verification data; maintaining the front-end element node validation request as is; According to the front-end element node verification request, sequentially re-executing steps from obtaining 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 to obtaining attributes of the display element node to generate third verification data; determining whether the reacquired first verification data, second verification data, and third verification data are the same; determining that the attribute verification was successful and recording the initial determination of a temporary mismatch if the reacquired first verification data, second verification data, and third verification data are the same; and generating an error log if at least two of the reacquired first verification data, second verification data, and third verification data are different.

3. After generating the error log, 3. The automated testing method for an intelligent command and control system of a container terminal according to claim 2, further comprising disabling a control flow based on the front-end element node until the updated first verification data, second verification data, and third verification data are the same.

4. The front-end element node is a container attribute including at least one of a category attribute, a transit attribute, a port of discharge attribute, a dangerous goods container attribute, an over-limit container attribute, a tank container attribute, a container type attribute, a tall container attribute, a reefer container attribute, a no-move attribute, and a bay assignment attribute; According to the front-end element node verification request, obtaining second verification data corresponding to the front-end element node verification request from a system database of a terminal operating system includes: Invoking a filter algorithm to screen all on-site containers from the system database, and obtaining container attributes of all on-site containers one by one to generate second verification data; In the front-end display interface, specifying a display element node corresponding to the front-end element node, obtaining attributes of the display element node, and generating third verification data includes: The automated testing method for an intelligent command and control system of a container terminal according to any one of claims 1 to 3, characterized in that it includes using a selenium frame to designate each on-site container as a corresponding display element node in the front-end display interface, and obtaining front-end category attributes of each display element node to generate third verification data.

5. Before you can view the Attribute Validation interactive interface, Obtaining the environment variable configuration of the terminal operating system; determining whether the user authority satisfies the set verification authority; The automated testing method for an intelligent command and control system of a container terminal according to claim 4, characterized in that if the attribute is satisfied, an attribute verification interactive interface is displayed.

6. An automated testing system for an intelligent command and control system of a container terminal, comprising: a first display module, a first determination module, a first acquisition module, a second acquisition module, a second display module, a designation module, a third acquisition module, and a second determination module, The first display module is configured to display an attribute verification interactive interface, and the attribute verification interactive interface is configured to input a front-end element node verification request corresponding to a front-end element node, the front-end element node including at least one of at least one container attribute, at least one vehicle attribute, and at least one spreader attribute; The first determination module is configured to determine whether at least one front-end element node verification request is received; The first obtaining module is configured to 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 after the first determining module determines that at least one front-end element node verification request is received; The second obtaining module is configured to obtain second verification data corresponding to the front-end element node verification request from a system database of the terminal operating system according to the front-end element node verification request after the first determining module determines that at least one front-end element node verification request has been received; The second display module is configured to display a front-end display interface corresponding to a front-end element node after the first determination module determines that at least one front-end element node verification request is received; The designation module is configured to designate a display element node in the front-end display interface corresponding to the front-end element node; the third obtaining module is configured to obtain attributes of the display element node to generate third verification data; 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, and if they are the same, determine that attribute verification is successful.

7. A re-verification module, a first recording module and a second recording module are further provided; When the second determination module determines that there are at least two different data in the first verification data, the second verification data, and the third verification data, the re-verification module is configured to save the first verification data, the second verification data, and the third verification data, maintain the front-end element node verification request as it is, and sequentially re-execute steps from obtaining the first verification data corresponding to the front-end element node verification request from the front-end interface corresponding to the front-end element node in the cache database according to the front-end element node verification request to obtaining attributes of the display element node and generating third verification data; and determine whether the re-acquired first verification data, second verification data, and third verification data are the same, and if they are the same, determine that the attribute verification is successful; the first recording module is configured to record the initial determination of a temporary mismatch when the re-verification module determines that the re-acquired first verification data, second verification data, and third verification data are the same; 7. The automated testing system for an intelligent command and control system of a container terminal according to claim 6, wherein the second recording module is configured to generate and record an error log when the re-verification module determines that there are at least two different data in the re-acquired first verification data, second verification data, and third verification data.

8. 8. The automated testing system for an intelligent command and control system of a container terminal according to claim 7, further comprising a disabling module configured to disable a control flow based on the front-end element node until the updated first verification data, second verification data, and third verification data become the same after an error log is generated and recorded by the second recording module.

9. The front-end element node is a container attribute including at least one of a category attribute, a transit attribute, a port of discharge attribute, a dangerous goods container attribute, an over-limit container attribute, a tank container attribute, a container type attribute, a tall container attribute, a reefer container attribute, a no-move attribute, and a bay assignment attribute; The second acquisition module is configured to call a filter algorithm to screen all on-site containers from the system database, and acquire container attributes of all on-site containers one by one to generate second verification data; The automated testing system for an intelligent command and control system of a container terminal according to any one of claims 6 to 8, characterized in that the third acquisition module is configured to use a selenium frame to designate each on-site container as a corresponding display element node in the front-end display interface, and acquire front-end category attributes of each display element node to generate third verification data.

10. 10. The automated testing system for an intelligent command and control system of a container terminal according to claim 9, further comprising an authority verification module configured to obtain an environment variable configuration of a terminal operating system, determine whether a user authority satisfies a set verification authority, and if so, display an attribute verification interactive interface.

Images