TWI864454B - System for batched updating test flow script - Google Patents

Abstract

A system is configured for batched updating test flow script. In the system, an arrangement setting device is applied to execute a test flow script arrangement program to link to a jump server to enter an arrangement setting web page and obtain a test flow script directory for a user to select an updating test flow script version for each of a plurality of production line servers, so as to accordingly built up a script corresponding relation, and make the jump server generate a batched updating order. After receiving the batched updating order, a proxy server transmits at least one test flow script to the production line servers according to the script corresponding relation so as to achieve batched updating.

Description

Batch update system for test process scripts

The present invention relates to a test process script update system, and more particularly to a test process script batch update system for batch updating the test process scripts of a plurality of production line servers.

As electronic products become more sophisticated, more and more modules with sophisticated functions are built into them. In order to monitor and manage electronic product production lines more efficiently, a large number of monitoring and control modules must be used in combination, and a large amount of monitoring and control data must be transmitted, stored and managed using channels such as the Internet of Things, local area networks and the Internet. In this case, each production line will most likely be equipped with at least one production line server.

In response to the needs of production line monitoring and management, the production line server records a large number of control and management rules. In order to ensure that the production line server can correctly and effectively manage the production line according to appropriate control and management rules, a test process script is usually installed in the production line server to perform self-tests on the production line server itself or test the modules that the production line can support.

In the above context, whenever the production conditions in the production line change, it is necessary to update or replace the test process script to provide appropriate control and management services in real time. When the above production conditions change, for example, there may be changes in the finished or semi-finished electronic products produced by the production line, or when there are new production line management requirements, or when switching to the production of different brands of products and needing to eliminate some information for confidentiality.

Generally speaking, in a systematic manufacturing plant, there are often several or even dozens of production lines. Each production line is equipped with a production line server, and the test process scripts of several or dozens of production line servers need to be updated or replaced. Since the production conditions and properties of each production line are different, each production line server is also different, resulting in different test process scripts that must be installed, replaced or updated for each production line server.

In order to ensure that each production line server can install, replace or update the test process script that best meets the current requirements of the production line. In the previous technology, it is necessary to rely on at least one script manager to use a management device to log in to the test script database and the production line server one by one, and then update the test process script one by one according to actual needs. Because the script manager must use the management device to correspond to multiple production line servers and repeatedly perform multiple tasks such as connection, login, selection, modification and upload, it will consume a lot of update time, thus seriously affecting the work efficiency of the production line.

In view of the fact that in the prior art, script managers generally have to use management devices to repeatedly execute multiple tasks on multiple production line servers, which seriously affects the work efficiency of the production line. Therefore, the main purpose of the present invention is to provide a batch update system for test process scripts (hereinafter referred to as "batch update system"), hoping that the batch update function can be achieved by setting it once.

Therefore, the necessary technical means adopted by the present invention to solve the problems of the prior art is to provide a batch update system for test process scripts (hereinafter referred to as "batch update system"). The batch update system is used to batch update a plurality of test process scripts corresponding to a plurality of production line servers, and includes a transfer server, a fortress server and a deployment setting device.

The transit server is used to store multiple test process scripts, and is connected to the production line server via a file transfer protocol (FTP) communication link. A test process script directory is established according to multiple script version names corresponding to the test process scripts, so that the test process script directory is updated when the test process scripts are changed.

The fortress server has a deployment configuration webpage, and when communicating with the relay server, it captures the test process script directory. The deployment configuration device connects to the fortress server via a Hyper Text Transfer Protocol (HTTP) communication link by executing a test process script deployment program to open the deployment configuration webpage, so that a deployment configuration personnel can select one of the script version names that should be updated for each production line server from the test process script directory to update the script version name, thereby establishing a script correspondence relationship based on the production line servers and the update script version name, so that the fortress server generates a batch update command based on the script correspondence relationship.

After the batch update command is sent to the transit server, the transit server batches the test process scripts corresponding to the update script version name to the production line server using the file transfer protocol according to the script correspondence relationship, thereby completing the batch update of the production line server.

