Computer hardware automated testing method, device, equipment, storage medium and computer program product

Abstract

The application relates to the field of computer software and automatic test technology, and particularly relates to a computer hardware automatic test method, device and equipment, a storage medium and a computer program product. The method comprises the following steps: obtaining equipment identification information and hardware configuration description information of a target computer, and generating corresponding equipment basic data; reading test flow configuration data corresponding to the equipment basic data, and obtaining flow organization relationship and execution association information of a plurality of to-be-executed test units by analysis; scheduling and controlling the plurality of to-be-executed test units based on the flow organization relationship and the execution association information, calling corresponding external test programs to execute test processing, and obtaining process output information; determining the execution state of each to-be-executed test unit according to the process output information, and generating test state data associated with the equipment basic data; and finally, storing test progress, displaying test results and generating test record data based on the test state data.

Description

Technical Field

[0001] This application relates to the field of computer software and automated testing technology, and in particular to a computer hardware automated testing method, apparatus, equipment, storage medium and computer program product. Background Technology

[0002] During the manufacturing process of computer hardware products, the processor, memory, graphics processing unit, storage medium, motherboard, network adapter, and firmware information of the device under test are typically tested before leaving the factory. This testing involves calling appropriate test programs based on different product models, production stations, and testing tasks. In existing technologies, such testing often relies on manual intervention with multiple independent programs. Testers typically need to manually organize device information, select test items, call test programs, and judge test results, resulting in a low level of automation. Furthermore, existing testing methods often lack a unified process organization and scheduling mechanism between different test programs, and there is a lack of effective correlation between test status, process output, and test records. This easily leads to problems such as disjointed test flow, fragmented test status management, and incomplete test records. Especially in cases of test interruption, abnormal shutdown, or station switching, existing solutions struggle to continuously store and uniformly manage test progress, resulting in poor efficiency in computer hardware production testing. Therefore, improving the efficiency of computer hardware production testing is a pressing issue that needs to be addressed. Summary of the Invention

[0003] The main purpose of this application is to provide a method, apparatus, equipment, storage medium, and computer program product for automated testing of computer hardware, aiming to solve the technical problem of how to improve the efficiency of computer hardware production testing.

[0004] To achieve the above objectives, this application proposes an automated testing method for computer hardware, the method comprising: Obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding basic device data based on the device identification information and hardware configuration description information; Read the test process configuration data corresponding to the basic data of the device, and parse the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; Based on the process organization relationship and the execution association information, the multiple test units to be executed are scheduled and controlled to call the corresponding external test programs to perform test processing and obtain the process output information corresponding to each test unit to be executed. Based on the process output information corresponding to each of the test units to be executed, the execution status of each of the test units to be executed is determined, and test status data associated with the basic data of the device is generated; Based on the test status data, test progress is stored and test results are displayed, and test record data is generated based on the test status data and the process output information.

[0005] In one embodiment, the step of obtaining device identification information and hardware configuration description information of the target computer, and generating corresponding device basic data based on the device identification information and the hardware configuration description information, includes: Obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding basic device data based on the device identification information and hardware configuration description information; Based on the system management interface, the processor information, memory information, graphics processing information, storage medium information, and network adaptation information of the target computer are queried to obtain the hardware configuration description information; The device identification information and the hardware configuration description information are structured, organized, and encapsulated to generate corresponding basic device data.

[0006] In one embodiment, the step of reading test process configuration data corresponding to the device basic data, and parsing the test process configuration data to obtain the process organization relationship and execution association information of multiple test units to be executed, includes: Read the preset configuration file and combine it with the device's basic data to determine the test process configuration data that matches the target computer. The test process configuration data is used to characterize multiple test nodes and their configuration content in the test process. The test process configuration data is parsed to extract the process hierarchy, sequence, and group affiliation of each test node, thereby obtaining the process organization relationship of multiple test units to be executed. Based on the test process configuration data, the calling object, execution conditions and result judgment criteria corresponding to each of the test units to be executed are determined, and the execution association information of multiple test units to be executed is obtained.

[0007] In one embodiment, the step of scheduling and controlling the plurality of test units to be executed based on the process organization relationship and the execution association information to call the corresponding external test program to execute test processing, and obtaining the process output information corresponding to each of the test units to be executed, includes: Based on the process organization relationship, the execution order of the multiple test units to be executed and the test unit to be scheduled are determined, and the corresponding scheduling control instructions are constructed in combination with the execution association information; Based on the scheduling control instruction, the external test program corresponding to the currently scheduled test unit is invoked, and the external test program is controlled to perform test processing on the currently scheduled test unit. During the execution of the test process by the external test program, the running output and abnormal output fed back by the external test program are collected to obtain the process output information corresponding to each test unit to be executed.

[0008] In one embodiment, the step of determining the execution status of each of the test units to be executed based on the process output information corresponding to each of the test units to be executed, and generating test status data associated with the device basic data, includes: The process output information corresponding to each test unit to be executed is parsed to extract the status identification information, exception prompt information and execution completion information related to the test execution results; Based on the status identification information, the exception prompt information, and the execution completion identification information, the execution results of each of the test units to be executed are identified, and the execution status corresponding to each of the test units to be executed is determined. The execution status of each of the test units to be executed is associated with the basic data of the device, and test status data is generated by combining the identification information of each of the test units to be executed.

[0009] In one embodiment, the steps of performing test progress storage processing and test result display processing based on the test status data, and generating test record data based on the test status data and the process output information, include: Based on the test status data, the status change content corresponding to each test unit to be executed is associated and organized, and the associated and organized status content is written into a preset status storage carrier to complete the test progress storage process. Based on the test status data, the result identifier and stage status corresponding to each of the test units to be executed are determined, and the result identifier and stage status corresponding to each of the test units to be executed are output to the preset display interface to complete the test result display process. The test status data and the process output information are summarized and correlated to generate test record data corresponding to the basic equipment data.

