General purpose testing arrangement for embedded module and subsystem based on host machine platform

Abstract

A embedded type modular and sub-system universal metering equipment based on the main computer platform, comprising a test example editing unit, a test use example pool, a test unit, a debugging unitand an analysis unit. The invention can transplant the modules and sub-systems originally needed to be downloaded into the hardware system onto the public host platform, thus avoiding the reduplicated exploitation of the test and measurement instrument.

Description

(1) Technical field [0001] The invention relates to a general testing device for embedded modules and subsystems based on a host platform. (2) Background technology [0002] Existing large-scale embedded system software testing mainly includes the following aspects: source code testing, module testing, integration testing, procedure testing, and performance testing. For source code testing, integration testing, procedure testing, and performance testing, there are generally corresponding testing tools provided by third parties. For example, source code testing tools include LogicScope (a software program measurement testing tool) and Rational Purify (a software program coverage testing tool). ); Many test instrument providers have corresponding emulators, protocol testers and security test tools. [0003] However, for module and subsystem testing, it is difficult to find a general module testing tool provided by a third party because it is closely related to the specific fu...

AI Technical Summary

Problems solved by technology

[0003] However, for module and subsystem testing, it is difficult to find a general module testing tool provided by a third party because it is closely related to the specific functions of the system, the implementation technology and the platform used.

The usual practice now is to write specific test tools for specific modules and subsystems by software testers, but because a large embedded system usually consists of dozens or even hundreds of modules, and for a large system, each The state transition of a module may be very complicated, and a large amount of test code needs to be written to cover all possible situations, which lacks versatility, low code utilization, and long test cycle. errors and omissions, leading to the introduction of some defects that should have been found during module testing into the system integration testing phase, and even lead to unreliability of test results

In addition, this test method generally requires the support of a specific hardware test environment, which affects the progress of software testing.

Images