Among the preferred supplementary technical means derived from the above-mentioned necessary technical means, the batch update system may include an authentication device, which is communicatively connected to the deployment setting device and the fortress server, so that after authenticating that a login account and a login password input by the deployment setting device are correct, the deployment setting device is connected to the fortress server via a hypertext transfer protocol communication link to open the deployment setting webpage.

Preferably, the batch update system may further include at least one test process script upload module, which is connected to the relay server via file transfer protocol communication to upload at least one newly added test process script to the relay server as a part of the test process script. After the upload is completed, the relay server adds a script version name corresponding to the newly added test process script in the test process script directory.

Preferably, the transit server may further include a version update monitoring module, so that after each production line server completes the batch update and records it in a server log of the production line server, the version update monitoring module is used to collect and record the update script version name of the production line server. In addition, the transit server may also include an update information publishing module, and the update information publishing module is used to publish a script update information according to the update script version name of the production line server.

In order to simultaneously present the script version name currently used by each production line server on the deployment configuration webpage, preferably, the fortress server further includes a webpage update module, so that after the fortress server receives the script update information, the deployment configuration webpage is updated according to the updated script version name of the production line server.

As mentioned above, in the batch update system of the test process script provided by the present invention, the deployment setting webpage established by the fortress server is used for the deployment setting personnel to simultaneously deploy and set the test process scripts required by multiple production line servers at one time, so that the fortress server generates a batch update command according to the deployment setting, and the transit server automatically performs batch update on multiple production line servers according to the batch update command. Undoubtedly, the test process script update time of the production line server can be greatly reduced, thereby greatly improving the work efficiency of the production line.

Since the batch update system of the test process script provided by the present invention can be widely used in the batch update of the test process script of various production line servers, it will not be described here one by one, and only a preferred embodiment will be listed to provide a specific description. In addition, the drawings in each embodiment are all in a very simplified form, and the components are not presented in an absolutely accurate ratio, only to facilitate and clearly assist in explaining the purpose and effect of the embodiment of the present invention.

Please refer to the first figure, which is a functional block diagram of a batch update system for test process scripts provided by a preferred embodiment of the present invention. As shown in the first figure, a batch update system for test process scripts (hereinafter referred to as "batch update system") 100 is used to batch update a plurality of test process scripts corresponding to three production line servers 200a, 200b and 200c, and the production line servers 200a, 200b and 200c have server logs 201a, 201b and 201c respectively. The batch update system 100 includes a transit server 1, three test process script upload modules 2a, 2b and 2c, a fortress server 3, a deployment setting device 4 and an authentication device 5.

The transit server 1 refers to a proxy server for transmitting files, which is connected to the production line servers 200a, 200b and 200c via a file transfer protocol (FTP) communication, and includes a test process script database 11, a version update monitoring module 12 and an update information publishing module 13. The test process script database 11 stores a plurality of test process scripts (only one test process script 111 is drawn as a representative in the figure), and a test process script directory 112 is established according to a plurality of script version names (not shown in the figure) corresponding to the test process script 111, so as to update the test process script directory 112 when the test process script is changed (such as added or deleted).

The test process script upload modules 2a, 2b and 2c are connected to the relay server 1 via file transfer protocol communication, so that when at least one new version of the test process script (hereinafter referred to as "the newly added test process script") is obtained (developed by the user or purchased from outside), the newly added test process script is uploaded to the relay server 1 as part of the test process script 111. After the upload is completed, the relay server 1 adds a script version name corresponding to the newly added test process script in the test process script directory 112.