[0010] Furthermore, to achieve the above objectives, this application also proposes an automated computer hardware testing device, which includes: The basic data module is used to obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding device basic data based on the device identification information and hardware configuration description information; The data parsing module is used to read the test process configuration data corresponding to the basic data of the device, and to parse the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; The scheduling and control module is used to schedule and control the multiple test units to be executed based on the process organization relationship and the execution association information, so as to call the corresponding external test program to execute the test processing and obtain the process output information corresponding to each test unit to be executed. The status determination module is used to determine the execution status of each of the test units to be executed based on the process output information corresponding to each of the test units to be executed, and to generate test status data associated with the basic data of the device. The test record module is used to store test progress and display test results based on the test status data, and to generate test record data based on the test status data and the process output information.

[0011] In addition, to achieve the above objectives, this application also proposes an automated computer hardware testing device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the automated computer hardware testing method described above.

[0012] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the computer hardware automated testing method described above.

[0013] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the computer hardware automated testing method described above.

[0014] This application obtains the device identification information and hardware configuration description information of the target computer, and generates corresponding basic device data based on the device identification information and hardware configuration description information; reads the test process configuration data corresponding to the basic device data, and parses the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; schedules and controls the multiple test units to be executed based on the process organization relationship and execution association information to call the corresponding external test program to execute the test processing, and obtains the process output information corresponding to each test unit to be executed; determines the execution status of each test unit to be executed based on the process output information corresponding to each test unit to be executed, and generates test status data associated with the basic device data; performs test progress storage processing and test result display processing based on the test status data, and generates test record data based on the test status data and process output information. This application obtains the device identification information and hardware configuration description information of the target computer and generates basic device data, enabling the basic information of the tested object to be uniformly organized. Then, based on the basic device data, it reads the test process configuration data and parses it to obtain the process organization relationship and execution association information of multiple test units to be executed, allowing the test content and execution relationship to be predetermined. Furthermore, by scheduling and controlling multiple test units to be executed, it calls the corresponding external test programs to perform test processing, and combines the process output information to determine the execution status and generate test status data. Simultaneously, it completes test progress storage, test result display, and test record generation, thus forming a continuous processing chain for test execution, status management, and result recording. This reduces the time consumption caused by information dispersion, process disconnection, and repetitive processing during the testing process, thereby improving the efficiency of computer hardware production testing. Attached Figure Description

[0015] Figure 1 This is a flowchart illustrating the first embodiment of the computer hardware automated testing method of this application; Figure 2 This is a schematic diagram of a sub-process in the second embodiment of the computer hardware automated testing method of this application; Figure 3 This is a schematic diagram of a sub-process in the third embodiment of the computer hardware automated testing method of this application; Figure 4 This is a schematic diagram of the module structure of the computer hardware automated testing device according to an embodiment of this application; Figure 5 This is a schematic diagram of the device structure of the hardware operating environment involved in the computer hardware automated testing method in this application embodiment.

[0016] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0017] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of this application.

[0018] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0019] It should be noted that during the manufacturing process of computer hardware products, the processor, memory, graphics processing unit, storage medium, motherboard, network adapter, and firmware information of the device under test are typically tested before leaving the factory. This testing involves calling appropriate test programs based on different product models, production stations, and testing tasks. In existing technologies, such testing often relies on manual intervention with multiple independent programs. Testers typically need to manually organize device information, select test items, call test programs, and judge test results, resulting in a low level of automation. Furthermore, existing testing methods often lack a unified process organization and scheduling mechanism between different test programs, and there is a lack of effective correlation between test status, process output, and test records. This easily leads to problems such as disjointed test processes, fragmented test status management, and incomplete test records. Especially in cases of test interruption, abnormal shutdown, or station switching, existing solutions struggle to continuously store and uniformly manage test progress, resulting in poor efficiency in computer hardware production testing. Therefore, improving the efficiency of computer hardware production testing is a pressing issue that needs to be addressed.

[0020] The main solution of this application is as follows: First, obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding basic device data based on this information. Second, read the test process configuration data corresponding to the basic device data, and parse the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data. Third, schedule and control the multiple test units to be executed based on the process organization relationship and execution association information to call the corresponding external test program to execute the test processing, and obtain the process output information corresponding to each test unit to be executed. Fourth, determine the execution status of each test unit to be executed based on the process output information corresponding to each test unit to be executed, and generate test status data associated with the basic device data. Fifth, perform test progress storage processing and test result display processing based on the test status data, and generate test record data based on the test status data and process output information.

[0021] This application obtains the device identification information and hardware configuration description information of the target computer and generates basic device data, enabling the basic information of the tested object to be uniformly organized. Then, based on the basic device data, it reads the test process configuration data and parses it to obtain the process organization relationship and execution association information of multiple test units to be executed, allowing the test content and execution relationship to be predetermined. Furthermore, by scheduling and controlling multiple test units to be executed, it calls the corresponding external test programs to perform test processing, and combines the process output information to determine the execution status and generate test status data. Simultaneously, it completes test progress storage, test result display, and test record generation, thus forming a continuous processing chain for test execution, status management, and result recording. This reduces the time consumption caused by information dispersion, process disconnection, and repetitive processing during the testing process, thereby improving the efficiency of computer hardware production testing.

[0022] It should be noted that the executing entity of the method in this embodiment can be a computing service device with data processing, network communication, and program execution functions, or it can be the aforementioned automated computer hardware testing device with the same or similar functions. This embodiment and the following embodiments will be described using an automated computer hardware testing device as an example.

[0023] Based on this, a first embodiment of the computer hardware automated testing method of this application is proposed. Please refer to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the computer hardware automated testing method of this application.

[0024] In this embodiment, the method includes the following steps: S1: Obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding basic device data based on the device identification information and hardware configuration description information; S2: Read the test process configuration data corresponding to the basic data of the device, and parse the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; It should be noted that: the target computer refers to the computer device under test that is currently entering the automated testing process and serving as the test object; device identification information refers to information used to characterize the identity attributes or device affiliation of the target computer; hardware configuration description information refers to information used to characterize the hardware composition and configuration status of the target computer; device basic data refers to structured data formed by organizing and associating the device identification information and the hardware configuration description information; test process configuration data refers to configuration data used to describe the test process content, test unit organization method, and call configuration relationship; test unit to be executed refers to the test item that can be scheduled and executed, obtained by parsing the test process configuration data; process organization relationship refers to the hierarchical relationship, sequential relationship, and grouping relationship between multiple test units to be executed; execution association information refers to the calling object, execution conditions, and result judgment criteria corresponding to each test unit to be executed.

