Test task-based test data acquisition method and apparatus, and electronic device

Abstract

The invention relates to the technical field of data acquisition, in particular to a test task-based test data acquisition method and device and electronic equipment. Comprising the steps of responding to an issuing instruction of a test task, and analyzing an equipment identifier associated with the test task; creating a special folder associated with the test task in the target industrial personal computer based on the equipment identifier; receiving test data collected in a test execution process, and automatically storing the test data in a special folder; newly added data files in the special folder are detected through periodic scanning; and when a newly added data file is detected, automatically uploading the newly added data file to a file server storage path associated with the test task. The defects that manual uploading operation of traditional test data acquisition is complex, and a corresponding relation between a test task and test data needs to be manually corresponded are overcome. The production efficiency of collecting test data for enterprises is greatly improved, and the use convenience of testers is improved.

Description

Technical Field

[0001] The present application relates to the field of data acquisition technology, and in particular to a method, device and electronic equipment for acquiring test data based on a test task. Background Art

[0002] Most companies collect test data manually by uploading the collected data to a dedicated test data management system. This method involves first saving the test data collected by the test equipment on the hard drive of the computer dedicated to the test equipment. Since the industrial computer cannot be connected to the company's OA network, the data in the industrial computer needs to be copied to the office computer using a mobile hard drive or a dedicated network. The office computer then logs into the test data management system and uploads the local test data to the designated location of the test data management system.

[0003] Manual upload of test data to a designated location in the test data management system is complex. This requires high levels of competence and responsibility from test personnel, and cannot guarantee timely and complete data collection. Furthermore, upload time and network requirements are high, requiring a connection between the test equipment's dedicated network and the company's OA network, and placing high security requirements on the dedicated test network.

[0004] Therefore, a method is needed to automatically collect test data for test tasks. Summary of the Invention

[0005] In view of this, the embodiments of the present application provide a test data collection method, device, electronic device and computer program product based on a test task to solve the problem that the test data is stored on the test engineer's personal computer, cannot be associated with the test task, and cannot realize the automatic collection of test data for the test task.

[0006] A first aspect of an embodiment of the present application provides a test data collection method based on a test task, comprising: Responding to the test task's issuing instruction, parsing the device identification associated with the test task; Creating a dedicated folder associated with the test task on the target industrial computer based on the device identifier; Receive test data collected during the test execution and automatically store it in the dedicated folder; Detecting new data files in the dedicated folder through periodic scanning; When a new data file is detected, the new data file is automatically uploaded to the file server storage path associated with the test task.

[0007] In one embodiment, responding to the instruction to issue the test task and parsing the device identifier associated with the test task includes: Responding to the test task's issuing instruction, parsing the task identifier of the test task and the associated device identifier; The task identifier includes a task number and a task name.

[0008] In one embodiment, creating a dedicated folder associated with the test task on the target industrial computer based on the device identifier includes: Locating the target industrial computer according to the device identifier, and dynamically creating a dedicated folder under a specified storage path of the target industrial computer; The dedicated folder is named with a combination of the task number and the task name.

[0009] In one embodiment, the dynamically creating a dedicated folder includes: Verify the write permission to the target industrial computer storage path; Detecting the existence of the dedicated folder; If a folder with the same name does not exist, a folder name that complies with the file system specifications is generated and the folder is created.

[0010] In one embodiment, detecting new data files in the dedicated folder through periodic scanning includes: Scanning the dedicated folder via a time-triggered incremental detection program; Newly added data files in the dedicated folder are identified based on a time base perception algorithm.

[0011] In one embodiment, the identifying the newly added data files in the dedicated folder based on the time reference perception algorithm includes: Record the system clock stamp as the reference time anchor point during the first scan; In subsequent scanning cycles, newly added data files are identified by comparing the deviation value between the file modification time and the reference time anchor point.

[0012] In one embodiment, in a subsequent scanning cycle, identifying a newly added data file by comparing the file modification time with the deviation value of the reference time anchor point includes: Extract modification timestamps and status change timestamps of files within the scanning period; Taking the modification timestamp and the state change timestamp as inputs of a multidimensional time model, calculating the Euclidean distance between the multidimensional time model and the reference time anchor point; When the Euclidean distance exceeds a preset threshold, the corresponding file is marked as a new data file.

