Entity component system test system and method, storage medium and program product

Abstract

The invention relates to the technical field of system testing, and discloses an entity component system testing system and method, a storage medium and a program product.A configuration manager responds to target testing configuration parameters defined by a user, and a testing center initializes all testing actuators based on the target testing configuration parameters; a user selects a target test case, a test center is integrated with a corresponding relationship between each test case and a test executor, the test of the corresponding test executor is triggered based on a target test case set, and the test executor tests the entity component system to be tested based on the target test case. The complex system is decomposed into a plurality of independent test units, so that the test complexity is greatly reduced, developers can quickly and accurately position and repair problems in the system, and the development and debugging period is remarkably shortened.

Description

Technical Field

[0001] The present invention relates to the technical field of system testing, and in particular to a physical component system testing system, method, storage medium and program product. Background Art

[0002] The Entity Component System (ECS) architecture is widely used in various large-scale projects. By separating data and behavior, ECS improves the scalability and performance of the system. However, as the scale of the system expands, how to test efficiently, especially for complex interactions and difficult bug location, has become a major challenge in the development process. Currently, there are mainly the following testing methods for the ECS architecture: Manual testing: Developers manually write test cases to gradually verify system functions, but this method is inefficient and prone to missing edge cases; Automated unit testing: Using existing testing frameworks (such as JUnit, NUnit) to perform unit testing on components and systems, although this improves testing efficiency, it is often unable to cope with complex interactions and large-scale data; Integration testing and end-to-end testing: By simulating the complete application process, the overall function of the system is verified, but this type of test is usually time-consuming and it is difficult to provide timely feedback on specific problems; Debugging methods based on logs and monitoring: By recording log information during system runtime and combining monitoring tools, problems can be located and analyzed, but this method relies on runtime data and it is difficult to detect potential problems in a timely manner. Summary of the invention

[0003] In view of this, the present invention provides a physical component system testing system, method, storage medium and program product to solve the problems that traditional system testing methods are inefficient, time-consuming and difficult to promptly feedback specific problems when processing complex interactions and large-scale data.

[0004] In a first aspect, the present invention provides an entity component system testing system, the system comprising a configuration manager, a test center and a test executor, wherein the configuration manager is integrated with a system test configuration parameter file, for responding to target test configuration parameters customized by a user based on the system test configuration parameter file, and sending the system test configuration parameters to the test center, wherein the system test configuration parameters represent various settings and options for controlling the test process; the test center is used to initialize all test executors based on the target test configuration parameters sent by the configuration manager, and provide a test execution interface to the user so that the user can select a target test case; the test center is integrated with a correspondence between each test case and the test executor, for triggering a test operation of a corresponding test executor based on a target test case set selected by the user, wherein the target test case set includes at least one target test case; the test executor is marked with its corresponding entity component system to be tested, for responding to the test operation triggered by the test center, and testing the entity component system to be tested based on the target test case.

[0005] The entity component system testing system provided by the present invention has a configuration manager that responds to user-defined target test configuration parameters and sends them to a test center. The test center initializes all test executors based on the target test configuration parameters and provides a test execution interface to the user so that the user can select a target test case. The test center integrates the correspondence between each test case and the test executor, and is used to trigger the test operation of the corresponding test executor based on the target test case set selected by the user. After the test executor responds to the triggered test operation, it can test the entity component system to be tested based on the target test case. By decomposing a complex system into multiple independent test units, the test complexity is greatly reduced, so that developers can quickly and accurately locate and fix problems in the system, significantly shortening the development and debugging cycle. Through modular design, the test process is made more flexible, and developers can replace or expand modules according to actual needs. It is optimized for the ECS architecture and shows higher efficiency and test coverage when processing complex interactions, concurrent operations and large-scale data.