[0025] Specifically, firstly, after the target computer enters the testing process, the system performs basic information collection processing to obtain the device identification information and hardware configuration description information corresponding to the target computer. The device identification information is used to determine the identity of the currently tested object, and the hardware configuration description information is used to characterize the hardware composition of the currently tested object. Subsequently, the system collects, organizes, and correlates the acquired device identification information and hardware configuration description information, transforming the originally scattered device identification information and hardware configuration content into a unified data representation, thereby generating the corresponding basic device data. Through this processing, the target computer can participate in the process flow in the subsequent testing process as a structured data object, rather than participating in subsequent operations as discrete information.

[0026] Furthermore, after generating the basic device data, the system reads the test process configuration data corresponding to the basic device data and parses the test process configuration data. On one hand, it extracts the arrangement, hierarchy, and sequence of each test item in the overall test process from the test process configuration data to obtain the process organization relationship of multiple test units to be executed. On the other hand, it extracts the call content, execution constraints, and result identification rules corresponding to each test unit to be executed from the test process configuration data to obtain the execution association information of multiple test units to be executed. Thus, the test process configuration data is converted into process structure information and execution rule information that can be directly used by subsequent scheduling and control, providing a foundation for the orderly execution of multiple test units to be executed.

[0027] This step first acquires the target computer's device identification information and hardware configuration description information, and generates corresponding basic device data, enabling the basic information of the object under test to be uniformly organized and structurally expressed. Then, it reads the test process configuration data corresponding to the basic device data and parses it to obtain the process organization relationship and execution association information of multiple test units to be executed, ensuring that the test content, execution order, and calling relationships in the test process are clearly established before execution. In this way, subsequent test processing can revolve around the unified basic device data and the parsed process configuration, reducing the processing burden caused by scattered device information, unclear process relationships, and ad-hoc determination of execution rules during testing. This provides support for improving the execution efficiency and process orderliness of computer hardware production testing.

[0028] S3: Based on the process organization relationship and the execution association information, schedule and control the multiple test units to be executed, so as to call the corresponding external test program to execute the test processing, and obtain the process output information corresponding to each test unit to be executed; It should be noted that scheduling control refers to the process of organizing and controlling the execution order, invocation timing, and execution process of multiple test units to be executed based on the process organization relationship and the execution association information; external test program refers to the program object corresponding to each test unit to be executed and used to execute specific test tasks; test processing refers to the process of performing corresponding detection or verification on the target computer by invoking the external test program; process output information refers to the running feedback information, output information, or exception information generated by the external test program during the execution of test processing.

[0029] Specifically, firstly, after obtaining the process organization relationship and execution association information of multiple test units to be executed, the system determines the execution path, sequence, and group to which the multiple test units to be executed belong in the overall test process based on the process organization relationship, and further determines the target test unit that should be scheduled at the moment based on the execution association information. Subsequently, the system generates corresponding scheduling control content around the currently scheduled test unit, so that different test units are no longer in a scattered and isolated execution state, but are incorporated into a unified process control logic, thereby ensuring that each test unit can enter the execution phase according to the predetermined process relationship.

[0030] Furthermore, after identifying the test unit to be executed, the system invokes the external test program corresponding to that test unit, enabling the external test program to perform corresponding test processing on the target computer. During the test processing, the system continuously acquires the runtime information, processing information, and exception information fed back by the external test program, and maps this feedback content to the corresponding test unit to be executed, forming the process output information corresponding to each test unit. In other words, this step not only realizes the invocation of the external test program, but also realizes the synchronous perception and information acquisition of the test execution process, thereby providing a directly usable data foundation for subsequent execution status determination.

[0031] This step, based on process organization and execution correlation information, schedules and controls multiple test units to be executed, ensuring a unified organization of the execution order, invocation timing, and execution relationships of each test unit. It also calls corresponding external test programs to execute test processing, enabling each test task to proceed in an orderly manner within the established process. Simultaneously, it acquires the process output information corresponding to each test unit during test processing, ensuring timely collection and response to feedback during test execution. Therefore, this step integrates test unit organization, program invocation, and process information acquisition, reducing the processing burden caused by scattered execution of test units, chaotic connections, and difficulty in controlling the execution process. This ultimately improves the execution efficiency and process controllability of computer hardware production testing.

[0032] S4: Based on the process output information corresponding to each of the test units to be executed, determine the execution status of each of the test units to be executed, and generate test status data associated with the basic data of the device; S5: Based on the test status data, perform test progress storage processing and test result display processing, and generate test record data based on the test status data and the process output information.

[0033] It should be noted that: execution status refers to the status result of each test unit after test processing, used to characterize whether the corresponding test unit has completed the corresponding test processing; test status data refers to the data formed by associating the execution status of each test unit with the basic data of the device; test progress storage processing refers to the process of writing and saving the status change content corresponding to each test unit during the test; test result display processing refers to the process of outputting the execution result and status information corresponding to each test unit to a preset display interface; test record data refers to the record data formed by summarizing and associating the test status data with the process output information.

[0034] Specifically, firstly, after each test unit completes its corresponding test processing and obtains process output information, the system parses the process output information corresponding to each test unit to identify the output content related to the test results, abnormal content, and execution completion status, and determines the execution status of each test unit accordingly. Subsequently, the system associates and organizes the execution status of each test unit with the device's basic data, so that the status results of each test unit are no longer isolated results, but rather belong to the status data of the corresponding target computer, thereby generating test status data associated with the device's basic data.

[0035] Furthermore, after generating the test status data, the system performs subsequent processing based on this data. On one hand, it writes the status changes of each test unit to be executed during the test into a preset storage medium to continuously save the test progress; on the other hand, it outputs the execution results and status information of each test unit to a preset display interface to form a result display of the test process. Simultaneously, the system also summarizes and correlates the test status data with the process output information to generate corresponding test record data, thereby enabling the status changes, execution results, and output content during the test process to form a unified record.

