Interface testing method, device and equipment for operating system

Abstract

The invention provides an interface test method, device and equipment for an operating system. The method comprises the following steps: acquiring multiple pieces of target test interface information of a target function module of an embedded operating system; determining a test point of each target test interface according to the multiple pieces of target test interface information; obtaining a test case for testing the target test interface; verifying the test point of the target test interface through a plurality of target functions of the test case to obtain a verification result; and obtaining test results of a plurality of target test interfaces in the target function module according to the verification result. According to the scheme, integration testing can be carried out on the interface of the embedded operating system.

Description

Technical Field

[0001] This invention relates to the field of computer information technology processing technology, and in particular to an interface testing method, apparatus and equipment for an operating system. Background Technology

[0002] With the booming development of maritime and aviation, communications and transportation, and industrial production automation, embedded operating systems have received widespread attention and application in various industries and fields. Consequently, their functions are becoming increasingly complex, and the number of interfaces for each function is also growing rapidly. Interface testing mainly verifies the functionality and stability of each component of the system under test. Its core lies in comprehensively and systematically verifying the transmission, processing, control, and interaction of data, while also checking the logical relationships between each subsystem and function.

[0003] Software testing can be categorized into various methods based on different standards and perspectives. For example, according to the different stages of test execution, testing can be divided into unit testing, integration testing, system testing, and acceptance testing; according to the different methods of test implementation, there are black-box testing, white-box testing, and gray-box testing, etc. In addition, there are various specialized tests such as functional testing, performance testing, interface testing, security testing, and compatibility testing, used to verify the performance of software in specific environments.

[0004] Interface testing is a crucial component and stage of system testing. However, in current test cases, most interface test cases focus solely on verifying the functionality of a single API interface. This approach leads to both arduous and complex test case design. Furthermore, the lack of a comprehensive interface testing framework further complicates the process. This is especially true when multiple interfaces collaborate—the so-called integration testing—as existing solutions fail to provide effective support and solutions. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide an interface testing method, apparatus and device for an operating system, which can perform integration testing on the interface of an embedded operating system.

[0006] To solve the above-mentioned technical problems, the technical solution of the present invention is as follows: An interface testing method for an operating system includes: Obtain multiple target test interface information for the target functional modules of the embedded operating system; Based on the information of the multiple target test interfaces, determine the test points for each target test interface; Obtain test cases for testing the target test interface; The test points of the target test interface are verified by using multiple objective functions of the test cases to obtain the verification results; Based on the verification results, the test results of multiple target test interfaces within the target functional module are obtained.

[0007] Optionally, obtain multiple target test interface information for the target functional modules of the embedded operating system, including: Obtain multiple functional modules of the embedded operating system and the interfaces within each functional module; The interfaces are categorized according to their functional modules, and the interface definition, input parameters, and output result information of each interface are determined to obtain multiple target test interface information.

[0008] Optionally, based on the multiple target test interface information, test points for each target test interface are determined, including: Based on the information of the multiple target test interfaces, determine the function of each target test interface; Based on the function of each target test interface, determine the test points for that target test interface.

[0009] Optionally, obtain test cases for testing the target test interface, including: Based on the test points of each target test interface, determine the target function required to verify the test points; Determine the expected results assuming the test points are correct; Test cases are obtained based on the objective function and expected results.

[0010] Optionally, the test points of the target test interface can be verified using multiple objective functions of the test cases to obtain verification results, including: Obtain the hardware and software configurations for deploying the embedded operating system to obtain the test environment; The embedded operating system is deployed in the test environment and the test cases are executed to obtain the execution results of multiple target functions within the test cases; Based on the execution result of the objective function, the verification result of the test points is obtained.

[0011] Optionally, the embedded operating system is deployed in the test environment and the test cases are executed to obtain the execution results of multiple objective functions within the test cases, including: The test cases are executed in the test environment to obtain the return values ​​of multiple target functions within the test cases; The execution result is obtained based on the returned value.