[0013] A second aspect of an embodiment of the present application provides a test data acquisition device based on a test task, comprising: A data acquisition module is used to respond to the instruction of the test task and analyze the device identification associated with the test task; A folder creation module, configured to create a dedicated folder associated with the test task on the target industrial computer based on the device identifier; A storage module, used to receive the test data collected during the test execution and automatically store it in the dedicated folder; A scanning module, configured to detect new data files in the dedicated folder through periodic scanning; The file uploading module is used to automatically upload the newly added data file to the file server storage path associated with the test task when a newly added data file is detected.

[0014] A third aspect of an embodiment of the present application provides an electronic device, comprising a processor, a memory, and a computer program stored in the memory and runnable on the processor. When the processor executes the computer program, the electronic device implements the test data collection method based on the test task provided in the first aspect of the embodiment of the present application.

[0015] A fourth aspect of the embodiments of the present application provides a computer program product, including a computer program. When the computer program is executed, the method according to the first aspect of the embodiments of the present application is executed.

[0016] The first aspect of the embodiment of the present application provides a test data collection method based on a test task, which analyzes the device identification associated with the test task by responding to the instruction issued by the test task; creates a dedicated folder associated with the test task on the target industrial computer based on the device identification; receives the test data collected during the test execution and automatically stores it in the dedicated folder; detects the new data files in the dedicated folder through periodic scanning; when a new data file is detected, automatically uploads the new data file to the file server storage path associated with the test task. Through a task-driven automated process, device identification parsing, dedicated folder creation, test data storage, incremental file detection and automatic upload are integrated into a closed-loop system, solving the problems of omissions and poor timeliness caused by manual operation; isolates different test environments with tasks as units to ensure the independence and integrity of data collection, and reduces system resource usage through a periodic scanning mechanism to achieve lightweight incremental detection. It solves the defects of traditional test data collection manual upload operations that are complex and require manual correspondence between test tasks and test data. It greatly improves the production efficiency of enterprise test data collection and improves the convenience of use for test personnel.

[0017] It can be understood that the beneficial effects of the second to fourth aspects mentioned above can be found in the relevant description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0019] Figure 1 This is a flow chart of a test data collection method based on a test task provided in one embodiment of the present application; Figure 2 This is a flow chart of a test data collection method based on a test task provided by another embodiment of the present application; Figure 3 This is a flow chart of a test data collection method based on a test task provided by another embodiment of the present application; Figure 4 Schematic diagram of the structure of the test data acquisition device based on the test task provided in the embodiment of the present application; Figure 5 It is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] In the following description, specific details such as specific system structures and techniques are provided for purposes of illustration rather than limitation to facilitate a thorough understanding of the embodiments of the present application. However, it will be apparent to those skilled in the art that the present application may be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid obscuring the description of the present application with unnecessary detail.

[0021] It should be understood that when used in the present specification and the appended claims, the term "comprising" indicates the presence of described features, integers, steps, operations, elements and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or collections thereof.

[0022] It will also be understood that the term "and / or" used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

[0023] As used in this specification and the appended claims, the term "if" can be interpreted as "when" or "upon" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrase "if it is determined" or "if [described condition or event] is detected" can be interpreted as meaning "upon determination" or "in response to determining" or "upon detection of [described condition or event]" or "in response to detecting [described condition or event]," depending on the context.

[0024] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0025] like Figure 1 As shown, the test data collection method based on the test task provided in the embodiment of the present application includes the following steps S101 to S105: Step S101: responding to an instruction to issue a test task, parsing a device identifier associated with the test task.

[0026] In the application, test tasks are issued through the test data management system. Test tasks have unique task numbers. By extracting the task number and name, the corresponding fields are pushed to the industrial computer corresponding to the designated test bench equipment.

[0027] In applications, such as Figure 2 As shown, the method provided in the embodiment of the present application is executed by the DTMS system (test data management system). The test manager publishes a task order on the test data management system. After receiving the task, the DTMS system prepares for the test.