[0036] This step determines the execution status of each test unit based on its corresponding process output information and generates test status data associated with the device's basic data. This ensures that the test results form a unified state representation around the target computer. Furthermore, it processes test progress storage and test result display based on the test status data, and combines the test status data with process output information to generate test record data. This allows for continuous saving, intuitive presentation, and unified recording of state changes, results, and output information during the test process. Thus, this step links status determination, progress storage, result display, and record generation, reducing the processing burden caused by scattered test result management, fragmented process information, and repetitive record organization. This improves the execution efficiency and process management capabilities of computer hardware production testing.

[0037] This embodiment acquires the device identification information and hardware configuration description information of the target computer, and generates corresponding basic device data based on the device identification information and hardware configuration description information; reads the test process configuration data corresponding to the basic device data, and parses the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; schedules and controls the multiple test units to be executed based on the process organization relationship and execution association information to call the corresponding external test program to execute the test processing, and obtains the process output information corresponding to each test unit to be executed; determines the execution status of each test unit to be executed based on the process output information corresponding to each test unit to be executed, and generates test status data associated with the basic device data; performs test progress storage processing and test result display processing based on the test status data, and generates test record data based on the test status data and process output information. This embodiment acquires the device identification information and hardware configuration description information of the target computer and generates basic device data, enabling the basic information of the tested object to be uniformly organized. Then, based on the basic device data, it reads the test process configuration data and parses it to obtain the process organization relationship and execution association information of multiple test units to be executed, allowing the test content and execution relationship to be predetermined. Furthermore, by scheduling and controlling multiple test units to be executed, it calls the corresponding external test programs to perform test processing, and combines the process output information to determine the execution status and generate test status data. Simultaneously, it completes test progress storage, test result display, and test record generation, thus forming a continuous processing chain for test execution, status management, and result recording. This reduces the time consumption caused by information dispersion, process disconnection, and repetitive processing during the testing process, thereby improving the efficiency of computer hardware production testing.

[0038] Based on the first embodiment described above, a second embodiment of the computer hardware automated testing method of this application is proposed. Please refer to... Figure 2 , Figure 2 This is a schematic diagram of a sub-process in the second embodiment of the computer hardware automated testing method of this application.

[0039] like Figure 2 As shown, in this embodiment, step S1 includes: S11: Obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding device basic data based on the device identification information and hardware configuration description information; S12: Based on the system management interface, query the processor information, memory information, graphics processing information, storage medium information, and network adaptation information of the target computer to obtain the hardware configuration description information; S13: The device identification information and the hardware configuration description information are structured, organized, and encapsulated to generate corresponding device basic data.

[0040] It should be noted that: the system management interface refers to the interface used to access the target computer's underlying system management information and perform hardware information queries; processor information refers to information used to characterize the target computer's processor configuration; memory information refers to information used to characterize the target computer's memory configuration; graphics processing information refers to information used to characterize the target computer's graphics processing unit configuration; storage media information refers to information used to characterize the target computer's hard disk or solid-state storage unit configuration; network adaptation information refers to information used to characterize the target computer's network communication unit configuration; structured organization refers to the processing of classifying, collecting, and standardizing the fields of the acquired information according to a preset data organization method; and associated encapsulation refers to the processing of associating corresponding device identification information and hardware configuration description information to form a unified data object.

[0041] Specifically, firstly, after the target computer enters the testing process, the system performs basic information collection and processing around the target computer. On one hand, the system acquires the target computer's device identification information to determine the identity of the currently tested object; on the other hand, it queries the target computer's processor information, memory information, graphics processing information, storage media information, and network adaptation information through the system management interface to obtain hardware configuration description information. In this way, basic content related to the hardware components can be directly extracted from the target computer's current operating environment, ensuring that the acquired information covers the target computer's main hardware configuration.

[0042] Furthermore, after completing the information query, the system further processes the device identification information and hardware configuration description information in a unified manner. Specifically, it first categorizes and organizes various types of information according to a preset data organization method, so that field content from different sources and categories forms data content with a consistent expression form; then, it associates and encapsulates the device identification information and hardware configuration description information according to the correspondence with the same target computer, forming a unified data result that can characterize the identity attributes and hardware composition of the target computer, thereby generating the corresponding basic device data. In this way, subsequent testing processes no longer call upon scattered raw information, but rather structured data objects that have already been collected and associated.

[0043] This step first acquires the target computer's device identification information and then queries the target computer's processor, memory, graphics processing, storage media, and network adaptation information based on the system management interface to obtain hardware configuration description information. This allows for the centralized acquisition of the target computer's identity information and main hardware configuration information. Next, the device identification information and hardware configuration description information are structured, organized, and encapsulated to generate corresponding basic device data, transforming scattered device information into a unified data representation. Consequently, subsequent testing can be directly based on this organized basic device data, reducing the processing burden caused by scattered use of device information, redundant organization, and unclear correspondences. This provides support for improving the execution efficiency and information organization capabilities of computer hardware production testing.

[0044] In this embodiment, step S2 includes: S21: Read the preset configuration file and combine it with the device basic data to determine the test process configuration data that matches the target computer, wherein the test process configuration data is used to characterize multiple test nodes and their configuration content in the test process; S22: Parse the test process configuration data, extract the process level, sequence and grouping relationship corresponding to each test node, and obtain the process organization relationship of multiple test units to be executed; S23: Based on the test process configuration data, determine the calling object, execution conditions and result judgment criteria corresponding to each of the test units to be executed, and obtain the execution association information of multiple test units to be executed.

[0045] It should be noted that the preset configuration file refers to a configuration file that is pre-established and used to describe the test process content; the test node refers to a configuration unit used to represent a specific test step in the test process; the configuration content refers to the process description information and execution description information corresponding to each test node; the calling object refers to the program or script object corresponding to the test unit to be executed and used to be called by the system to execute the test task; the execution condition refers to the limiting content that the test unit to be executed must meet when it enters execution; and the result judgment basis refers to the basis used to identify and judge the execution result of the test unit to be executed.