[0006] In an optional embodiment, the test executor is a specific test executor, which is used to test the entity component system to be tested marked by it based on the target test case corresponding to itself. The system also includes a basic test executor, wherein the basic test executor is used to parse the first test case sent by the test center, determine the first entity component system to be tested corresponding to the first test case, and test the first entity component system to be tested based on the first test case. The first test case matches the target test case set with the correspondence between the test cases and the test executor through the test center. If a target test case fails to match the test executor successfully, the target test case that fails to match the test executor is determined as the first test case and sent to the basic test executor.

[0007] The present invention designs a basic test executor and a specific test executor to jointly implement the test of the entity component system. The test executor can directly call the method of the ECS system instance to verify whether its behavior meets the expectations, which significantly improves the test efficiency. In particular, for large-scale data processing scenarios, the basic test executor can provide a general test function and execute the test of non-specific entity component systems based on non-specific test cases, thereby improving the comprehensiveness of the entity component system test.

[0008] In an optional implementation, the test executor is further configured to generate a test result based on the logging settings in the target test configuration parameters, and present the test result to the user through a test execution interface.

[0009] The present invention can record the logs during the test process based on the test configuration parameters set by the user, and display the logs to the user, so that the user can clearly understand the process of system testing. By optimizing the test tool chain and process, not only the test quality is improved, but also the cost of system testing and the workload of users are reduced.

[0010] In an optional implementation, the entity component system to be tested is a system module corresponding to the entity component to be tested in the ECS system selected by the user.

[0011] The present invention provides a module for users to select system modules corresponding to entity components to be tested, so that users can select systems to be tested according to different test scenarios, and users can easily customize the test process according to project requirements.

[0012] In a second aspect, the present invention provides an entity component system testing method, which is applied to the entity component system testing system of the first aspect or any corresponding embodiment thereof, and the method includes: in response to target test configuration parameters customized by a user based on a system test configuration parameter file, initializing all test executors based on the target test configuration parameters, wherein the system test configuration parameters represent various settings and options for controlling the test process; providing a test execution interface to the user so that the user can select a target test case; based on the target test case set selected by the user, triggering the test operation of the corresponding test executor so that the test executor tests the entity component system to be tested based on the target test case, wherein the target test case set includes at least one target test case, wherein each test case corresponds to the test executor, and the test executor is marked with its corresponding entity component system to be tested.

[0013] The entity component system testing method provided by the present invention responds to the target test configuration parameters customized by the user based on the system test configuration parameter file, initializes all test executors based on the target test configuration parameters, and provides a test execution interface to the user so that the user can select a target test case; based on the target test case set selected by the user, triggers the test operation of the corresponding test executor so that the test executor tests the entity component system to be tested based on the target test case. Under the ECS architecture, it can accurately verify specific system behaviors, realize automated management of the test process, simplify the test execution process, reduce human intervention, and further improve the reliability of the test.

[0014] In an optional implementation, the target test configuration parameters include at least test process resources, test basic configuration information and the test order of each entity component system to be tested, and initializing all test executors based on the target test configuration parameters includes: initializing all test executors based on the test basic configuration information, and releasing the test process resources to the test executor, the test process resources include at least the resource content of initialization before test execution, test execution and cleanup after test completion; marking them in the corresponding test executor according to the test order of each entity component system to be tested.

[0015] In an optional embodiment, the test executor is a specific test executor, which is used to test the entity component system to be tested marked by it based on the target test case corresponding to itself. Before the test executor tests the entity component system to be tested based on the target test case, the method also includes: obtaining the system identification of the entity component system to be tested, comparing the obtained system identification with the entity component system identification of the entity component to be tested marked by itself, and judging whether the entity component system to be tested is successfully associated; if the entity component system to be tested is successfully associated, checking whether the corresponding test case and the entity component system to be tested meet the safety test conditions; if the corresponding test case and the test safety conditions of the entity component system to be tested meet the safety test conditions, executing the step of testing the entity component system to be tested based on the target test case in the target test case set.

[0016] Before testing, the specific test executor of the present invention can also pre-determine whether the system identification of the entity component to be tested is consistent with the system identification of its own mark, and check whether the test conditions are met. Only after both are confirmed to be correct, will the system test be executed to ensure the safety and reliability of the system test.