The jump server 3 is a front-end server (Jump Server) that is set at the front end of the system and has a strong protection capability to prevent viruses or hackers from invading. The jump server 3 has a deployment setting web page 31 established and includes a web page update module 32. When the jump server 3 is communicatively connected to the relay server 1, the test process script directory 112 can be captured. The deployment setting device 4 can be a computer or a mobile electronic communication device, in which a test process script deployment program 41 is installed. When a deployment setting personnel operates the deployment setting device 4 to execute the test process script deployment program 41, it will be communicatively connected to the authentication device 5, and the authentication device 5 is communicatively connected to the jump server 3. After the deployment configuration personnel inputs a login account and a login password through the deployment configuration device 4, and after the authentication device 5 authenticates that the input login account and login password are correct, the deployment configuration device 4 can establish a Hyper Text Transfer Protocol (HTTP) communication link to the fortress server 3 to open the deployment configuration web page 31.

In the deployment setting web page 31, the deployment setting personnel can select one of the script version names that should be updated for each production line server 200a~200c from the test process script directory 112 to update the script version name, thereby establishing a script correspondence relationship based on the production line server 200a~200c and the update script version name, so that the fortress server 3 generates a batch update command S1 based on the script correspondence relationship.

For further example, the script correspondence can be presented by the script correspondence table shown in Table 1. As shown in Table 1, the production line server codes S0001~S0003 represent the production line servers 200a~200c respectively, and the content of the two lines of the production line server code and the current script version name will be automatically presented on the deployment setting webpage 31. The content of the update script version name line of the expected update is selected and filled in by the deployment setting personnel from the test process script directory 112.

Table 1: Script correspondence table Production line server code Current script version name Expected update script version name S0001 TFS001.001 TFS001.003 S0002 TFS001.001 TFS001.001 S0003 TFS001.001 TFS002.004

As shown in Table 1, for the production line servers coded S0001 and S0003, the current script version name is different from the expected update script version name, indicating that the deployment personnel are updating and deploying the production line servers 200a and 200c. For the production line server coded S0002, the current script version name is the same as the expected update script version name, indicating that the deployment personnel decided to use the test process script 111 corresponding to the current script version name of the production line server 200b.

After the batch update command S1 is transmitted to the relay server 1, the relay server 1 can batch transmit the test process scripts corresponding to the update script version name to the production line servers 200a~200c according to the script correspondence relationship using the file transfer protocol, thereby completing the batch update of the test process scripts for the production line servers 200a~200c.

The version update monitoring module 12 of the transit server 1 can monitor the progress of the batch update of the production line servers 200a~200c in a polling manner, and after confirming that the production line servers 200a~200c have completed the batch update and recorded in the server logs 201a~201c of the production line servers 200a~200c, collect and record the update script version names of the production line servers 200a~200c. Afterwards, the update information publishing module 13 of the transit server 1 can publish a script update information according to the update script version names of the production line servers 200a~200c. Preferably, the script update information can be sent to the fortress server 3 and the electronic device operated by the deployment and configuration personnel (including the above-mentioned deployment and configuration device 4) by means of e-mail, text message, information push, etc., so that the deployment and configuration personnel know that the batch update work of the test process script 111 has been completed.

In order to simultaneously present the script version name currently used by the production line servers 200a~200c on the deployment configuration webpage 31, preferably, the webpage update module 32 of the fortress machine server 3 further updates the deployment configuration webpage 31 according to the updated script version name of the production line servers 200a~200c after the fortress machine server 3 receives the script update information. The script correspondence table in the updated deployment configuration webpage 31 is shown in Table 2.

Table 2: Updated script correspondence table Production line server code Current script version name Expected update script version name S0001 TFS001.003 Input to be selected S0002 TFS001.001 Input to be selected S0003 TFS002.004 Input to be selected

As shown in Table 2, after the update of the deployment configuration webpage 31 is completed, the updated script version name after the update is completed will be used as the current script version name, and the field of the updated script version name to be updated must wait until the next time there is a batch update requirement, and then the deployment configuration personnel will select and input it from the test process script directory 112.