[0012] Optionally, based on the execution result of the objective function, the verification result of the test points is obtained, including: The execution result is compared with the expected result. When the execution result is consistent with the expected result, the verification result of the test point verification is obtained. When the execution result is inconsistent with the expected result, the verification result of the test point verification is obtained as failed.

[0013] The present invention also provides an interface testing device for an operating system, comprising: The acquisition module is used to acquire multiple target test interface information of the target functional modules of the embedded operating system; The processing module is configured to: determine the test points of each target test interface based on the multiple target test interface information; obtain test cases for testing the target test interfaces; verify the calls to the test points of the target test interfaces through multiple target functions of the test cases to obtain verification results; and, based on the verification results, test multiple target test interfaces within the target functional module through the test cases to obtain test results.

[0014] The present invention also provides a computing device, comprising: a processor and a memory storing a computer program, wherein the computer program, when executed by the processor, performs the method described above.

[0015] The present invention also provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method described above.

[0016] The above-described solution of the present invention has at least the following beneficial effects: The above-described solution of the present invention obtains multiple target test interface information of a target functional module of an embedded operating system; determines test points for each target test interface based on the multiple target test interface information; obtains test cases for testing the target test interfaces; verifies the test points of the target test interfaces through multiple objective functions of the test cases to obtain verification results; and obtains test results for multiple target test interfaces within the target functional module based on the verification results. This allows for integration testing of the interfaces of an embedded operating system. Attached Figure Description

[0017] Figure 1 This is a flowchart illustrating the interface testing method for the operating system according to an embodiment of the present invention; Figure 2 This is a schematic diagram of the target functional module interface classification of the operating system according to an embodiment of the present invention; Figure 3 This is a flowchart of the interface integration testing method for the operating system according to an embodiment of the present invention; Figure 4 This is a detailed interface testing flowchart of the interface integration testing method for the operating system according to an embodiment of the present invention; Figure 5 This is a structural diagram of the interface testing device for the operating system according to an embodiment of the present invention. Detailed Implementation

[0018] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0019] like Figure 1 As shown, an embodiment of the present invention proposes an interface testing method for an operating system, comprising: Step 11: Obtain multiple target test interface information for the target functional modules of the embedded operating system; Here, as Figure 2 As shown, the embedded operating system includes multiple interfaces. These interfaces are classified according to functional components, and the number and information of interfaces for each functional component are confirmed to obtain multiple target test interface information for multiple target functional modules.

[0020] Step 12: Determine the test points for each target test interface based on the multiple target test interface information; Here, we compile detailed information on each target test interface and determine its test points based on the functionality of each interface. Each test point refers to a specific function of the target test interface that is being tested.

[0021] Step 13: Obtain test cases for testing the target test interface; The test case is a set of test cases for all target test interfaces within the target functional module. Through this test case, the testing of all target test interfaces within the target functional module can be completed.

[0022] Step 14: Verify the test points of the target test interface through multiple objective functions of the test cases, and obtain the verification results; When multiple target functions within the test case are executed, each target function performs a corresponding operation and returns an execution result. Based on the execution result, it is determined whether the test points of the target test interface have met expectations, and the verification result is obtained.

[0023] Step 15: Based on the verification results, obtain the test results of multiple target test interfaces within the target functional module.

[0024] By combining the verification results of each test point, the test result of each target test interface can be obtained. For example, if the verification result of all test points for a target test interface is "pass", then the target test interface has passed the test.

[0025] In this embodiment, as Figure 3 As shown, the interface testing process for an embedded operating system is mainly divided into two parts: the test preparation phase and the test execution phase. In the test preparation phase, the main tasks are to analyze the interface testing requirements and design interface integration test cases based on these requirements. Simultaneously, a suitable test environment is set up to ensure that the designed test cases can be effectively executed. During this process, the test environment setup and test case design can be performed concurrently. When the test execution phase begins, the pre-set test cases will be actually run in the pre-built test environment. The progress and status of the entire testing process are monitored in real time, and the obtained test results are comprehensively recorded and deeply analyzed.