[0046] Specifically, first, the system reads a preset configuration file and matches the test process content in the configuration file with the device's basic data to determine the test process configuration data suitable for the current target computer. This matching is not simply reading all configuration content, but rather combining the target computer's device attributes and hardware configuration to determine the test nodes and their corresponding configuration content applicable to the current test object from the configuration file, ensuring that subsequent test processes revolve around the current target computer. Through this process, pre-set process configurations for different devices or test scenarios can be converted into actual test process data corresponding to the current target computer.

[0047] Furthermore, after obtaining the test process configuration data, the system further parses and processes it. On one hand, it extracts the process hierarchy, sequence, and grouping relationships between each test node from the test process configuration data, thereby transforming the configuration-level process description into a process organization relationship between multiple test units to be executed. On the other hand, it continues to determine the calling object, execution conditions, and result judgment criteria corresponding to each test unit to be executed based on the test process configuration data, thereby obtaining the execution association information of multiple test units to be executed. In other words, this step not only completes the reading of the test process but also further decomposes the test process configuration data into the process structure information and execution rule information required for subsequent scheduling and execution, giving the test units to be executed a basis for orderly scheduling and judgment.

[0048] This step involves reading a preset configuration file and combining it with the device's basic data to determine the test process configuration data that matches the target computer, ensuring that the object under test is matched with the appropriate test process content. Furthermore, by parsing the test process configuration data, the process organization relationships and execution association information of multiple test units to be executed are obtained. This allows the hierarchical relationships, sequential relationships, calling relationships, and judgment criteria between test nodes to be clearly established before execution. As a result, subsequent test processing can be directly based on the matched and parsed process configuration, reducing the processing burden caused by ad-hoc selection of test processes, ad-hoc determination of execution relationships, and scattered setting of result judgment rules. This, in turn, helps improve the efficiency of process organization and the orderly execution of computer hardware production testing.

[0049] This embodiment acquires the device identification information and hardware configuration description information of the target computer, and generates corresponding basic device data based on the device identification information and hardware configuration description information; reads the test process configuration data corresponding to the basic device data, and parses the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; schedules and controls the multiple test units to be executed based on the process organization relationship and execution association information to call the corresponding external test program to execute the test processing, and obtains the process output information corresponding to each test unit to be executed; determines the execution status of each test unit to be executed based on the process output information corresponding to each test unit to be executed, and generates test status data associated with the basic device data; performs test progress storage processing and test result display processing based on the test status data, and generates test record data based on the test status data and process output information. This embodiment acquires the device identification information and hardware configuration description information of the target computer and generates basic device data, enabling the basic information of the tested object to be uniformly organized. Then, based on the basic device data, it reads the test process configuration data and parses it to obtain the process organization relationship and execution association information of multiple test units to be executed, allowing the test content and execution relationship to be predetermined. Furthermore, by scheduling and controlling multiple test units to be executed, it calls the corresponding external test programs to perform test processing, and combines the process output information to determine the execution status and generate test status data. Simultaneously, it completes test progress storage, test result display, and test record generation, thus forming a continuous processing chain for test execution, status management, and result recording. This reduces the time consumption caused by information dispersion, process disconnection, and repetitive processing during the testing process, thereby improving the efficiency of computer hardware production testing.

[0050] Based on the second embodiment described above, a third embodiment of the computer hardware automated testing method of this application is proposed. Please refer to... Figure 3 , Figure 3 This is a schematic diagram of a sub-process in the third embodiment of the computer hardware automated testing method of this application.

[0051] In this embodiment, step S3 includes: S31: Based on the process organization relationship, determine the execution order of the multiple test units to be executed and the test unit to be scheduled, and construct the corresponding scheduling control instruction in combination with the execution association information; S32: Based on the scheduling control instruction, call the external test program corresponding to the currently scheduled test unit, and control the external test program to perform test processing on the currently scheduled test unit; S33: During the execution of the test process by the external test program, the running output and abnormal output fed back by the external test program are collected to obtain the process output information corresponding to each test unit to be executed.

[0052] It should be noted that the execution order refers to the sequential execution order of multiple test units in the test process; the currently scheduled test unit refers to the test unit currently selected to enter the execution phase according to the execution order; the scheduling control instruction refers to the instruction content generated based on the process organization relationship and the execution association information, used to control the execution of the currently scheduled test unit; the operation output refers to the normal operation information fed back by the external test program during the execution of the test processing; the abnormal output refers to the abnormal information or error information fed back by the external test program during the execution of the test processing.

[0053] Specifically, firstly, based on the process organization relationship, the system identifies the arrangement relationship of multiple test units to be executed within the overall test process, determines the execution order of each test unit, and identifies the currently scheduled test unit that should enter the execution phase. Based on this, the system further combines execution association information to determine the calling object, execution conditions, and result identification related content corresponding to the currently scheduled test unit, and constructs corresponding scheduling control instructions accordingly. Through this process, the system combines the sequential relationship at the process level with the association content at the execution level, providing the currently scheduled test unit with the control basis to enter the actual execution phase.

[0054] Furthermore, after generating the scheduling control instruction, the system, based on the instruction, calls the external test program corresponding to the currently scheduled test unit and controls the external test program to perform test processing on the unit. During the test processing, the system continuously collects the runtime output and exception output from the external test program and establishes a correspondence between the collected output and the corresponding test unit to be executed, thus forming process output information for each unit. This not only achieves the actual execution of the current test unit but also simultaneously acquires and collects execution process information, providing a direct data foundation for subsequent execution status determination.

[0055] This step first determines the execution order of multiple test units and the currently scheduled test units based on the process organization relationship, and constructs corresponding scheduling control instructions based on execution association information, so that the execution object and execution time of the test units can be clearly defined. Then, based on the scheduling control instructions, the corresponding external test program is called to execute the test processing, and the running output and exception output are collected during the execution process to obtain the process output information corresponding to each test unit to be executed, so that test execution and process information acquisition can be carried out synchronously. Thus, this step connects the determination of test order, program call control and process output acquisition, reducing the processing burden caused by independent execution of test units, unclear call connections and difficulty in timely acquisition of execution feedback, thereby helping to improve the execution efficiency and process controllability of computer hardware production testing.

