White Paper: C++ practical testing for embedded systems part 2
Parasoft
White Paper: C++ practical testing for embedded systems part 2
In the second part of its latest White Paper, Parasoft discusses what it means ’to obtain particular goals with unit testing, like certain level of code coverage’.
Related images
The paper also focuses more closely on the safety relevance of unit testing, analysing coverage goals, coverage metrics and generating test cases.
If you are interested in reading the White Paper, please click on the link above to download the PDF.
White Paper: C++ practical testing for embedded systems part 2 — contents
- Achieving actual results with unit testing
- Coverage goals
- Coverage metrics
- Generating test cases
- Verifying outcomes
- Extending coverage
- Stubs and drivers
- Functional testing goals — faults injections
- Data sources
- Additional considerations
- Associated cost
- Memory monitoring
- Regression test suit
- Reporting
- Functional safety relevance of unit testing
- Safety integrity levels
- Unit testing and safety integrity levels
- Other safety standards
- Wrap up
Request more information
More stories
White Paper: achieving measurable results through proper workflow management download
According to Parasoft, its latest White Paper helps software teams ’achieve both productivity and quality by making quality tasks an integrated part of the daily development process’.
Data sheet: Parasoft Insure++ memory analysis and error detection download
Data sheet: Concerto application lifecycle management download
Data sheet: DotTEST comprehensive code quality tools download
DotTEST is an integrated program for automating best practices to improve software development.
Data sheet: C++ test for Wind River Workbench download