[0017] In an optional embodiment, the entity component system testing system also includes a basic test executor, which tests the first entity component system to be tested based on the first test case in the target test case set, including: parsing and deserializing the first test case to determine the first entity component system to be tested corresponding to the first test case, the first test case matches the target test case set with the correspondence between the test cases and the test executor through the test center in the entity component system, if a target test case does not match the test executor successfully, then the target test case that does not match the test executor successfully is determined as the first test case; and the first entity component system to be tested is tested based on the first test case.

[0018] If the test center of the present invention determines that a test case does not successfully match the corresponding test executor, the basic test executor can be used to execute the test based on the unsuccessfully matched test case to ensure the integrity and comprehensiveness of the system test.

[0019] In a third aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the entity component system testing method of the second aspect or any corresponding embodiment thereof.

[0020] In a fourth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute the entity component system testing system of the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0022] Figure 1 is a schematic diagram of the structure of a physical component system testing system according to an embodiment of the present invention; Figure 2 is a structural example diagram of an entity component system testing system according to an embodiment of the present invention; Figure 3 is a flow chart of a method for testing an entity component system according to an embodiment of the present invention; Figure 4 is an example diagram of the interaction of ports in a physical component system test system according to an embodiment of the present invention; Figure 5 is an example flow chart of an entity component system testing method according to an embodiment of the present invention; Figure 6 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0023] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0024] As the complexity of software systems increases, traditional testing methods can no longer meet the needs of complex interactions and large-scale data processing. As an efficient data processing design model, the Entity-Component-System (ECS) architecture is widely used in software development. Entities are basic objects in software, components are data containers attached to entities, and the system processes these component data to achieve specific behaviors. By separating objects (entities), data (components), and logic (systems), the ECS architecture significantly improves the performance and flexibility of the system, making large-scale data management and behavior processing possible, but this also puts higher requirements on testing.

[0025] Existing testing methods have the following problems in practice: Low efficiency of manual testing: Manually writing and executing test cases is time-consuming and laborious, and it is difficult to fully cover all scenarios; Insufficient unit test coverage: Traditional unit testing frameworks are difficult to fully simulate the high concurrency and multi-component interactions in the ECS architecture, resulting in low test coverage; High integration testing costs: Integration testing and end-to-end testing require simulating the complete system process, with a long testing cycle and inability to provide timely feedback and locate specific problems; Log debugging relies on the runtime environment: Debugging methods based on logs and monitoring rely on runtime data, and cannot detect problems in advance during the development phase, and analyzing complex log information requires professional skills; Lack of a unified testing tool chain: Existing testing tools are scattered and lack a unified testing framework and standards, resulting in a complex testing process and high maintenance costs.

[0026] In this embodiment, a physical component system testing system is provided, such as Figure 1 As shown, the system includes a configuration manager, a test center and a test executor, wherein the configuration manager is integrated with a system test configuration parameter file, which is used to respond to the target test configuration parameters customized by the user based on the system test configuration parameter file and send them to the test center, and the system test configuration parameters represent various settings and options for controlling the test process; the test center is used to initialize all test executors based on the target test configuration parameters sent by the configuration manager, and provide a test execution interface to the user so that the user can select a target test case; the test center is integrated with the correspondence between each test case and the test executor, which is used to trigger the test operation of the corresponding test executor based on the target test case set selected by the user, and the target test case set includes at least one target test case; the test executor is marked with its corresponding entity component system to be tested, which is used to respond to the test operation triggered by the test center, and test the entity component system to be tested based on the target test case.

[0027] The test framework of the embodiment of the present invention includes a configuration manager, a test center, a test executor, and auxiliary tools such as a test case data parsing tool and a test method tag, etc. Each module can communicate with each other through an interface to ensure the efficiency and flexibility of the system during the test process.