In summary, in the batch update system 100 provided by the present invention, the deployment setting webpage 31 established by the fortress server 3 is used for the deployment setting personnel to simultaneously perform one-time deployment setting of the test process script 111 required by multiple production line servers 200a~200c, so that the fortress server 3 generates a batch update command S1 according to the deployment setting, and the transit server 1 automatically performs batch update on multiple production line servers 200a~200c according to the batch update command S1. Undoubtedly, the update time of the test process script 111 of the production line servers 200a~200c can be greatly reduced, thereby greatly improving the work efficiency of the production line.

The above detailed description of the preferred specific embodiments is intended to more clearly describe the features and spirit of the present invention, but is not intended to limit the scope of the present invention by the preferred specific embodiments disclosed above. On the contrary, the purpose is to cover various changes and arrangements with equivalents within the scope of the patent application for the present invention.

100: Batch update system 1: Transfer server 11: Test process script database 111: Test process script 112: Test process script directory 12: Version update monitoring module 13: Update information release module 2a, 2b, 2c: Test process script upload module 200a, 200b, 200c: Production line server 201a, 201b, 201c: Server log 3: Fortress server 31: Deployment setting web page 32: Web page update module 4: Deployment setting device 41: Test process script deployment program 5: Authentication device S1: Batch update command

The first figure is a functional block diagram of a batch update system for the test process script provided by the preferred embodiment of the present invention.

100: Batch update system

1: Relay server

11: Test process script database

111:Test process script

112: Test process script directory

12: Version update monitoring module

13: Update information release module

2a, 2b, 2c: Test process script upload module

200a, 200b, 200c: Production line server

201a,201b,201c: Server log

3: Fortress Server

31: Deployment settings page

32: Web page update module

4: Deployment and configuration equipment

41:Test process script deployment program

5: Authentication device

S1: Batch update command

Claims (5)

A batch update system for test process scripts is used to batch update a plurality of test process scripts corresponding to a plurality of production line servers, and includes: a transfer server for storing a plurality of test process scripts, and a file transfer protocol (File Transfer Protocol) for transferring the test process scripts to the server. A test process script directory is established according to the multiple script version names corresponding to the test process scripts, so as to update the test process script directory when the test process scripts are changed; a fortress server is established with a deployment setting webpage, and when the communication link is connected to the relay server, the test process script directory is captured; a deployment setting device is established by executing a test process script deployment program and using a Hyper Text Transfer Protocol (HTP) to transmit the test process script directory to the production line servers; Protocol; HTTP) communication link to the fortress machine server to open the deployment setting webpage, so that a deployment setting personnel can select one of the script version names to be updated for each of the production line servers from the test process script directory, so as to establish a script correspondence relationship based on the production line servers and at least one of the above-mentioned update script version names, so that the fortress machine server generates a batch update command based on the script correspondence relationship; and an authentication device, which is communication-connected between the deployment setting device and the The fortress server, after verifying that a login account and a login password input by the deployment configuration device are correct, enables the deployment configuration device to connect to the fortress server through the hypertext transfer protocol communication to open the deployment configuration webpage, wherein the batch update command is transmitted to the transit server, so that the transit server batches the test process scripts corresponding to the at least one update script version name to the production line servers according to the script correspondence relationship through the file transfer protocol, thereby completing the batch update of the production line servers. The batch update system of the test process script as described in claim 1 further comprises at least one test process script upload module, which is connected to the relay server through the file transfer protocol communication to upload at least one newly added test process script to the relay server as part of the test process scripts, and after the upload is completed, the relay server adds at least one script version name corresponding to the at least one newly added test process script in the test process script directory. The batch update system of the test process script as described in claim 1, wherein the transit server further includes a version update monitoring module, so that after each of the production line servers completes the batch update and records it in a server log of each of the production line servers, the version update monitoring module is used to collect and record the update script version names of the production line servers. The batch update system of the test process script as described in claim 3, wherein the transit server further includes an update information publishing module, and the update information publishing module is used to publish a script update information according to the update script version name of the production line servers. The batch update system of the test process script as described in claim 4, wherein the fortress server further includes a web page update module, so that after the fortress server receives the script update information, the deployment setting web page is updated according to the update script version name of the production line servers.

Images