[0028] Step S102: creating a dedicated folder associated with the test task on the target industrial computer based on the device identification.

[0029] In the application, the DTMS system parses the device ID associated with the test task and associates the test bench with it. Click Start to extract the data. A folder named with the task number is automatically created in the specified location on the industrial computer.

[0030] Step S103: receiving the test data collected during the test execution process and automatically storing it in a dedicated folder.

[0031] In the application, test data is collected during the execution of the test task and automatically stored in a specific folder on the industrial computer. In addition, the industrial computer can also delete the folder.

[0032] Step S104: Detect new data files in the dedicated folder through periodic scanning.

[0033] In the application, a collection and scanning program is installed on the industrial computer. This program uses a data increment algorithm to automatically scan a specific folder at a fixed time point to check whether there is incremental test data stored in the folder. If so, the incremental data is copied to the file server repository.

[0034] Step S105: When a new data file is detected, the new data file is automatically uploaded to the file server storage path associated with the test task.

[0035] In the application, when incremental data is scanned, the system automatically uploads it to the designated location of the test data management system. This does not rely on real-time network connectivity; as long as the network is connected, it will automatically upload. The upload speed is fast, the data volume is minimal, and no manual intervention is required.

[0036] In the application, testers can search for historical test data based on information such as task number, project name, executing department, and test personnel. Data can be located based on different dimensions, including project information, task information, time information, key characteristics, executing organization, and personnel. Downloaded data can be uploaded to a workstation for analysis.

[0037] The embodiment of the present application automatically completes the upload of test data by automatically creating a dedicated folder. Compared with the traditional manual upload of test data, the test personnel need to match the test tasks with the data before the data can be uploaded to the enterprise data management system. This solution automatically scans the incremental data change signals of the dedicated folder regularly through the program, and automatically uploads the data to the file storage server associated with the test task. By forcibly associating with the test task, the test task is forcibly associated with information such as product development projects, test equipment, test execution departments, and test personnel, which facilitates later data search and application. New data files in the dedicated folder are detected through periodic scanning; when new data files are detected, the new data files are automatically uploaded to the file server storage path associated with the test task. Through a task-driven automated process, device identification resolution, dedicated folder creation, test data storage, incremental file detection and automatic upload are integrated into a closed-loop system, solving the problems of omissions and poor timeliness caused by manual operations; different test environments are isolated by tasks to ensure the independence and integrity of data collection, while the periodic scanning mechanism reduces system resource usage and realizes lightweight incremental detection. This solves the problem of traditional test data collection and uploading, which is complicated and requires manual mapping of test tasks and test data. It significantly improves the efficiency of test data collection for enterprises and improves the convenience of use for test personnel.

[0038] In one embodiment, responding to the instruction to issue the test task and parsing the device identifier associated with the test task includes: Responding to the test task's issuing instruction, parsing the task identifier of the test task and the associated device identifier; The task identifier includes a task number and a task name.

[0039] The embodiment of the present application enhances the binding accuracy of tasks and devices through a dual verification mechanism of parsing task identifiers and device identifiers; the structured definition of task numbers and names provides standardized input for subsequent folder creation, avoiding path conflicts caused by ambiguous identifiers, and improving the orderliness of data classification storage from the source.

[0040] In one embodiment, creating a dedicated folder associated with the test task on the target industrial computer based on the device identifier includes: Locating the target industrial computer according to the device identifier, and dynamically creating a dedicated folder under a specified storage path of the target industrial computer; The dedicated folder is named with a combination of the task number and the task name.

[0041] In the application, the test data management system extracts a specific test task number and the device number associated with the task, automatically associates the device number with the industrial computer that controls the device, and the computer dynamically generates a folder named with the task number and name at the specified location of the industrial computer.

[0042] The embodiment of the present application dynamically locates the target industrial computer based on the device identification, and names the dedicated folder with a combination of fields, thereby achieving a strong association between the storage path and the task logic; this design ensures the uniqueness of the folder naming during multi-tasking concurrency, while making the file server storage path traceable, significantly reducing the risk of data mismatch.