[0028] like Figure 2As shown, the configuration manager of the embodiment of the present invention is the control center of the entire test process, which is integrated with the system test configuration parameter file and is responsible for loading and managing the test configuration parameter file, wherein the test configuration parameters represent various settings and options for controlling the test process, including but not limited to whether to enable specific test functions, whether to record test logs, the root directory of the test file, the definition of the test detail level (whether to enable certain use cases), the test result output format, and the specific components to be tested in the ECS system (the system modules corresponding to the specific components). It allows users to customize the global test options, path information, test process and other test configuration parameters according to specific needs, ensuring that the tests in different environments can be adaptive, so that developers can easily customize the test process according to project requirements, saving time and resources. In the system architecture, the configuration manager ensures the flexibility of the test execution process by providing a set of dynamic configuration mechanisms. Users can adjust the test configuration parameters according to actual conditions to adapt to various test requirements. After the configuration manager responds to the user-defined target test configuration parameters, it can send the target test configuration parameters to the test center.

[0029] The test center of the embodiment of the present invention is the coordination module of the entire test framework, responsible for initializing the test environment, scheduling and managing the test executors, and ensuring that the test process is carried out as expected. It can load all related test executors and initialize them according to the target test configuration parameters sent by the configuration manager. Figure 2As shown, the initialization operation may include using the test marking method to mark the test case file path and output log file path of the test executor, and marking the corresponding test executor according to the execution order of the test executor in the target test configuration parameters, so that the test executor executes the test task in a predetermined order. The execution order may include the execution sequence of each test executor, and may also include the sequence of methods for a certain test executor to perform tests, just as an example; the initialization operation also includes resource management, initializing and releasing necessary resources during the test process, and determining the stability and consistency of the test environment. The test center will record all resource contents marked with initialization before testing, test execution, and cleanup methods after the test is completed, and can store initialization, test execution, and cleanup methods The resource methods managed by the test center are saved in a hash table, where the initialization mark, test mark and cleanup mark may include but are not limited to the test timing, type, number of days and date, respectively. As an example only, during the entire testing process, the test center ensures the coordination of each test module, ensures the rational use of resources and avoids conflicts, which not only simplifies the developer's workflow, but also ensures the systematicness and integrity of the test; after the initialization is completed, the test center can display the test execution interface to the user through the test executor window, and the user can select a specific test case in the interface and trigger the test operation. The test center integrates a one-to-one correspondence between each test case and the test executor, and in response to the target test case set selected by the user, it can trigger the test operation of the corresponding test executor.

[0030] The test executor is the core module for executing tests, such as Figure 2 As shown, the test executor tag with the entity system is used to configure the scope of application and the target entity component system of the test executor. It is specifically used to handle specific test requirements in the ECS system. It can verify whether the behavior of the entity component system is accurate by directly calling the method of the system instance. At the same time, it implements the test executor interface so that it can be uniformly scheduled. The test executor responds to the test operation triggered by the test center, and can test the entity component system to be tested based on its corresponding target test case. By applying the marking method to the test executor, it can ensure that the test process is automatically adjusted according to different system requirements, making the test process more flexible and adaptable.

[0031] Specifically, the entity component system to be tested is a system module corresponding to the entity component to be tested in the ECS system selected by the user.

[0032] The user of the embodiment of the present invention can select the system module corresponding to the entity component to be tested through the configuration manager. In the subsequent selection of test cases, the user can select the target test case corresponding to the previously selected entity component system to be tested to test the selected entity component system to be tested.

[0033] The present invention provides a module for users to select system modules corresponding to entity components to be tested, so that users can select systems to be tested according to different test scenarios, and users can easily customize the test process according to project requirements.

