1 OVERVIEW

With the rapid development of hardware components, the functions of embedded systems are becoming increasingly powerful and complex. From early systems with only simple control functions, it has developed into intelligent systems that are widely used in various fields and have diverse functions, such as smart homes, smart cars, industrial automation, etc. This has led to an increasing scale and complexity of embedded software, as well as higher requirements for software quality and reliability, resulting in a significant increase in the difficulty and workload of embedded software testing work.

Early embedded systems were relatively simple, and traditional manual testing methods were able to meet testing requirements to a certain extent. However, with the increasing complexity of embedded software, problems such as low efficiency, easy errors, and difficulty in repeated execution of manual testing have gradually become prominent. It is no longer possible to conduct comprehensive, accurate, and efficient testing of large-scale embedded software, and cannot meet the needs of rapid iteration and high-quality development of embedded software.

In response to the above issues, ZC provides complete embedded automation testing services, which can effectively improve customer testing efficiency, reduce testing costs, and improve product quality.

2 AUTOMATED TESTING PLAN

Test Process

Config:Different Configuration Files

Compiler: Compile

Debugger: Burn debugging

TestCase: Test Code

TestResult: Test Result

TestReport: Test Report

3 TEST PROCESS

1. Generate multiple sets of configuration files Config through configuration tools (such as MuNiu tool, EB tool).

Multiple sets of Config

2. Add test code to the compilation path

Method 1: Test through UART serial port printing

Uart prints logs

Method 2: Test by reading the test result variables in the test code

Embedded testing code

3. Automatically compile multiple sets of Config through the Makefile command line and generate elf files

Supports multiple compilers and can be operated in command-line format, making automation more convenient

Makefile compilation environment

4. Using Python to call the debugger for burning, running, and testing

Lauterbach log

5. Call the debugger in Python to obtain the result

Lauterbach's output result

6. Automatically generate test reports based on the results

Can customize the generation of test reports

4 TESTING EQUIPMENT DESCRIPTION

Hardware Requirements

Communication devices: Different communication devices are required in different testing environments. For example, when testing CAN communication, CAN related communication devices are needed, mainly requiring Python to be able to call the device's API for operation