[0043] In one embodiment, the dynamically creating a dedicated folder includes: Verify the write permission to the target industrial computer storage path; Detecting the existence of the dedicated folder; If a folder with the same name does not exist, a folder name that complies with the file system specifications is generated and the folder is created.

[0044] In the application, use the file system to traverse the files or subfolders in the target folder and obtain the file / folder information that needs to be processed.

[0045] After generating the folder name, check to see if the folder already exists. If not, create it.

[0046] Make sure the generated folder name is legal and will not cause path parsing errors. Also, make sure the script has sufficient permissions to create the folder in the target directory.

[0047] The embodiment of the present application solves the problem of creation failure caused by insufficient permissions, path conflicts or illegal naming through a three-level protection mechanism of write permission verification, folder existence status detection and name compliance verification; this process enhances the robustness of the system and is particularly suitable for industrial control environments with high security requirements.

[0048] In one embodiment, detecting new data files in the dedicated folder through periodic scanning includes: Scanning the dedicated folder via a time-triggered incremental detection program; Newly added data files in the dedicated folder are identified based on a time base perception algorithm.

[0049] The incremental detection program triggered by time in the embodiment of the present application is combined with a time base perception algorithm to process only newly added data files, reducing I / O load and computing overhead. At the same time, it dynamically calibrates the scanning base through time anchor points to avoid missed detections due to system clock drift.

[0050] In one embodiment, the identifying the newly added data files in the dedicated folder based on the time reference perception algorithm includes: Record the system clock stamp as the reference time anchor point during the first scan; In subsequent scanning cycles, newly added data files are identified by comparing the deviation value between the file modification time and the reference time anchor point.

[0051] The embodiment of the present application uses the first scan system clock stamp as the benchmark anchor point and quantifies the relative change of the file modification time through the deviation value; it breaks through the limitation of the fixed time window and adaptively identifies files with different generation frequencies, which is particularly suitable for long-cycle test scenarios and effectively reduces the misjudgment rate.

[0052] In one embodiment, in a subsequent scanning cycle, identifying a newly added data file by comparing the file modification time with the deviation value of the reference time anchor point includes: Extract modification timestamps and status change timestamps of files within the scanning period; Taking the modification timestamp and the state change timestamp as inputs of a multidimensional time model, calculating the Euclidean distance between the multidimensional time model and the reference time anchor point; When the Euclidean distance exceeds a preset threshold, the corresponding file is marked as a new data file.

[0053] In the application, a time-based incremental detection algorithm is designed. The algorithm model is to build an intelligent file incremental detection system based on time-series fingerprint comparison technology to achieve accurate data capture of the target folder: The initial time anchor point is constructed through the file system metadata index, and the system clock stamp of the first scan time is recorded as the reference coordinate for subsequent incremental judgment.

[0054] Design a sliding time window algorithm that performs the following steps in each scanning cycle: a) Extract the mtime (modification time) and ctime (status change time) from the file system metadata b) Construct a multi-dimensional time model and perform similarity calculation with LastScanTime.

[0055] c) When the Euclidean distance exceeds the threshold (i.e., the file timestamp is significantly later than the benchmark time), the incremental data marking mechanism is triggered.

[0056] After obtaining the incremental data file mark, the system automatically crawls the marked files and data to the set storage server.

[0057] In applications, building a multidimensional time model means using mtime and ctime as two dimensions (e.g., a two-dimensional vector) to jointly participate in similarity calculation. Similarity calculation is expressed through the relationship between Euclidean distance and threshold. Euclidean distance is a vector composed of mtime and ctime and a reference time anchor (LastScanTime). Let the reference time anchor be , for each file, the extracted timestamp data is: modification time and status change time The Euclidean distance calculation formula is: ; when >When the preset threshold is reached, the file is marked as new data.

[0058] The embodiment of the present application fuses the dual features of the modification timestamp and the state change timestamp through a multidimensional time model, and calculates the Euclidean distance between them and the reference anchor point; this model solves the problem of insufficient sensitivity of a single time series feature, uses the distance threshold of the vector space to determine newly added files, and improves the accuracy of incremental recognition in complex scenarios.