[0056] Based on the second embodiment described above, in this embodiment, step S4 includes: S41: Parse the process output information corresponding to each test unit to be executed, and extract the status identification information, exception prompt information and execution completion identification information related to the test execution result; S42: Based on the status identification information, the exception prompt information, and the execution completion identification information, identify the execution results of each of the test units to be executed, and determine the execution status corresponding to each of the test units to be executed; S43: Associate the execution status of each of the test units to be executed with the basic data of the device, and generate test status data by combining the identification information of each of the test units to be executed.

[0057] It should be noted that: status identification information refers to the output information used to characterize the test result status of the test unit to be executed; exception prompt information refers to the prompt information used to characterize the exception situation that occurred during the execution of the test unit to be executed; execution completion identification information refers to the identification information used to characterize whether the test unit to be executed has completed the current test processing; execution result refers to the test processing result identified based on the process output information; and identification information refers to the correspondence information used to distinguish the test units to be executed.

[0058] Specifically, firstly, the system parses and processes the process output information corresponding to each test unit to be executed, extracting different categories of information related to the test execution results. These include status identifiers reflecting the test status, exception prompts reflecting abnormal situations, and execution completion identifiers indicating whether the test processing has ended. In other words, the system does not directly use the raw output content, but first breaks down and extracts the status-related content from the process output information, transforming it into status-based information that can be used for result identification. Through this processing, the runtime content fed back by external test programs can be further organized into the basis for subsequent status determination.

[0059] Furthermore, after extracting the aforementioned information, the system further identifies the execution results of each test unit based on status identifiers, exception prompts, and execution completion identifiers, and determines the execution status of each test unit accordingly. Subsequently, the system associates the execution status of each test unit with the device's basic data and organizes it in conjunction with the identifier information corresponding to each test unit. This ensures that the test status reflects the execution status of a specific test unit and is attributed to the corresponding target computer, thereby generating test status data. Thus, the result information originally scattered across different test units is transformed into unified status data oriented towards the target computer.

[0060] This step parses the process output information corresponding to each test unit to be executed, extracting status identification information, exception prompts, and execution completion identification information, enabling the status-related content in the process output to be categorized and identified. Based on this information, the execution result and execution status of each test unit to be executed are determined, and the execution status is associated with the device's basic data. Combined with the identification information corresponding to each test unit, test status data is generated, transforming the scattered output content of the test results into unified status data corresponding to the target computer. Therefore, this step reduces the processing burden caused by directly relying on the original output content for manual identification and scattered organization of test results, which is beneficial to improving the efficiency of status determination and the orderly management of results in computer hardware production testing.

[0061] In this embodiment, step S5 includes: S51: Based on the test status data, the status change content corresponding to each of the test units to be executed is associated and organized, and the associated and organized status content is written into a preset status storage carrier to complete the test progress storage process. S52: Based on the test status data, determine the result identifier and stage status corresponding to each of the test units to be executed, and output the result identifier and stage status corresponding to each of the test units to be executed to the preset display interface to complete the test result display processing; S53: Summarize and associate the test status data with the process output information to generate test record data corresponding to the basic equipment data.

[0062] It should be noted that: status change content refers to the status change information of each test unit to be executed during the test process; preset status storage carrier refers to the storage object used to write and save the test progress-related status content; result identifier refers to the identifier content used to characterize the test result category of each test unit to be executed; stage status refers to the status content of each test unit to be executed in the current stage of the test process; preset display interface refers to the interface object used to output and display test result information; summary association refers to the process of aggregating data content from different sources and establishing corresponding relationships.

[0063] Specifically, firstly, based on test status data, the system organizes and categorizes the status changes of each test unit to be executed, forming a set of corresponding status content. Then, the system writes the organized status content into a preset status storage medium to continuously save the execution progress of the current test process. Through this process, the status changes of each test unit to be executed during the test process are no longer limited to instantaneous results, but can reflect the current test progress in the form of saved status content. Simultaneously, the system further determines the result identifier and stage status corresponding to each test unit to be executed based on the test status data, and outputs the result identifier and stage status to a preset display interface, allowing the execution results and current progress during the test to be presented in a graphical way.

[0064] Furthermore, after completing progress storage and result display, the system further summarizes and correlates the test status data and process output information. Specifically, the system integrates the status results and stage information reflected in the test status data with the operational feedback content reflected in the process output information, so that the status changes and execution output of the same target computer during the test process can form a unified data representation result, thereby generating test record data corresponding to the basic equipment data. Thus, the state saving, result display, and record generation during the test process are linked into a continuous data processing process, enabling the execution information of the test process to form a complete record around the same equipment object.

[0065] This step, based on test status data, associates and organizes the status changes corresponding to each test unit to be executed and writes them into a preset status storage medium, ensuring continuous preservation of test progress. Simultaneously, based on the test status data, it determines the result identifier and stage status corresponding to each test unit to be executed and outputs them to a preset display interface, allowing for a clear presentation of test results and current progress. Furthermore, by summarizing and associating test status data with process output information, it generates test record data corresponding to the equipment's basic data, ensuring a unified record of status and output content during the test process. Therefore, this step integrates test progress preservation, test result display, and test record generation, reducing the processing burden caused by scattered storage of status information, independent display of result information, and subsequent repetitive organization of record content during the test process. This improves the efficiency of process management and information organization in computer hardware production testing.