[0034] The entity component system testing system provided by the present invention has a configuration manager that responds to user-defined target test configuration parameters and sends them to a test center. The test center initializes all test executors based on the target test configuration parameters and provides a test execution interface to the user so that the user can select a target test case. The test center integrates the correspondence between each test case and the test executor, and is used to trigger the test operation of the corresponding test executor based on the target test case set selected by the user. After the test executor responds to the triggered test operation, it can test the entity component system to be tested based on the target test case. By decomposing a complex system into multiple independent test units, the test complexity is greatly reduced, so that developers can quickly and accurately locate and fix problems in the system, significantly shortening the development and debugging cycle. Through modular design, the test process is made more flexible, and developers can replace or expand modules according to actual needs. It is optimized for the ECS architecture and shows higher efficiency and test coverage when processing complex interactions, concurrent operations and large-scale data.

[0035] In an optional embodiment, the above-mentioned test executor is a specific test executor, which is used to test the marked entity component system to be tested based on its corresponding target test case. The entity component system testing system also includes a basic test executor, wherein the basic test executor is used to parse the first test case sent by the test center, determine the first entity component system to be tested corresponding to the first test case, and test the first entity component system to be tested based on the first test case.

[0036] Among them, the first test case matches the target test case set with the correspondence between each test case and the test executor through the test center. If a target test case fails to match the test executor successfully, the target test case that fails to match the test executor is determined as the first test case and sent to the basic test executor.

[0037] The specific test executor (specific system test executor or the above-mentioned test executor with entity system) of the embodiment of the present invention is extended or inherited from the basic test executor, and is specifically used to handle specific test requirements in the ECS system, that is, each specific test executor is marked with its corresponding entity component system to be tested, and can directly call the test case method of the corresponding entity component system to be tested to verify whether the behavior of the system is accurate, so as to achieve accurate verification of specific system behavior under the ECS architecture, simplify the test execution process, reduce human intervention, and further improve the reliability of the test; the basic test executor provides a general test function, which can be used for some test cases, and in the test After completion, a detailed test report will be generated. The test center will match the target test case set selected by the user with the correspondence between each test case and the test executor. If a target test case fails to match the test executor successfully, it means that it is not a specific test requirement of a system. The unmatched target test case can be sent to the basic test executor. The basic test executor can use the test case data parsing tool to parse the target test case, deserialize and determine the entity component system to be tested to which the target test case is applied. After the determination is completed, the basic test executor can test the corresponding entity component system to be tested based on the target test case to obtain the test results.

[0038] The present invention designs a basic test executor and a specific test executor to jointly implement the test of the entity component system. The test executor can directly call the method of the ECS system instance to verify whether its behavior meets the expectations, which significantly improves the test efficiency. In particular, for large-scale data processing scenarios, the basic test executor can provide a general test function and execute the test of non-specific entity component systems based on non-specific test cases, thereby improving the comprehensiveness of the entity component system test.

[0039] In an optional implementation, the test executor is further configured to generate test results based on the logging settings in the target test configuration parameters, and present the test results to the user through the test execution interface.

[0040] The test executor of an embodiment of the present invention can also generate a detailed log file based on the settings in the test configuration parameters (i.e., whether to record the test log is selected for the user in the configuration manager), including the execution status, results and any possible errors of each test step, and the test results and log file can be displayed to the user through the test executor window to form a test execution interface.

[0041] The present invention can record the logs during the test process based on the test configuration parameters set by the user, and display the logs to the user, so that the user can clearly understand the process of system testing. By optimizing the test tool chain and process, not only the test quality is improved, but also the cost of system testing and the workload of users are reduced.

[0042] According to an embodiment of the present invention, an embodiment of an entity component system testing method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0043] In this embodiment, a method for testing an entity component system is provided, which is applied to the above-mentioned entity component system testing system. Figure 3 is a flowchart of a method for testing an entity component system according to an embodiment of the present invention. Figure 3 As shown, the process includes the following steps: Step S301 , in response to a target test configuration parameter customized by a user based on a system test configuration parameter file, all test executors are initialized based on the target test configuration parameter.

[0044] Among them, system test configuration parameters represent various settings and options that control the test process.