[0059] The present application embodiment uses a bench test data automatic collection embodiment to illustrate the above method flow: like Figure 3 As shown in the figure, the test manager of a vehicle development project issued a test task with the task code LJ24060317. The task name is the supplementary fatigue test of the front leaf spring assembly of a certain vehicle model 2912010-KT633.

[0060] The test task is published in the Test Operations Management System (DTMS). After receiving the task, the tester links the corresponding test bench equipment (six-channel electro-hydraulic servo system-4#) on the corresponding interface and determines the test start and end time.

[0061] Click the test start button, and the DTMS system will automatically push the task order name + code field to the industrial computer associated with the test bench, and create a file named " The test bench conducts physical tests according to the test outline. When the test process ends, the tester clicks "End of test" and the bench equipment program collects the test data and stores the test data in a dedicated folder.

[0062] The test operations management system automatically scans the IPC folders at regular intervals. If new data is found within the folders, it automatically copies the new data over the network to a designated file server, where the storage path is associated with the test task. The system displays a corresponding test data package or file under this task. After the test task is completed, the system allows the tester to delete the designated folder on the IPC, completing the automatic collection of test data.

[0063] When the test personnel inquire about or use the test data, they can find the corresponding test task sheet in the test operation management system by querying the task number, project number, project name, operating equipment, test executor, execution unit, execution time and other information. The corresponding test data location will be displayed, and the data will be downloaded to the local computer. The data will be processed using professional test data analysis software to analyze and compile a test report.

[0064] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0065] The present application also provides a test task-based test data acquisition device for performing the steps of the test task-based test data acquisition method described above. The test task-based test data acquisition device can be a virtual appliance in an electronic device, run by a processor of the electronic device, or it can be the electronic device itself.

[0066] like Figure 4 As shown, the test data acquisition device 100 based on the test task provided in the embodiment of the present application includes: The data acquisition module 101 is used to respond to the instruction of issuing a test task and analyze the device identification associated with the test task; A folder creation module 102 is configured to create a dedicated folder associated with the test task on the target industrial computer based on the device identifier; The storage module 103 is used to receive the test data collected during the test execution and automatically store it in the dedicated folder; The scanning module 104 is configured to detect new data files in the dedicated folder through periodic scanning; The file uploading module 105 is configured to automatically upload a new data file to a file server storage path associated with the test task when a new data file is detected.

[0067] In application, each module in the test data acquisition device based on the test task may be a software program module, or may be implemented by different logic circuits integrated in a processor, or may be implemented by multiple distributed processors.

[0068] like Figure 5 As shown, the embodiment of the present application further provides an electronic device 200, including: at least one processor 201 ( Figure 5 Only one processor is shown in the figure), a memory 202, and a computer program 203 stored in the memory 202 and executable on at least one processor 201. When the processor 201 executes the computer program 203, the steps in the above-mentioned method embodiments are implemented.

[0069] In applications, electronic devices may include, but are not limited to, processors and memories. Those skilled in the art will appreciate that Figure 5 The electronic device is merely an example and does not limit the electronic device. The electronic device may include more or fewer components than shown in the figure, or may include a combination of certain components or different components.

[0070] In applications, a processor may be a central processing unit (CPU), other general-purpose processors, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0071] In applications, in some embodiments, memory can be an internal storage unit of an electronic device, such as a hard drive or memory. In other embodiments, memory can also be an external storage device of the electronic device, such as a plug-in hard drive, a Smart Media Card (SMC), a Secure Digital (SD) card, or a flash memory card. Furthermore, memory can include both internal storage units and external storage devices. Memory is used to store operating systems, application programs, boot loaders, data, and other programs, such as computer program code. Memory can also be used to temporarily store data that has been output or is about to be output.

[0072] It should be noted that the information interaction, execution process, etc. between the above-mentioned devices / units are based on the same concept as the method embodiment of this application. Their specific functions and technical effects can be found in the method embodiment section and will not be repeated here.

[0073] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiment can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of this application. The specific working process of the units and modules in the above-mentioned system can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here.

[0074] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0075] An embodiment of the present application provides a computer program product, including a computer program. When the computer program product runs on an electronic device, the electronic device can implement the steps in the above-mentioned various method embodiments when executing the computer program product.

