Auto electronics
Informationalized Solution
R&D tools
As the increasing of the complication of automotive electronic software, it is necessary to finish software testing in the initial stage of development, find and fix problems in early stage of test to ensure software quality and delivery cycle time. Moreover, ISO26262 and ASPICE have made clear requests for software testing, which require that the software unit/integration testing should be done according to the test strategy.
Polelink provides not only solution to software unit/integration testing, but also test service for unit/integration testing.
Scope of test: dynamic testing for model/code (application layer): unit/component/software level
Figure 1 Test Scope
In software testing, in order to ensure the sufficient coverage of test, it is necessary to test the software units. It is needful to verify whether the performance of every subsystem or function conform to design expectations, whether the interfaces conform to requirements, and then combine the requirement coverage and model(function) coverage to ensure the test quality of each unit.
After unit testing, the units will be integrated according to architectural design to integration testing. Similarly, it is needful to verify whether the performances of the integrated components conform to design expectations, whether the interfaces conform to requirements, and then combine the requirement coverage and model(function) coverage to ensure the test quality of each component.
After component testing, it is necessary to test the software from application layer and verify whether the whole functions of software conform to expectations.
Test contents:
1) Test requirements confirmation: confirming the testability of test requirements, confirming ambiguities with developer, assisting to complete part of test requirements
2) Automatic testing environment construction
3) Test cases writing: making use of demand analysis, equivalent classes, boundary values, error-guessing and other methods to design test cases according to the requirements of ISO26262.
4) Review of test cases: reviewing test cases with customers and forming review record
5) Trace matrix: forming trace matrix by the bidirectional traceability between test cases, requirements and test evaluation
6) Test cases execution: executing written test cases automatically
7) Test results confirmation: receiving test results automatically
8) Results of coverage: making use of coverage indexes such as statement coverage, branch coverage, MCDC coverage, function coverage, call coverage, etc.
9) Problem location and analysis: data playback, problem analysis and producing suggestion of revision
10) Test report: automatically customizable test reports and closing reports
Test patterns:
Take the form of a combination of resident and non-resident. Core code will be tested in customer’s company, and non-core code will be tested in Polelink after negotiating with customers.
Implemented projects:
Ø BMS model testing of an OEM in Shanghai
Ø VUC model testing of a supplier in Beijing
Ø ADAS-ACC/LKA model testing of a supplier in Shanghai
Ø Light control model /code testing of a supplier in Shanghai
Ø TCU model testing of an institute in Beijing
Ø VCU model testing of an institute in Shanxi
Ø BMS model/code testing of a supplier in Shanghai
Our advantages:
Ø We are professional in automotive electronic software testing; the members of testing team have many-year work experience, and are familiar with the test specifications of industry
Ø We are focused on model testing based on simulink model, and familiar with MATLAB/Simulink and test tools
Ø We are focused on code testing based on C/C++, and familiar with mainstream compiler and code testing tools
Ø Integration: continuous test, tool integration and customized development
Ø Full-time project manager
Ø With the assistance of the experience from HIL testing, deeply understanding every testing object, automatically accumulation and complementing Polelink’s HIL business
Ø Focusing on testing, we have no competition with customers, so we can maximize customer information security and keep independence and objectivity
Ø Advanced automotive electronic test tool chain
Example of test project:
Figure 2 Graphical test case building
Figure 3 Description of test case
Figure 4 Automatic test report
Figure 5 Test problem list and problem analysis
Figure 6 Test data replay analysis