[0045] like Figure 4 As shown, the user triggers the test of the entity component system, and the configuration manager is responsible for loading the test configuration parameter file, where the test configuration parameter file defines global test options, such as whether to enable logging, the storage path of test cases, etc. When the configuration is loaded, the configuration manager returns the test configuration parameter information to the user. After the configuration file is loaded, the user continues to trigger the initialization operation of the test center. The test center obtains the target test configuration parameters from the configuration manager, and loads all test executors based on the target test configuration parameters, scans and initializes all test executors in turn, and ensures that the test executors can work normally in subsequent processes. The specific test executor scans and associates the corresponding entity component system based on the identification of the specific entity component system marked by itself; through the marking and reflection mechanism, the test executor can identify the different functional modules of the system and prepare to call the interfaces of these modules during the actual testing process.

[0046] Step S302: providing a test execution interface to the user so that the user can select a target test case.

[0047] After the test executor completes associating the corresponding entity component system, the test execution interface can be displayed to the user through the test executor window. The user can select the target test case in the test execution interface and trigger the test operation.

[0048] Step S303 : triggering the test operation of the corresponding test executor based on the target test case set selected by the user, so that the test executor tests the entity component system to be tested based on the target test case.

[0049] The target test case set includes at least one target test case, wherein each test case has a corresponding relationship with a test executor, and the test executor is marked with its corresponding entity component system to be tested.

[0050] The test center of the embodiment of the present invention can match the target test case set selected by the user with the correspondence between each test case and the test executor based on the correspondence between each test case and the test executor integrated by itself, determine the correspondence between the target test case and the test executor, and trigger the test executor to perform the test operation. The test executor tests the corresponding marked entity component system to be tested based on the target test case. If the test center determines that a target test case has not been successfully matched with any test executor, the target test case is sent to the basic test executor. The basic test executor obtains and parses the target test case, and can deserialize it through the test case output parsing tool to obtain a specific test case object (i.e., the entity component system to be tested), and can test the determined test case object based on the target test case.

[0051] The entity component system testing method provided in this embodiment responds to the target test configuration parameters customized by the user based on the system test configuration parameter file, initializes all test executors based on the target test configuration parameters, and provides a test execution interface to the user so that the user can select a target test case; based on the target test case set selected by the user, triggers the test operation of the corresponding test executor so that the test executor tests the entity component system to be tested based on the target test case. Under the ECS architecture, it can accurately verify specific system behaviors, realize automated management of the test process, simplify the test execution process, reduce human intervention, and further improve the reliability of the test.

[0052] Specifically, based on the target test configuration parameters, all test executors are initialized, including: initializing all test executors based on the test basic configuration information, and releasing the test process resources to the test executors, the test process resources at least include the resource content of initialization before test execution, test execution and cleanup after test completion; marking them in the corresponding test executors according to the test order of each entity component system to be tested.

[0053] The target test configuration parameters include at least test process resources, test basic configuration information and the test sequence of each entity component system to be tested.

[0054] The test center of the embodiment of the present invention can use the test marking method to mark the test case file path and output log file path of the test executor, and mark the corresponding test executor according to the execution order of the test executor in the target test configuration parameters, so that the test executor executes the test task in a predetermined order. The execution order may include the execution sequence of each test executor, and may also include the sequence of methods for testing by a certain test executor, just as an example; it can also initialize and release necessary resources during the test process to determine the stability and consistency of the test environment. The test center will record all resource contents marked with initialization before testing, test execution and cleanup methods after the test is completed, and can save the resource methods of initialization, test execution and cleanup in a hash table, wherein the initialization mark, test mark and cleanup mark may include but are not limited to the test timing, type, number of days and date, respectively, just as an example. During the entire testing process, the test center ensures the coordination of each test module, ensures the rational use of resources and avoids conflicts, which not only simplifies the workflow of developers, but also ensures the systematicness and integrity of the test.