[0026] In an optional embodiment of the present invention, step 11, obtaining multiple target test interface information of the target functional module of the embedded operating system, may include: Step 111: Obtain multiple functional modules of the embedded operating system and the interfaces within each functional module; like Figure 2 As shown, the functional modules may include a task management interface module, an interrupt / exception management interface module, a clock / timer management interface module, a task synchronization and communication interface module, a memory management interface module, a file system interface module, a device management interface module, and a network communication interface module. Each functional module may be further divided into multiple sub-functional interface modules based on the number of interfaces and their functional characteristics.

[0027] Step 112: Classify the interfaces according to their functional modules, determine the interface definition, input parameters and output result information of each interface, and obtain multiple target test interface information.

[0028] Here, confirm the number of interfaces for each functional module of the system and list detailed interface information, including: interface definition, input parameters, output results, etc. Confirm the consistency and correctness of the interfaces, ensuring that the behavior of all interfaces conforms to established standards and specifications.

[0029] In an optional embodiment of the present invention, step 12, determining the test points for each target test interface based on the plurality of target test interface information, includes: Step 121: Determine the function of each target test interface based on the multiple target test interface information; Here, based on the interface definition, input parameters, and output results of the target test interface, the specific implementation function of the target test interface is clarified.

[0030] Step 122: Determine the test points of each target test interface based on its function.

[0031] Here, test points are determined for the interface function. The test points and test points developed for a certain function of the interface are analyzed and described in detail during the testing process, and the expected return results of the interface during the testing process are given.

[0032] In an optional embodiment of the present invention, step 13, obtaining test cases for testing the target test interface, includes: Step 131: Determine the target function required to verify the test point based on the test point of each target test interface; The objective function is used to implement the functionality of the test point, and the execution result of the objective function is used to verify whether the functionality of the test point can be implemented.

[0033] Step 132: Determine the expected result assuming the test point is correct; Step 133: Obtain test cases based on the objective function and expected results.

[0034] Here, the test cases have the functions of automatically identifying interfaces, executing target functions, and recording test results. The results are displayed intuitively and easily, quickly distinguishing between passed and failed test items. The designed test cases undergo rationality verification and review to ensure their effectiveness and comprehensiveness.

[0035] In an optional embodiment of the present invention, step 14, verifying the test points of the target test interface through multiple objective functions of the test cases to obtain verification results, includes: Step 141: Obtain the hardware and software configurations for deploying the embedded operating system to obtain the test environment; The hardware configuration includes detailed information about the server model, network card type, hard disk configuration, and network switch, among other devices, on which the embedded operating system is installed. The software configuration includes the kernel version of the embedded operating system, the configuration of the compilation environment, and other related software components. By configuring both the hardware and software, a test environment consistent with the actual usage environment of the embedded operating system is obtained, ensuring the authenticity and reliability of the test results.

[0036] Step 142: Deploy the embedded operating system in the test environment and execute the test cases to obtain the execution results of multiple objective functions within the test cases; specifically, step 142 includes: Step 1421: Execute the test cases in the test environment to obtain the return values ​​of multiple target functions within the test cases; Step 1422: Obtain the execution result based on the returned value.

[0037] Step 143: Based on the execution result of the objective function, obtain the verification result of the test points. Specifically, step 143 includes: Step 1431: Compare the execution result with the expected result. When the execution result is consistent with the expected result, the verification result of the test point verification is obtained. Step 1432: When the execution result is inconsistent with the expected result, a verification result indicating that the test point verification has failed is obtained.

[0038] Compare the execution result with the expected result. If they match, the objective function executed successfully, and the test point functionality is achieved. If they do not match, an error occurred during the execution of the objective function. The specific error needs to be investigated, and a problem report needs to be generated for subsequent regression testing. In this case, the test point functionality cannot be fully achieved, and the test point verification fails.

[0039] The method of this invention, in the test preparation phase, analyzes the interface testing requirements, clarifies the test objectives and scope, and designs interface integration test cases based on the requirements analysis results. It selects or configures suitable hardware, software, and supporting tools, builds the test environment, and ensures the test cases can be executed smoothly. In the test execution phase, test cases are executed in a predetermined order within the built test environment; the entire test process is monitored; test data and results are recorded, and problems and data are analyzed. Through the method of this invention, integration testing of the unit module interfaces of an embedded operating system is performed, achieving a clear and concise presentation of the results generated by the test cases running under this scheme.

[0040] The method of the present invention will be specifically described below with reference to a specific embodiment: Example 1: Integration testing of the memory management interface of an embedded operating system. Step 11: Obtain multiple target test interface information for the target functional modules of the embedded operating system; Memory management involves twelve functional interfaces, its core responsibility being the management and control of the internal details of the memory heap. This includes initializing the starting addresses and occupancy of dynamically allocated physical memory blocks, and establishing and maintaining a detailed allocation table. This allocation table clearly marks the allocated memory regions, unoccupied free regions, and the specific capacities of these regions, ensuring accurate tracking and efficient utilization of the entire memory space. Through these interfaces, the memory management system can effectively manage memory resources and optimize program execution efficiency.

[0041] Step 12: Determine the test points for each target test interface based on the multiple target test interface information; Based on the provided basic interface information, each interface underwent testing and analysis. Considering the specific functions of each interface, test points were planned in detail, and expected test results were defined. For example, when testing the memory allocation interface, it was necessary to determine whether the requested memory size could be correctly allocated, and to check the accuracy of the corresponding records in the allocation table. For the memory release interface, the focus was on verifying whether the relevant memory area could be correctly marked as available after the release operation, and whether the allocation table update was error-free. In addition, other interfaces also needed to be evaluated, such as whether the memory query interface could accurately report memory usage, and whether the memory reallocation interface maintained data integrity when adjusting memory block sizes. Through this series of tests, it was ensured that all interfaces could work stably and reliably, meeting the system's memory management requirements.

[0042] Steps 13 and 14: Obtain test cases for testing the target test interface; verify the test points of the target test interface through multiple objective functions of the test cases, and obtain the verification results; First, a memory partition is created by calling the `mpart_create` interface function. Then, the `mpart_getinfo` interface function is used to obtain information about this partition, including the amount of used and free memory. Next, the `mpart_alloc` interface function is used to allocate a cache within this partition, and `mpart_getinfo` is called again to check the memory partition's usage. Next, the first byte of the cache region allocated in the previous step is set to the character 'a' for processing. Immediately afterward, `mpart_alloc` is called again to allocate a second cache within the partition, and `mpart_getinfo` is used to obtain the latest memory partition usage. Then, `mpart_realloc` is called to reallocate the initially allocated cache space, changing its size, and `mpart_getinfo` is called again to verify the repartitioned memory partition information, specifically checking whether the new partition still contains the character 'a'. After reallocation, the cache is released using `mpart_free`, and `mpart_getinfo` is used to update the memory partition information. For further testing, `mem_findmax` is called to find the largest free block in the current user heap, and the relevant information is printed. Next, `mpart_realloc` is used to reallocate the cache allocated in step four, and `mpart_getinfo` is called again to retrieve memory partition information. Then, `mpart_findmaxfree` is called to retrieve the largest free block within the partition. To test the impact of different memory management operations, `xnmalloc` is called to allocate 16 bytes of space in a non-allocated memory partition of the user heap. This 16 bytes are then added to the current memory partition using `mpart_addmem`, and `mpart_getinfo` is called again to update the memory partition information. Additionally, the `mpart_memalign` interface function is tested to ensure that the allocated cache space meets the boundary alignment requirements. To visually demonstrate the current memory status of the user heap, the `mem_show` interface function is called. Finally, the current memory partition is deleted using the `mpart_delete` interface function, and `mem_show` is called again to display the final memory status of the user heap. Each step includes verifying the correctness of the interface call using specific functions and checking whether the return parameters meet expectations. If any exception occurs, the system will provide an error message; if everything is normal, the corresponding return value will be output as expected.