[0066] This embodiment acquires the device identification information and hardware configuration description information of the target computer, and generates corresponding basic device data based on the device identification information and hardware configuration description information; reads the test process configuration data corresponding to the basic device data, and parses the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; schedules and controls the multiple test units to be executed based on the process organization relationship and execution association information to call the corresponding external test program to execute the test processing, and obtains the process output information corresponding to each test unit to be executed; determines the execution status of each test unit to be executed based on the process output information corresponding to each test unit to be executed, and generates test status data associated with the basic device data; performs test progress storage processing and test result display processing based on the test status data, and generates test record data based on the test status data and process output information. This embodiment acquires the device identification information and hardware configuration description information of the target computer and generates basic device data, enabling the basic information of the tested object to be uniformly organized. Then, based on the basic device data, it reads the test process configuration data and parses it to obtain the process organization relationship and execution association information of multiple test units to be executed, allowing the test content and execution relationship to be predetermined. Furthermore, by scheduling and controlling multiple test units to be executed, it calls the corresponding external test programs to perform test processing, and combines the process output information to determine the execution status and generate test status data. Simultaneously, it completes test progress storage, test result display, and test record generation, thus forming a continuous processing chain for test execution, status management, and result recording. This reduces the time consumption caused by information dispersion, process disconnection, and repetitive processing during the testing process, thereby improving the efficiency of computer hardware production testing.

[0067] In one embodiment, the automated computer hardware testing method includes the following steps: Step 1: After the system starts, the hardware information acquisition module runs automatically, comprehensively collects the hardware configuration information of the computer under test through the WMI interface, and saves the information as a structured document; Step 2: The test configuration and process management module reads the preset XML test configuration file, parses out the test station, test item and corresponding script path, and displays it in a tree structure in the graphical user interface module; Step 3: The user triggers the test start command through the graphical interface. The script execution and control engine module schedules the first test item sequentially; Step 4: For the currently pending test item, the engine module calls the unified logging module to record the start information and marks the test item's status as "Running" on the graphical interface. Simultaneously, the test status persistence management module updates this status in the status XML file. Step 5: The engine module creates an independent process, asynchronously executes the script file corresponding to the test item, and captures the script output in real time. After the script finishes execution, the engine module analyzes the results based on its exit code or output content; Step 6: If the script executes successfully (e.g., exit code 0), the engine module determines the test item as "passed"; otherwise, it is determined as "failed". The determination result is immediately notified to the test state persistence management module and the graphical user interface module. The state management module updates the state XML file, and the graphical user interface module updates the tree node display (e.g., green marks pass, red marks failure). Step 7: The engine module checks the station configuration of the currently failed item. If the configuration requires "Stop if there is a failure at this station", the engine suspends the scheduling of subsequent test items for that station and waits for processing; otherwise, it continues to schedule the next test item for this station and returns to step 4. Step 8: Repeat steps 4-7 until all station test items are completed in sequence, or the process is manually stopped; Step 9: After all tests are completed, the system can automatically generate a test report, summarizing hardware information, test results, timestamps, and log summaries.

[0068] In this embodiment, the entire process from hardware information acquisition to multi-item testing is automated, eliminating the need for manual intervention in the execution and judgment of individual test steps, significantly improving testing speed. Automatic test result evaluation by the program eliminates subjective errors and oversights from human judgment, ensuring consistent standards are applied. All hardware information, test steps, results, detailed logs, and timestamps are recorded completely and in a structured manner, providing a complete data chain for quality analysis and issue tracing. The test process and the addition of different external programs are defined through external XML configuration files, allowing for rapid adjustments to test content and order based on different product lines without modifying the main program code. Through persistent test state and file backup mechanisms, the system can handle unexpected interruptions, supporting breakpoint resumption and reducing the risk of lost test progress due to anomalies. Testers only need to perform initial startup and final result confirmation; a single person can monitor multiple devices, greatly saving manpower.

[0069] This application also provides an automated computer hardware testing device. Please refer to... Figure 4 , Figure 4 This is a schematic diagram of the module structure of an automated computer hardware testing device according to an embodiment of this application. The automated computer hardware testing device includes: The basic data module 401 is used to obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding device basic data based on the device identification information and the hardware configuration description information; The data parsing module 402 is used to read the test process configuration data corresponding to the basic data of the device, and to parse the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; The scheduling control module 403 is used to schedule and control the multiple test units to be executed based on the process organization relationship and the execution association information, so as to call the corresponding external test program to execute the test processing and obtain the process output information corresponding to each test unit to be executed. The status determination module 404 is used to determine the execution status of each of the test units to be executed based on the process output information corresponding to each of the test units to be executed, and to generate test status data associated with the basic data of the device. The test record module 405 is used to perform test progress storage and test result display processing based on the test status data, and to generate test record data based on the test status data and the process output information.

[0070] The automated computer hardware testing apparatus provided in this application, employing the automated computer hardware testing method described in the above embodiments, can solve the technical problem of how to improve the efficiency of computer hardware production testing. Compared with the prior art, the beneficial effects of the automated computer hardware testing apparatus provided in this application are the same as those of the automated computer hardware testing method described in the above embodiments, and other technical features in the automated computer hardware testing apparatus are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0071] This application provides an automated computer hardware testing device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the automated computer hardware testing method in the above embodiments.

[0072] The following is for reference. Figure 5 , Figure 5 This is a schematic diagram of the hardware operating environment involved in the computer hardware automated testing method in the embodiments of this application, showing a schematic diagram of the structure of a computer hardware automated testing device suitable for implementing the embodiments of this application. Figure 5 The computer hardware automated testing equipment shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0073] like Figure 5As shown, the computer hardware automated testing equipment may include a processing unit 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the computer hardware automated testing equipment. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to the I / O interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 1003 including, for example, magnetic tape, hard disk, etc.; and communication devices 1009. Communication device 1009 allows the computer hardware automation testing equipment to communicate wirelessly or wiredly with other devices to exchange data. Although the figure shows computer hardware automation testing equipment with various systems, it should be understood that it is not required to implement or possess all of the systems shown. More or fewer systems may be implemented alternatively.

[0074] In particular, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. When the computer program is executed by the processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0075] The automated computer hardware testing equipment provided in this application, employing the automated computer hardware testing method described in the above embodiments, can solve the technical problem of how to improve the efficiency of computer hardware production testing. Compared with the prior art, the beneficial effects of the automated computer hardware testing equipment provided in this application are the same as those of the automated computer hardware testing method provided in the above embodiments, and other technical features of this automated computer hardware testing equipment are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0076] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0077] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0078] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the computer hardware automated testing method in the above embodiments.