[0055] In an optional embodiment, the above-mentioned test executor is a specific test executor, which is used to test the entity component system to be tested marked by it based on the target test case corresponding to itself. Before the test executor tests the entity component system to be tested based on the target test case, the method also includes: obtaining the system identification of the entity component system to be tested, comparing the obtained system identification with the entity component system identification of the entity component to be tested marked by itself, and judging whether the entity component system to be tested is successfully associated; if the entity component system to be tested is successfully associated, checking whether the corresponding test case and the entity component system to be tested meet the safety test conditions; if the corresponding test case and the test safety conditions of the entity component system to be tested meet the safety test conditions, executing the step of testing the entity component system to be tested based on the target test case in the target test case set.

[0056] The above-mentioned test executor is a specific test executor, which corresponds to the associated test case and the entity component system to be tested, and is used to test the entity component system to be tested marked by it based on the target test case corresponding to itself. Specifically, Figure 4As shown, before testing, a specific test executor can verify the association with the entity component system to be tested through system marking. For example, it can obtain the system identification of the entity component system to be tested, compare the obtained system identification with the entity component system to be tested marked by itself, and determine whether the entity component system to be tested is successfully associated. If the association is successful, it can then detect whether the corresponding test cases and the entity component system to be tested meet the security test conditions. For example, it can determine whether the test conditions are met through the code in the specific test executor. If the security test conditions are met, the entity component system to be tested is tested based on the target test case. If the security test conditions are not met, the test operation can be terminated.

[0057] Before testing, the specific test executor of the present invention can also pre-determine whether the system identification of the entity component to be tested is consistent with the system identification of its own mark, and check whether the test conditions are met. Only after both are confirmed to be correct, will the system test be executed to ensure the safety and reliability of the system test.

[0058] In an optional embodiment, the entity component system testing system also includes a basic test executor, which tests the first entity component system to be tested based on the first test case in the target test case set, including: parsing and deserializing the first test case to determine the first entity component system to be tested corresponding to the first test case, the first test case matches the target test case set with the correspondence between each test case and the test executor through the test center in the entity component system, if a target test case does not match the test executor successfully, then the target test case that does not match the test executor successfully is determined as the first test case; and the first entity component system to be tested is tested based on the first test case.

[0059] If the test center of the embodiment of the present invention determines that a target test case has not been successfully matched with any test executor, the target test case will be sent to the basic test executor. The basic test executor obtains and parses the target test case, and can deserialize it through the test case output parsing tool to obtain a specific test case object (i.e., the entity component system to be tested), and can then test the determined test case object based on the target test case.

[0060] If the test center of the present invention determines that a test case does not successfully match the corresponding test executor, the basic test executor can be used to execute the test based on the unsuccessfully matched test case to ensure the integrity and comprehensiveness of the system test.

[0061] In a specific embodiment, Figure 5As shown, before designing the test framework of the entity component system, the test case content can be written in advance, the test case file format can be defined, the test case file parsing can be implemented, and the test code logic can be output to the test log. After that, the test can be performed based on the entity component system test system. The configuration manager provides the user with an interface for customizing the target test configuration parameters. The test center initializes the test environment, schedules and manages the test executor based on the target test configuration parameters to ensure the efficient execution of the test process. The basic tester obtains the parsed test case, deserializes to determine the corresponding entity component system to be tested, and executes the test. The specific test executor tests the marked entity component system to be tested based on its corresponding target test case, verifies the behavior of the entity component system to be tested, records the log file, and displays it to the user. For detailed description, please refer to the above embodiment, which will not be repeated here.

[0062] See also Figure 6 , Figure 6 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 6 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 6 A processor 10 is taken as an example.

[0063] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0064] The memory 20 stores instructions executable by at least one processor 10, so that at least one processor 10 executes the method shown in the above embodiment.

[0065] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0066] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0067] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 6 The example of connecting through bus is taken in the following.

[0068] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device may be a touch screen.

[0069] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0070] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of the computer program instruction in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc., and accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.

[0071] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A physical component system testing system, characterized in that: The system includes a configuration manager, a test center and a test executor, wherein: The configuration manager is integrated with a system test configuration parameter file, which is used to respond to the target test configuration parameters customized by the user based on the system test configuration parameter file and send them to the test center, wherein the system test configuration parameters represent various settings and options for controlling the test process; The test center is used to initialize all test executors based on the target test configuration parameters sent by the configuration manager, and provide a test execution interface to the user so that the user can select the target test case; The test center integrates the correspondence between each test case and the test executor, and is used to trigger the test operation of the corresponding test executor based on the target test case set selected by the user, wherein the target test case set includes at least one target test case; The test executor is marked with its corresponding entity component system to be tested, and is used to respond to the test operation triggered by the test center and test the entity component system to be tested based on the target test case.

2. The entity component system testing system according to claim 1, characterized in that: The test executor is a specific test executor, which is used to test the marked entity component system to be tested based on the target test case corresponding to itself. The system also includes a basic test executor, wherein: The basic test executor is used to parse the first test case sent by the test center, determine the first entity component system to be tested corresponding to the first test case, and test the first entity component system to be tested based on the first test case. The first test case matches the target test case set with the correspondence between each test case and the test executor through the test center. If a target test case fails to match the test executor successfully, the target test case that fails to match the test executor is determined as the first test case and sent to the basic test executor.

3. The system according to claim 1, characterized in that The test executor is also used to generate test results based on the logging settings in the target test configuration parameters, and present the test results to the user through the test execution interface.

4. The system according to claim 1, characterized in that The entity component system to be tested is a system module corresponding to the entity component to be tested in the ECS system selected by the user.

5. A method for testing an entity component system, characterized in that: The method is applied to the entity component system testing system according to any one of claims 1 to 4, and the method comprises: In response to a target test configuration parameter customized by a user based on a system test configuration parameter file, initializing all test executors based on the target test configuration parameter, the system test configuration parameter representing various settings and options for controlling a test flow; Provide a test execution interface to the user so that the user can select a target test case; Based on a target test case set selected by a user, a test operation of a corresponding test executor is triggered so that the test executor tests the entity component system to be tested based on the target test case. The target test case set includes at least one target test case, wherein each test case corresponds to a test executor, and the test executor is marked with its corresponding entity component system to be tested.

6. The method according to claim 5, characterized in that The target test configuration parameters at least include test process resources, test basic configuration information and the test sequence of each entity component system to be tested. Initializing all test executors based on the target test configuration parameters includes: Initialize all test executors based on the test basic configuration information, and release the test process resources to the test executors, wherein the test process resources at least include resource contents of initialization before test execution, test execution, and cleanup after test completion; The test sequences of the entity component systems to be tested are marked in the corresponding test executors.

7. The method according to claim 5, characterized in that The test executor is a specific test executor, which is used to test the entity component system to be tested marked by it based on the target test case corresponding to itself. Before the test executor tests the entity component system to be tested based on the target test case, the method also includes: Obtaining the system identifier of the entity component system to be tested, comparing the obtained system identifier with the system identifier of the entity component to be tested marked by itself, and determining whether the entity component system to be tested is successfully associated; If the entity component system to be tested is successfully associated, check whether the corresponding test cases and the entity component system to be tested meet the safety test conditions; If the corresponding test case and the test safety conditions of the entity component system to be tested meet the safety test conditions, the step of testing the entity component system to be tested based on the target test case in the target test case set is executed.

8. The method according to claim 7, characterized in that The entity component system testing system further includes a basic test executor, which tests the first entity component system to be tested based on a first test case in a target test case set, including: The first test case is parsed and deserialized to determine the first entity component system to be tested corresponding to the first test case. The first test case matches the target test case set with the correspondence between each test case and the test executor through the test center in the entity component system. If a target test case fails to match the test executor, the target test case that fails to match the test executor is determined as the first test case. The first entity component system to be tested is tested based on the first test case.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the entity component system testing method according to any one of claims 4 to 8.

10. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to cause a computer to execute the entity component system testing method according to any one of claims 4 to 8.

Images