[0043] An embedded operating system was installed on the required hardware environment. After the installation and configuration of the operating system and related software were completed, integration test cases were installed and compiled. The verification results were obtained after running these test cases.

[0044] Step 15: Based on the verification results, obtain the test results of multiple target test interfaces within the target functional module; According to such Figure 4 The verification results shown, combined with the description of the test points and the steps of the test case scheme, allow for an intuitive assessment of the call status of each interface and the obtaining of the test results for the target test interface.

[0045] like Figure 5 As shown, embodiments of the present invention also provide an operating system interface testing device 50, comprising: The acquisition module 51 is used to acquire multiple target test interface information of the target functional modules of the embedded operating system; The processing module 52 is configured to: determine the test points of each target test interface based on the multiple target test interface information; obtain test cases for testing the target test interfaces; verify the calls to the test points of the target test interfaces through multiple target functions of the test cases to obtain verification results; and, based on the verification results, test the multiple target test interfaces within the target functional module through the test cases to obtain test results.

[0046] Optionally, obtain multiple target test interface information for the target functional modules of the embedded operating system, including: Obtain multiple functional modules of the embedded operating system and the interfaces within each functional module; The interfaces are categorized according to their functional modules, and the interface definition, input parameters, and output result information of each interface are determined to obtain multiple target test interface information.

[0047] Optionally, based on the multiple target test interface information, test points for each target test interface are determined, including: Based on the information of the multiple target test interfaces, determine the function of each target test interface; Based on the function of each target test interface, determine the test points for that target test interface.

[0048] Optionally, obtain test cases for testing the target test interface, including: Based on the test points of each target test interface, determine the target function required to verify the test points; Determine the expected results assuming the test points are correct; Test cases are obtained based on the objective function and expected results.

[0049] Optionally, the test points of the target test interface can be verified using multiple objective functions of the test cases to obtain verification results, including: Obtain the hardware and software configurations for deploying the embedded operating system to obtain the test environment; The embedded operating system is deployed in the test environment and the test cases are executed to obtain the execution results of multiple target functions within the test cases; Based on the execution result of the objective function, the verification result of the test points is obtained.

[0050] Optionally, the embedded operating system is deployed in the test environment and the test cases are executed to obtain the execution results of multiple objective functions within the test cases, including: The test cases are executed in the test environment to obtain the return values ​​of multiple target functions within the test cases; The execution result is obtained based on the returned value.

[0051] Optionally, based on the execution result of the objective function, the verification result of the test points is obtained, including: The execution result is compared with the expected result. When the execution result is consistent with the expected result, the verification result of the test point verification is obtained. When the execution result is inconsistent with the expected result, the verification result of the test point verification is obtained as failed.

[0052] It should be noted that this device is the same as the method described above. All implementations in the above method embodiments are applicable to the embodiments of this device and can achieve the same technical effect.

[0053] Embodiments of the present invention also provide a computing device, including: a processor and a memory storing a computer program, wherein the computer program, when executed by the processor, performs the method as described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

[0054] Embodiments of the present invention also provide a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the method as described above. All implementations in the above method embodiments are applicable to this embodiment and can achieve the same technical effects.

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

[0056] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0057] In the embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

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

[0059] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0060] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0061] Furthermore, it should be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of the present invention. Moreover, the steps performing the above series of processes can naturally be executed in the order described, but are not necessarily required to be executed in chronological order; some steps can be executed in parallel or independently of each other. Those skilled in the art will understand that all or any step or component of the method and apparatus of the present invention can be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or a combination thereof. This is something that those skilled in the art can achieve by using their basic programming skills after reading the description of the present invention.

[0062] Therefore, the object of the present invention can also be achieved by running a program or a set of programs on any computing device. The computing device can be a known general-purpose device. Therefore, the object of the present invention can also be achieved simply by providing a program product containing program code implementing the method or apparatus. That is, such a program product also constitutes the present invention, and the storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium can be any known storage medium or any storage medium developed in the future. It should also be noted that in the apparatus and method of the present invention, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent to the present invention. Furthermore, the steps performing the above series of processes can naturally be performed in the order described, but are not necessarily required to be performed in chronological order. Some steps can be performed in parallel or independently of each other.

[0063] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. An interface testing method for an operating system, characterized in that, include: Obtain multiple target test interface information for the target functional modules of the embedded operating system; Based on the information of the multiple target test interfaces, determine the test points for each target test interface; Obtain test cases for testing the target test interface; The test points of the target test interface are verified by using multiple objective functions of the test cases to obtain the verification results; Based on the verification results, the test results of multiple target test interfaces within the target functional module are obtained.

2. The operating system interface testing method according to claim 1, characterized in that, Obtain multiple target test interface information for the target functional modules of the embedded operating system, including: Obtain multiple functional modules of the embedded operating system and the interfaces within each functional module; The interfaces are categorized according to their functional modules, and the interface definition, input parameters, and output result information of each interface are determined to obtain information on multiple target test interfaces.

3. The operating system interface testing method according to claim 1, characterized in that, Based on the information of the multiple target test interfaces, the test points for each target test interface are determined, including: Based on the information of the multiple target test interfaces, determine the function of each target test interface; Based on the function of each target test interface, determine the test points for that target test interface.

4. The operating system interface testing method according to claim 1, characterized in that, Obtain test cases for testing the target test interface, including: Based on the test points of each target test interface, determine the target function required to verify the test points; Determine the expected results assuming the test points are correct; Test cases are obtained based on the objective function and expected results.

5. The operating system interface testing method according to claim 1, characterized in that, The test points of the target test interface are verified through multiple objective functions of the test cases, and the verification results are obtained, including: Obtain the hardware and software configurations for deploying the embedded operating system to obtain the test environment; The embedded operating system is deployed in the test environment and the test cases are executed to obtain the execution results of multiple target functions within the test cases; Based on the execution result of the objective function, the verification result of the test points is obtained.

6. The operating system interface testing method according to claim 5, characterized in that, The embedded operating system is deployed in the test environment and the test cases are executed to obtain the execution results of multiple objective functions within the test cases, including: The test cases are executed in the test environment to obtain the return values ​​of multiple target functions within the test cases; The execution result is obtained based on the returned value.

7. The operating system interface testing method according to claim 5, characterized in that, Based on the execution result of the objective function, the verification results of the test points are obtained, including: The execution result is compared with the expected result. When the execution result is consistent with the expected result, the verification result of the test point verification is obtained. When the execution result is inconsistent with the expected result, the verification result of the test point verification is obtained as failed.

8. An interface testing device for an operating system, characterized in that, include: The acquisition module is used to acquire multiple target test interface information of the target functional modules of the embedded operating system; The processing module is used to determine the test points for each target test interface based on the multiple target test interface information. Obtain test cases for testing the target test interface; The test cases are used to verify the calls to test points of the target test interface by multiple objective functions, and the verification results are obtained. Based on the verification results, the test cases are used to test multiple target test interfaces within the target functional module, and the test results are obtained.

9. A computing device, characterized in that, include: A processor, a memory storing a computer program, wherein the computer program, when executed by the processor, performs the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, A storage instruction that, when executed on a computer, causes the computer to perform the method as described in any one of claims 1 to 7.

Images