[0079] The aforementioned computer-readable storage medium carries one or more programs. When these programs are executed by an automated computer hardware testing device, the automated computer hardware testing device performs the following actions: acquires device identification information and hardware configuration description information of the target computer, and generates corresponding basic device data based on the device identification information and hardware configuration description information; reads test process configuration data corresponding to the basic device data, and parses the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; schedules and controls the multiple test units to be executed based on the process organization relationship and execution association information to call corresponding external test programs to perform test processing, and acquires the process output information corresponding to each test unit to be executed; determines the execution status of each test unit to be executed based on the process output information corresponding to each test unit to be executed, and generates test status data associated with the basic device data; performs test progress storage processing and test result display processing based on the test status data, and generates test record data based on the test status data and process output information. Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0080] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0081] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0082] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described automated computer hardware testing method, thereby solving the technical problem of how to improve the efficiency of computer hardware production testing. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the automated computer hardware testing method provided in the above embodiments, and will not be repeated here.

[0083] This application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the computer hardware automated testing method described above.

[0084] The computer program product provided in this application can solve the technical problem of how to improve the efficiency of computer hardware production testing. Compared with the prior art, the beneficial effects of the computer program product provided in the embodiments of this application are the same as the beneficial effects of the computer hardware automated testing method provided in the above embodiments, and will not be repeated here.

[0085] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent scope of this application.

Claims

1. A method for automated testing of computer hardware, characterized in that, The method includes: Obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding basic device data based on the device identification information and hardware configuration description information; Read the test process configuration data corresponding to the basic data of the device, and parse the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; Based on the process organization relationship and the execution association information, the multiple test units to be executed are scheduled and controlled to call the corresponding external test programs to perform test processing and obtain the process output information corresponding to each test unit to be executed. Based on the process output information corresponding to each of the test units to be executed, the execution status of each of the test units to be executed is determined, and test status data associated with the basic data of the device is generated. Based on the test status data, test progress is stored and test results are displayed, and test record data is generated based on the test status data and the process output information.

2. The method as described in claim 1, characterized in that, The step of obtaining the device identification information and hardware configuration description information of the target computer, and generating corresponding basic device data based on the device identification information and hardware configuration description information, includes: Obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding basic device data based on the device identification information and hardware configuration description information; Based on the system management interface, the processor information, memory information, graphics processing information, storage medium information, and network adaptation information of the target computer are queried to obtain the hardware configuration description information; The device identification information and the hardware configuration description information are structured, organized, and encapsulated to generate corresponding basic device data.

3. The method as described in claim 1, characterized in that, The steps of reading the test process configuration data corresponding to the device's basic data, and parsing the test process configuration data to obtain the process organization relationship and execution association information of multiple test units to be executed, include: Read the preset configuration file and combine it with the device's basic data to determine the test process configuration data that matches the target computer. The test process configuration data is used to characterize multiple test nodes and their configuration content in the test process. The test process configuration data is parsed to extract the process hierarchy, sequence, and group affiliation of each test node, thereby obtaining the process organization relationship of multiple test units to be executed. Based on the test process configuration data, the calling object, execution conditions and result judgment criteria corresponding to each of the test units to be executed are determined, and the execution association information of multiple test units to be executed is obtained.

4. The method as described in claim 1, characterized in that, The step of scheduling and controlling the multiple test units to be executed based on the process organization relationship and the execution association information to call the corresponding external test program to execute the test processing, and obtaining the process output information corresponding to each test unit to be executed, includes: Based on the process organization relationship, the execution order of the multiple test units to be executed and the test unit to be scheduled are determined, and the corresponding scheduling control instructions are constructed in combination with the execution association information; Based on the scheduling control instruction, the external test program corresponding to the currently scheduled test unit is invoked, and the external test program is controlled to perform test processing on the currently scheduled test unit. During the execution of the test process by the external test program, the running output and abnormal output fed back by the external test program are collected to obtain the process output information corresponding to each test unit to be executed.

5. The method as described in claim 1, characterized in that, The step of determining the execution status of each of the test units to be executed based on the process output information corresponding to each of the test units to be executed, and generating test status data associated with the basic data of the device, includes: The process output information corresponding to each test unit to be executed is parsed to extract the status identification information, exception prompt information and execution completion information related to the test execution results; Based on the status identification information, the exception prompt information, and the execution completion identification information, the execution results of each of the test units to be executed are identified, and the execution status corresponding to each of the test units to be executed is determined. The execution status of each of the test units to be executed is associated with the basic data of the device, and test status data is generated by combining the identification information of each of the test units to be executed.

6. The method as described in claim 1, characterized in that, The steps of storing test progress and displaying test results based on the test status data, and generating test record data based on the test status data and the process output information, include: Based on the test status data, the status change content corresponding to each test unit to be executed is associated and organized, and the associated and organized status content is written into a preset status storage carrier to complete the test progress storage process. Based on the test status data, the result identifier and stage status corresponding to each of the test units to be executed are determined, and the result identifier and stage status corresponding to each of the test units to be executed are output to the preset display interface to complete the test result display process. The test status data and the process output information are summarized and correlated to generate test record data corresponding to the basic equipment data.

7. An automated testing device for computer hardware, characterized in that, The device includes: The basic data module is used to obtain the device identification information and hardware configuration description information of the target computer, and generate corresponding device basic data based on the device identification information and hardware configuration description information; The data parsing module is used to read the test process configuration data corresponding to the basic data of the device, and to parse the process organization relationship and execution association information of multiple test units to be executed based on the test process configuration data; The scheduling and control module is used to schedule and control the multiple test units to be executed based on the process organization relationship and the execution association information, so as to call the corresponding external test program to execute the test processing and obtain the process output information corresponding to each test unit to be executed. The status determination module is used to determine the execution status of each of the test units to be executed based on the process output information corresponding to each of the test units to be executed, and to generate test status data associated with the basic data of the device. The test record module is used to store test progress and display test results based on the test status data, and to generate test record data based on the test status data and the process output information.

8. An automated testing device for computer hardware, characterized in that, The device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the computer hardware automated testing method as described in any one of claims 1 to 6.

9. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the computer hardware automated testing method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the steps of the computer hardware automated testing method as described in any one of claims 1 to 6.

Images