[0076] If the integrated unit is implemented as a software functional unit and sold or used as a standalone product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application can implement all or part of the process steps in the above-mentioned method embodiments by using a computer program to instruct the relevant hardware. The computer program can be stored in a computer-readable storage medium. When executed by a processor, the computer program can implement the steps of each of the above-mentioned method embodiments. The computer program includes computer program code, which can be in source code form, object code form, executable file, or some intermediate form. Computer-readable media can include at least: any entity or device capable of carrying computer program code to a device / electronic device, recording media, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signals, telecommunication signals, and software distribution media. Examples include USB flash drives, removable hard drives, magnetic disks, or optical disks. In some jurisdictions, based on legislation and patent practice, computer-readable media cannot be electric carrier signals or telecommunication signals.

[0077] In the above embodiments, the description of each embodiment has its own focus. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0078] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0079] In the embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0081] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the scope of protection of the present application.

Claims

1. A test data collection method based on a test task, characterized in that: include: Responding to the test task's issuing instruction, parsing the device identification associated with the test task; Creating a dedicated folder associated with the test task on the target industrial computer based on the device identifier; Receive test data collected during the test execution and automatically store it in the dedicated folder; Detecting new data files in the dedicated folder through periodic scanning; When a new data file is detected, the new data file is automatically uploaded to the file server storage path associated with the test task.

2. The test data collection method based on the test task according to claim 1, characterized in that: The step of responding to the instruction of issuing the test task and parsing the device identification associated with the test task includes: Responding to the test task's issuing instruction, parsing the task identifier of the test task and the associated device identifier; The task identifier includes a task number and a task name.

3. The test data collection method based on the test task according to claim 2, characterized in that: The step of creating a dedicated folder associated with the test task on the target industrial computer based on the device identifier includes: Locating the target industrial computer according to the device identifier, and dynamically creating a dedicated folder under a specified storage path of the target industrial computer; The dedicated folder is named with a combination of the task number and the task name.

4. The test data collection method based on test tasks according to claim 2, characterized in that: The dynamic creation of a dedicated folder includes: Verify the write permission to the target industrial computer storage path; Detecting the existence of the dedicated folder; If a folder with the same name does not exist, a folder name that complies with the file system specifications is generated and the folder is created.

5. The test data collection method based on test tasks according to claim 1, characterized in that: The detecting new data files in the dedicated folder by periodic scanning includes: Scanning the dedicated folder by a time-triggered incremental detection program; Newly added data files in the dedicated folder are identified based on a time base perception algorithm.

6. The test data collection method based on test tasks according to claim 5, characterized in that: The identifying of the newly added data files in the dedicated folder based on the time base perception algorithm includes: Record the system clock stamp as the reference time anchor point during the first scan; In subsequent scanning cycles, newly added data files are identified by comparing the deviation value between the file modification time and the reference time anchor point.

7. The test data collection method based on test tasks according to claim 5, characterized in that: In subsequent scanning cycles, newly added data files are identified by comparing the file modification time with the deviation value of the reference time anchor point, including: Extract modification timestamps and status change timestamps of files within the scanning period; Taking the modification timestamp and the state change timestamp as inputs of a multidimensional time model, calculating the Euclidean distance between the multidimensional time model and the reference time anchor point; When the Euclidean distance exceeds a preset threshold, the corresponding file is marked as a new data file.

8. A test data acquisition device based on a test task, characterized in that: include: A data acquisition module is used to respond to the instruction of the test task and analyze the device identification associated with the test task; A folder creation module, configured to create a dedicated folder associated with the test task on the target industrial computer based on the device identifier; A storage module, used to receive the test data collected during the test execution and automatically store it in the dedicated folder; A scanning module, configured to detect new data files in the dedicated folder through periodic scanning; The file uploading module is used to automatically upload the newly added data file to the file server storage path associated with the test task when a newly added data file is detected.

9. An electronic device, characterized in that: The electronic device comprises a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the electronic device implements the method according to any one of claims 1 to 7.

10. A computer program product, characterized in that The invention comprises a computer program, which, when being executed, enables the method according to any one of claims 1 to 7 to be performed.

Images