CN112597178A - Test sequence file management method, device and system - Google Patents
Test sequence file management method, device and system Download PDFInfo
- Publication number
- CN112597178A CN112597178A CN202110009305.9A CN202110009305A CN112597178A CN 112597178 A CN112597178 A CN 112597178A CN 202110009305 A CN202110009305 A CN 202110009305A CN 112597178 A CN112597178 A CN 112597178A
- Authority
- CN
- China
- Prior art keywords
- test sequence
- sequence file
- file
- server
- updated
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The embodiment of the application provides a method, a device and a system for managing a test sequence file, and relates to the technical field of production line testing. Under the condition that the test sequence file in the process server is updated, the updated test sequence file is sent to the production server, so that the production server can synchronize the updated test sequence file to a production database included by the production server in real time, the accuracy and consistency of the test sequence file are ensured, and the application timeliness of the test sequence file is improved.
Description
Technical Field
The application relates to the technical field of production line testing, in particular to a method, a device and a system for managing a test sequence file.
Background
The test sequence file is a standard file for specifying test items and test data ranges in the production line test process, and is an indispensable standardized file in the production line test process.
At present, a test sequence file in production line test is usually transmitted to a client in the modes of mails, field confirmation, third-party communication software and the like, and when the test sequence file is updated for multiple versions, the accuracy and consistency of the test sequence cannot be ensured in the mode, and the timeliness is low.
Disclosure of Invention
In view of the above, embodiments of the present application provide a method, an apparatus, and a system for managing test sequence files to improve the above problem.
In a first aspect, the present application provides a test sequence file management method, where the method is applied to a production server including a production database, and the production server is in communication connection with a process server; the method comprises the following steps:
receiving a target test sequence file sent by the process server, wherein the target test sequence file is a test sequence file with an update;
and synchronizing the target test sequence file to the production database.
In an optional embodiment, the production server is further communicatively connected to a client, and the method further comprises:
receiving a query request sent by a client, wherein the query request comprises at least one query item;
querying whether the production database comprises query content corresponding to the query item or not based on the query item;
and if the production database comprises query contents corresponding to the query items, sending the query contents to the client so that the client updates the test sequence file according to the query contents, wherein the query contents comprise the latest version number of the test sequence file and the latest test sequence file.
In an optional embodiment, the step of sending the query content to the client, so that the client updates the test sequence file according to the query content includes:
generating a file download link based on the latest test sequence file;
taking the file downloading link and the version number of the latest test sequence file as query contents;
and sending the query content to the client so that the client judges whether the test sequence file needs to be updated according to the version number, and if the test sequence file needs to be updated, acquiring the latest test sequence file according to the file download link and updating.
In an optional embodiment, the step of receiving the target test sequence file sent by the flow server includes:
receiving a target test sequence file sent by the process server when the updated test sequence file exists according to a first preset time interval;
or sending an update query request to the process server according to a second preset time interval so that the process server queries whether the test sequence file is updated or not based on the update query request;
and receiving a target test sequence file returned by the process server based on the updating query request.
In an alternative embodiment, the method further comprises:
displaying a test sequence file query interface, wherein the test sequence file query interface displays file information of all validated test sequence files;
and responding to the query operation on the test sequence file query interface, acquiring target file information from the file information of all the validated test sequence files according to the query operation, and displaying the target file information.
In a second aspect, the present application provides a test sequence file management method, where the method is applied to a process server including a process database, the process server is in communication connection with a production server, and the production server includes a production database; the method comprises the following steps:
inquiring whether the test sequence file in the process database is updated or not, and if the updated test sequence file is determined to exist, acquiring the updated test sequence file;
and sending the updated test sequence file as a target test sequence file to the production server so that the production server synchronizes the target test sequence file to the production database.
In an alternative embodiment, the method further comprises:
displaying an audit release interface, wherein the audit release interface comprises at least one file information item to be filled;
responding to information input operation aiming at each file information item, and obtaining file information corresponding to each file information item;
and generating a test sequence file to be updated based on the file information, and storing the test sequence file to be updated in the process database.
In an optional embodiment, the step of querying whether the test sequence file in the process database has an update includes:
inquiring whether the test sequence file in the process database is updated or not according to a first preset time interval;
or receiving an update query request sent by the production server;
and inquiring whether the test sequence file in the process database is updated or not based on the updating inquiry request.
In a third aspect, the present application provides a test sequence file management apparatus, where the apparatus is applied to a production server including a production database, and the production server is in communication connection with a process server; the device comprises:
the first receiving module is used for receiving a target test sequence file sent by the process server, wherein the target test sequence file is a test sequence file with an update;
and the synchronization module is used for synchronizing the target test sequence file to the production database.
In a fourth aspect, the present application provides a test sequence file management apparatus, where the apparatus is applied to a process server including a process database, the process server is in communication connection with a production server, and the production server includes a production database; the device comprises:
the query module is used for querying whether the test sequence file in the process database is updated or not, and if the updated test sequence file is determined to exist, the updated test sequence file is obtained;
and the sending module is used for sending the updated test sequence file serving as a target test sequence file to the production server so that the production server synchronizes the target test sequence file to the production database.
In a fifth aspect, the present application provides a test sequence file management system, including a production server and a process server, which are communicatively connected, where the production server includes a production database, and the process server includes a process database;
the process server is used for inquiring whether the test sequence file in the process database is updated or not, and if the updated test sequence file is determined to exist, acquiring the updated test sequence file; sending the updated test sequence file as a target test sequence file to the production server;
the production server is used for receiving a target test sequence file sent by the process server, wherein the target test sequence file is a test sequence file with an update, and the target test sequence file is synchronized to the production database.
The embodiment of the application provides a method, a device and a system for managing a test sequence file, wherein the updated test sequence file is sent to a production server under the condition that the test sequence file in a process server is updated, so that the production server can synchronize the updated test sequence file to a production database included by the production server in real time, the accuracy and the consistency of the test sequence file are ensured, and the timeliness of the application of the test sequence file is improved.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, several embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is an architecture diagram of a test sequence file management system according to an embodiment of the present application.
Fig. 2 is a flowchart of a test sequence file management method according to an embodiment of the present disclosure.
Fig. 3 is a second flowchart of a test sequence file management method according to an embodiment of the present application.
Fig. 4 is a functional block diagram of a test sequence file management apparatus according to an embodiment of the present disclosure.
Fig. 5 is a second functional block diagram of the test sequence file management apparatus according to the embodiment of the present application.
Icon: 1-a production server; 10-production database; 11-first test sequence file management means; 111-a receiving module; 112-a synchronization module; 2-a process server; 20-a process database; 21-second test sequence file management means; 211-a query module; 212-a sending module; and 3, a client.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
Furthermore, the appearances of the terms "first," "second," and the like, if any, are used solely to distinguish one from another and are not to be construed as indicating or implying relative importance.
It should be noted that the features of the embodiments of the present application may be combined with each other without conflict.
As introduced in the background art, a test sequence file is a standard file that specifies test items and test data ranges in a production line test process, and is an indispensable standardized file in the production line test process.
At present, a test sequence file in production line test is usually transmitted to a client in the modes of mails, field confirmation, third-party communication software and the like, and when the test sequence file is updated for multiple versions, the accuracy and consistency of the test sequence cannot be ensured in the mode, and the timeliness is low.
In view of this, embodiments of the present application provide a method, an apparatus, and a system for managing a test sequence file, where an updated test sequence file is sent to a production server under the condition that the test sequence file in a process server is updated, so that the production server can synchronize the updated test sequence file to a production database included in the production server in real time, thereby ensuring accuracy and consistency of the test sequence file, and improving timeliness of application of the test sequence file. The above scheme is explained in detail below.
It should be noted that the above prior art solutions have drawbacks that are the results of practical and careful study by the applicant, and therefore, the discovery process of the above problems and the solutions proposed by the following embodiments of the present application for the above problems should be the contributions of the applicant to the present application in the course of the present application.
Some embodiments of the present application will be described in detail below with reference to the accompanying drawings. The embodiments described below and the keys in the embodiments can be combined with each other without conflict.
Referring to fig. 1, the present application provides a test sequence file management system, which includes a production server 1 and a process server 2 connected in communication, where the production server 1 includes a production database 10, and the process server 2 includes a process database 20.
The process server 2 is configured to query whether the test sequence file in the process database 20 is updated, and if it is determined that the updated test sequence file exists, obtain the updated test sequence file. And sends the updated test sequence file as a target test sequence file to the production server 1.
The production server 1 is configured to receive a target test sequence file sent by the process server 2, where the target test sequence file is a test sequence file with an update, and synchronize the target test sequence file to the production database 10.
The production database 10 or the process database 20 may be a relational database, such as Mysql database, maridb database, SQL Server database, Access database, or Oracle database. The production database 10 may also be a non-relational database, such as a Key-Value storage database, Column-Oriented database, Document-Oriented database, and the like.
Optionally, the test sequence file management system may further include at least one client 3, each client 3 is communicatively connected to the production server 1, and the client 3 is configured to send a query request to the production server 1, where the query request includes at least one query item.
The production server 1 inquires whether the production database 10 includes inquiry content corresponding to the inquiry item based on the inquiry item. If the production database 10 includes query contents corresponding to the query items, the query contents are sent to the client 3.
The client 3 updates the test sequence file according to the query content, wherein the query content includes the version number of the latest test sequence file and the latest test sequence file. In this way, real-time updating of the test sequence file at the client 3 is achieved.
According to the test sequence file management system provided by the embodiment of the application, under the condition that the test sequence file in the process server 2 is updated, the updated test sequence file is sent to the production server 1, so that the production server 1 can synchronize the updated test sequence file to the production database 10 included in the production server 1 in real time, the accuracy and consistency of the test sequence file are guaranteed, and the application timeliness of the test sequence file is improved.
The following describes in detail the steps of the test sequence file management method provided in the embodiment of the present application based on the schematic diagram of the test file management system shown in fig. 1.
Referring to fig. 2, fig. 2 is a flowchart illustrating a test sequence file management method according to an embodiment of the present disclosure. The production server 1 may synchronize the target test sequence file to the production database 10 by the following method.
In step S11, the target test sequence file sent by the flow server 2 is received.
Wherein, the target test sequence file is a test sequence file with update.
Step S12, the target test sequence file is synchronized to the production database 10.
Therefore, when the test sequence file in the process server 2 is updated, the updated target test sequence file can be updated to the production database 10 in the production server 1 in real time, so that the updating of the related test sequence file in the subsequent production line is facilitated, the accuracy and the consistency of the test sequence file are ensured, and the timeliness of the application of the test sequence file is improved.
As an alternative implementation, in step S1, the receiving of the target test sequence file sent by the flow server 2 may be implemented by:
and receiving the target test sequence file sent by the process server 2 when the updated test sequence file exists according to the first preset time interval.
Wherein the first preset time interval may be 1 minute, 2 minutes, 3 minutes, or the like. It will be appreciated that the shorter the time interval, the higher the timeliness of the presence of an updated target test sequence file sync, and that the longer the time interval, the lower the timeliness of the presence of an updated target test sequence file sync. The size of the first preset time interval can be determined according to actual needs.
For example, when the first preset time interval is 3 minutes, the process server 2 may query whether the test sequence file included in the process database 20 is updated according to the frequency of once every 3 minutes, and when it is queried that the test sequence file is updated, the updated test sequence file is used as a target test sequence file, and the target test sequence file is sent to the process server 2. It is convenient for the production server 1 to synchronize the target test sequence file to the production database 10 after receiving it. Therefore, the timeliness of the synchronization of the test sequence files with the updates is guaranteed.
As another alternative, in step S1, the receiving of the target test sequence file sent by the flow server 2 may also be implemented by:
and sending an updating query request to the process server 2 according to a second preset time interval, so that the process server 2 queries whether the test sequence file is updated or not based on the updating query request.
And receiving the target test sequence file returned by the flow server 2 based on the updating query request.
Wherein the second predetermined time interval may likewise be 1 minute, 2 minutes or 3 minutes, etc. It will be appreciated that the shorter the time interval, the higher the timeliness of the presence of an updated target test sequence file sync, and that the longer the time interval, the lower the timeliness of the presence of an updated target test sequence file sync. The size of the first preset time interval can be determined according to actual needs. Meanwhile, the second preset time interval may coincide with the first preset time interval.
For example, the second preset time interval may be consistent with the first preset time interval, and is 3 minutes, the production server 1 sends an update query request to the process server 2 every 3 minutes, and the process server 2 queries whether the test sequence file has an update based on the update query request after receiving the update query request. The updating of the test sequence file is convenient to find in time, and the timeliness of the synchronization of the updated test sequence file is ensured.
In an alternative embodiment, the production server 1 is further communicatively connected to the client 3, and the method further comprises:
receiving a query request sent by the client 3, wherein the query request comprises at least one query item.
Based on the query item, the production database 10 is queried as to whether query content corresponding to the query item is included.
If the production database 10 includes query contents corresponding to the query items, the query contents are sent to the client 3, so that the client 3 updates the test sequence file according to the query contents, wherein the query contents include the latest version number of the test sequence file and the latest test sequence file.
The query item may include ID information of the client 3 itself, an item name of a production line to which the client 3 belongs, a location of the production line to which the client 3 belongs, or a device type of the client 3.
For example, the production server 1 may query the production database 10 for query content corresponding to the query item based on the above-mentioned query item. For example, according to the item name of the production line to which the client 3 belongs, the test sequence file of the same item corresponding to the item name is found, and then based on the device type of the client 3, the latest test sequence file suitable for the device type and the version number of the latest test sequence file are found from the test sequence files of the same item.
And then, sending the version number of the latest test sequence file and the latest test sequence file to the client 3, so that the client 3 updates the test sequence file according to the version number of the latest test sequence file and the latest test sequence file.
Therefore, the test sequence file irrelevant to the client 3 can be prevented from being issued to the client 3, the test sequence file irrelevant to the project for which the client 3 is responsible is prevented from being updated, and therefore the updating accuracy and the production efficiency are improved.
In an alternative embodiment, the query content is sent to the client 3, so that the client 3 updates the test sequence file according to the query content can be implemented by:
a file download link is generated based on the latest test sequence file.
And taking the file download link and the version number of the latest test sequence file as query content.
And sending the query content to the client 3 so that the client 3 judges whether the test sequence file needs to be updated according to the version number, and if the test sequence file needs to be updated, acquiring the latest test sequence file according to the file download link and updating.
For example, if the version number of the latest test sequence file is 1.2.1 and the version number of the current test sequence file in the client 3 is 1.2.0, it may be determined that the test sequence file in the client 3 is updated, and at this time, the latest test sequence file is downloaded according to the file download link and the latest test sequence file with the version number of 1.2.1 is updated to the client 3.
Therefore, the risk of the test process caused by the update error of the test sequence file in the client 3 due to blind update is avoided.
Further, in order to make the update of the test sequence file more intuitive, an embodiment of the present application further provides a visual query method, and in an optional implementation, the visual query method may be implemented in the following manner:
and displaying a test sequence file query interface, wherein the test sequence file query interface displays file information of all validated test sequence files.
And responding to the query operation on the test sequence file query interface, acquiring target file information from the file information of all the validated test sequence files according to the query operation, and displaying the target file information.
Optionally, the test sequence file query interface may include at least one filter item, for example, the filter item may be an item name, an item number, and the like. In this way, the user can input the content corresponding to the screening items in the test sequence file query interface, so as to acquire and display the target file information from all validated test sequence files.
And the target file information or the file information of the validated test sequence file may include a streamer number, a submission date, an applicant, a project name, a project number, a version number, a station name, a device type, a description, the number of test sequence files, a virtual file view key, and the like.
Therefore, by changing the test sequence file query interface, a user can check the file information of all the test sequence files which take effect as required, and can easily acquire the target file information, thereby improving the use efficiency.
Referring to fig. 3, the process server 2 may obtain the updated test sequence file through the following steps, so that the production server 1 synchronizes the target test sequence file to the production database 10.
Step S21, query whether the test sequence file in the process database 20 has an update, and if it is determined that the updated test sequence file exists, obtain the updated test sequence file.
Step S22, sending the updated test sequence file as a target test sequence file to the production server 1, so that the production server 1 synchronizes the target test sequence file to the production database 10.
It can be understood that the process server 2 is configured to interface with a test sequence file publishing side, and when a user updates a test sequence file online, the test sequence file is uploaded to the process server 2 and stored in the process database 20 included in the process server 2, and when the process server 2 queries that the test sequence file in the process database 20 is updated, the updated test sequence file is sent to the production server 1, so that the production server 1 updates the test sequence file to the production database 10. Therefore, the accuracy and consistency of the test sequence file are ensured, and the timeliness of the application of the test sequence file is improved.
In an alternative embodiment, before querying whether the test sequence file in the process database 20 has an update, the process server 2 may further provide an audit process, and after the audit is passed, accept the issue operation of the user, as shown in the following steps:
and displaying an audit issuing interface, wherein the audit issuing interface comprises at least one to-be-filled file information item.
File information corresponding to each file information item is obtained in response to an information input operation for each file information item.
The test sequence file to be updated is generated based on the file information, and is saved in the flow database 20.
Optionally, the file item information to be filled out may include the applicant (i.e. the person who applies to issue the test sequence file), the application date, the item name, the item number, the version number, the station name, the device type (i.e. the device type to which the test sequence file is suitable), the description, and a virtual file upload button (which may be used to upload the test sequence file updated offline for review).
Therefore, before the test sequence file is officially released, the information of the test sequence file can be ensured to be complete and correct through auditing, errors in production line test caused by the fact that the test sequence file with information loss is updated are avoided, and production efficiency is reduced.
Meanwhile, as an optional implementation manner, after the audit is completed, the test sequence file to be updated is generated based on the file information and stored in the process database 20, and then the position 0 or the position 1 of the relevant flag may be set at the same time to indicate that the test sequence file in the process database 20 is updated. Therefore, the updated test sequence file is convenient to obtain, and the updating timeliness is improved.
Based on the above embodiment, optionally, in step S21, querying whether the test sequence file in the flow database 20 has an update may be implemented by:
as an alternative, whether there is an update in the test sequence file in the process database 20 may be queried at a first preset time interval.
The first preset time may be 1 minute, 2 minutes, 3 minutes, and the like. For example, it may be queried whether the flag bit is 1 every 3 minutes, and when the flag bit is 1, it indicates that there is an update in the test sequence file in the flow database 20, and when the flag bit is 0, it indicates that there is no update in the test sequence file in the flow database 20.
As another alternative, an update query request sent by the production server 1 may also be received. Based on the update query request, the test sequence file in the flow database 20 is queried for updates.
Optionally, the production server 1 may also send the query request at a preset time interval to improve the timeliness of the test sequence file update. Similarly, during query, whether the test sequence file in the flow database 20 is updated or not can be determined according to the state of the flag bit, so that the updated test sequence file can be conveniently obtained, and the updating timeliness is improved.
It should be understood that, although the steps in the flowcharts of fig. 2 to 3 are shown in sequence as indicated by the arrows, the steps are not necessarily performed in sequence as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.
Based on the same inventive concept, please refer to fig. 4 in combination, and fig. 4 is a functional block diagram of a test sequence file management apparatus according to an embodiment of the present application. In the embodiment of the present application, there is provided a first test sequence file management apparatus 11 corresponding to the test sequence file management method shown in fig. 2, the apparatus including:
the receiving module 111 is configured to receive a target test sequence file sent by the process server 2, where the target test sequence file is a test sequence file with an update.
A synchronization module 112 for synchronizing the target test sequence file to the production database 10.
In an alternative embodiment, the production server 1 is further communicatively connected to the client 3, and the apparatus further includes a response module, where the response module is configured to receive a query request sent by the client 3, where the query request includes at least one query item. Based on the query item, the production database 10 is queried as to whether query content corresponding to the query item is included. If the production database 10 includes query contents corresponding to the query items, the query contents are sent to the client 3, so that the client 3 updates the test sequence file according to the query contents, wherein the query contents include the latest version number of the test sequence file and the latest test sequence file.
In an alternative embodiment, the synchronization module 112 is further configured to generate a file download link based on the latest test sequence file. And taking the file download link and the version number of the latest test sequence file as query content. And sending the query content to the client 3 so that the client 3 judges whether the test sequence file needs to be updated according to the version number, and if the test sequence file needs to be updated, acquiring the latest test sequence file according to the file download link and updating.
In an optional embodiment, the receiving module 111 is further configured to receive the target test sequence file sent by the flow server 2 when it is found that the updated test sequence file exists according to the first preset time interval.
Or, the receiving module 111 is further configured to send an update query request to the process server 2 at a second preset time interval, so that the process server 2 queries whether the test sequence file has an update based on the update query request.
And receiving the target test sequence file returned by the flow server 2 based on the updating query request.
In an optional embodiment, the method further includes a file query module 211, where the file query module 211 is configured to display a test sequence file query interface, where the test sequence file query interface displays file information of all validated test sequence files. And responding to the query operation on the test sequence file query interface, acquiring target file information from the file information of all the validated test sequence files according to the query operation, and displaying the target file information.
Since the principle of the apparatus in the embodiment of the present application to solve the problem is similar to the steps of the test sequence file management method in fig. 2 shown in the embodiment of the present application, the implementation principle of the apparatus may refer to the implementation principle of the method, and repeated details are not repeated. The respective modules in the first test sequence file management apparatus 11 may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
Based on the same inventive concept, please refer to fig. 5, in which fig. 5 is a second functional block diagram of the test sequence file management apparatus according to the embodiment of the present application. In the embodiment of the present application, there is further provided a second test sequence file management apparatus 21 corresponding to the test sequence file management method shown in fig. 3, the apparatus including:
the query module 211 is configured to query whether the test sequence file in the process database 20 is updated, and if it is determined that the updated test sequence file exists, obtain the updated test sequence file.
A sending module 212, configured to send the updated test sequence file to the production server 1 as a target test sequence file, so that the production server 1 synchronizes the target test sequence file to the production database 10.
In an alternative embodiment, the apparatus further comprises:
and the display module is used for displaying an audit release interface, wherein the audit release interface comprises at least one file information item to be filled.
File information corresponding to each file information item is obtained in response to an information input operation for each file information item.
The test sequence file to be updated is generated based on the file information, and is saved in the flow database 20.
In an optional embodiment, the query module 211 is further configured to query whether the test sequence file in the process database 20 has an update according to a first preset time interval.
Alternatively, the query module 211 is further configured to receive an update query request sent by the production server 1. Based on the update query request, the test sequence file in the flow database 20 is queried for updates.
Since the principle of the apparatus in the embodiment of the present application to solve the problem is similar to the steps of the test sequence file management method in fig. 3 shown in the embodiment of the present application, the implementation principle of the apparatus may refer to the implementation principle of the method, and repeated details are not repeated. The respective modules in the second test sequence file management means 21 described above may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In summary, the embodiment of the present application provides a method, an apparatus, and a system for managing a test sequence file, where the updated test sequence file is sent to the production server 1 under the condition that the test sequence file in the process server 2 is updated, so that the production server 1 can synchronize the updated test sequence file to the production database 10 included in the production server 1 in real time, thereby ensuring the accuracy and consistency of the test sequence file, and improving the timeliness of the application of the test sequence file.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (11)
1. The test sequence file management method is applied to a production server comprising a production database, wherein the production server is in communication connection with a process server; the method comprises the following steps:
receiving a target test sequence file sent by the process server, wherein the target test sequence file is a test sequence file with an update;
and synchronizing the target test sequence file to the production database.
2. The test sequence file management method of claim 1, wherein the production server is further communicatively coupled to a client, the method further comprising:
receiving a query request sent by a client, wherein the query request comprises at least one query item;
querying whether the production database comprises query content corresponding to the query item or not based on the query item;
and if the production database comprises query contents corresponding to the query items, sending the query contents to the client so that the client updates the test sequence file according to the query contents, wherein the query contents comprise the latest version number of the test sequence file and the latest test sequence file.
3. The method according to claim 2, wherein the step of sending the query content to the client so that the client updates the test sequence file according to the query content comprises:
generating a file download link based on the latest test sequence file;
taking the file downloading link and the version number of the latest test sequence file as query contents;
and sending the query content to the client so that the client judges whether the test sequence file needs to be updated according to the version number, and if the test sequence file needs to be updated, acquiring the latest test sequence file according to the file download link and updating.
4. The method according to claim 1, wherein the step of receiving the target test sequence file sent by the process server comprises:
receiving a target test sequence file sent by the process server when the updated test sequence file exists according to a first preset time interval; alternatively, the first and second electrodes may be,
sending an updating query request to the process server according to a second preset time interval so that the process server queries whether the test sequence file is updated or not based on the updating query request;
and receiving a target test sequence file returned by the process server based on the updating query request.
5. The test sequence file management method of claim 1, further comprising:
displaying a test sequence file query interface, wherein the test sequence file query interface displays file information of all validated test sequence files;
and responding to the query operation on the test sequence file query interface, acquiring target file information from the file information of all the validated test sequence files according to the query operation, and displaying the target file information.
6. The test sequence file management method is applied to a process server comprising a process database, wherein the process server is in communication connection with a production server, and the production server comprises a production database; the method comprises the following steps:
inquiring whether the test sequence file in the process database is updated or not, and if the updated test sequence file is determined to exist, acquiring the updated test sequence file;
and sending the updated test sequence file as a target test sequence file to the production server so that the production server synchronizes the target test sequence file to the production database.
7. The test sequence file management method of claim 6, further comprising:
displaying an audit release interface, wherein the audit release interface comprises at least one file information item to be filled;
responding to information input operation aiming at each file information item, and obtaining file information corresponding to each file information item;
and generating a test sequence file to be updated based on the file information, and storing the test sequence file to be updated in the process database.
8. The test sequence file management method according to claim 6, wherein the step of querying whether the test sequence file in the process database has an update comprises:
inquiring whether the test sequence file in the process database is updated or not according to a first preset time interval; alternatively, the first and second electrodes may be,
receiving an updating query request sent by the production server;
and inquiring whether the test sequence file in the process database is updated or not based on the updating inquiry request.
9. The test sequence file management device is applied to a production server comprising a production database, and the production server is in communication connection with a process server; the device comprises:
the first receiving module is used for receiving a target test sequence file sent by the process server, wherein the target test sequence file is a test sequence file with an update;
and the synchronization module is used for synchronizing the target test sequence file to the production database.
10. The test sequence file management device is applied to a process server comprising a process database, wherein the process server is in communication connection with a production server, and the production server comprises a production database; the device comprises:
the query module is used for querying whether the test sequence file in the process database is updated or not, and if the updated test sequence file is determined to exist, the updated test sequence file is obtained;
and the sending module is used for sending the updated test sequence file serving as a target test sequence file to the production server so that the production server synchronizes the target test sequence file to the production database.
11. The test sequence file management system is characterized by comprising a production server and a process server which are in communication connection, wherein the production server comprises a production database, and the process server comprises a process database;
the process server is used for inquiring whether the test sequence file in the process database is updated or not, and if the updated test sequence file is determined to exist, acquiring the updated test sequence file; sending the updated test sequence file as a target test sequence file to the production server;
the production server is used for receiving a target test sequence file sent by the process server, wherein the target test sequence file is a test sequence file with an update, and the target test sequence file is synchronized to the production database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110009305.9A CN112597178A (en) | 2021-01-05 | 2021-01-05 | Test sequence file management method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110009305.9A CN112597178A (en) | 2021-01-05 | 2021-01-05 | Test sequence file management method, device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112597178A true CN112597178A (en) | 2021-04-02 |
Family
ID=75206915
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110009305.9A Pending CN112597178A (en) | 2021-01-05 | 2021-01-05 | Test sequence file management method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112597178A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254032A (en) * | 2021-05-07 | 2021-08-13 | 杭州广立微电子股份有限公司 | Probe card record file updating module, system and method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070244905A1 (en) * | 2006-04-14 | 2007-10-18 | Fujitsu Limited | Computer-readable recording medium containing application management program, and method and apparatus for application management |
| US20140281732A1 (en) * | 2013-03-15 | 2014-09-18 | Red Hat, Inc. | Automated update testing and deployment |
| CN108182075A (en) * | 2017-12-29 | 2018-06-19 | 成都三零凯天通信实业有限公司 | A kind of program by the automatic escalation target software of socket communication modes |
| CN109101381A (en) * | 2018-08-02 | 2018-12-28 | Oppo（重庆）智能科技有限公司 | Configuration file update method, system, electronic equipment and storage medium |
| CN111399873A (en) * | 2015-10-26 | 2020-07-10 | 阿里巴巴集团控股有限公司 | Model updating method and device |
-
2021
- 2021-01-05 CN CN202110009305.9A patent/CN112597178A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070244905A1 (en) * | 2006-04-14 | 2007-10-18 | Fujitsu Limited | Computer-readable recording medium containing application management program, and method and apparatus for application management |
| US20140281732A1 (en) * | 2013-03-15 | 2014-09-18 | Red Hat, Inc. | Automated update testing and deployment |
| CN111399873A (en) * | 2015-10-26 | 2020-07-10 | 阿里巴巴集团控股有限公司 | Model updating method and device |
| CN108182075A (en) * | 2017-12-29 | 2018-06-19 | 成都三零凯天通信实业有限公司 | A kind of program by the automatic escalation target software of socket communication modes |
| CN109101381A (en) * | 2018-08-02 | 2018-12-28 | Oppo（重庆）智能科技有限公司 | Configuration file update method, system, electronic equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254032A (en) * | 2021-05-07 | 2021-08-13 | 杭州广立微电子股份有限公司 | Probe card record file updating module, system and method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8122040B2 (en) | Method of integrating remote databases by automated client scoping of update requests over a communications network | |
| CN103984715B (en) | Data synchronizing and checking method, device and system of isomerous database | |
| US7899783B1 (en) | Monitoring data integrity | |
| CN103020058B (en) | A kind of multi-version data acquisition method and device | |
| EP2767912A2 (en) | In-memory real-time synchronized database system and method | |
| CN112699151B (en) | Data processing method, device, equipment and medium | |
| US8280847B2 (en) | Apparatus, method, and computer program product for synchronizing data sources | |
| CN111427951A (en) | Data synchronization method and device, computer equipment and storage medium | |
| CN112597178A (en) | Test sequence file management method, device and system | |
| US20080133543A1 (en) | System and Method for Dynamic and On-Demand Data Transfer and Synchronization Between Isolated Networks | |
| CN111078672A (en) | Data comparison method and device for database | |
| CN112100275A (en) | Data synchronization method, system and electronic equipment | |
| CN113742325A (en) | Data warehouse construction method, device and system, electronic equipment and storage medium | |
| CN106341449B (en) | Method of data synchronization and device | |
| CN112416991A (en) | Data processing method and device and storage medium | |
| CN110515909B (en) | File storage method and device, electronic equipment and computer storage medium | |
| CN115756889A (en) | Task center architecture method for double data buses of aerospace measurement and control ground station network | |
| CN115113989B (en) | Transaction execution method, device, computing equipment and storage medium | |
| JP2011019161A (en) | Database access program, data acquisition apparatus and database access method | |
| CN113645309A (en) | Processing method and system for multi-client data differentiation secondary caching and synchronization | |
| CN111949731A (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN114372081B (en) | Data preparation method, device and equipment | |
| CN111339100A (en) | Data checking method and device | |
| CN115190015A (en) | Soft load system configuration method and device, computer equipment and storage medium | |
| US20220179879A1 (en) | Systems and methods for intermittent synchronizing of customer relationship management local application clients |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |