SDK Development


Discuss and develop the mbed SDK.

You are viewing an older revision! See the latest version

Mbed SDK automated test suite reporting

Table of Contents

  1. Rationale

Rationale

Test suite and automation tools ought to report test data in at least few formats. Each format should satisfy different need. For example:

  • As console output while test suite is running as CLI (command line interface) application.
  • HTML report is human readable and can be presented to audience.
  • JUnit format (formatted XML) is used by various tools, test result parsers to generate reports, combine test data or just present it in Continuous Integration report page.
  • Other like database dump: export test result data directly to database located locally or remotely.

All mentioned above methods are supported by test suite at this time.

  • Console output is by default printing compile, build and rest result data. Additionally switches like -v or -V can be used for command line to get extra prints from test suite configuration and diagnostic or MUT (mbed under test) console output respectively.
  • HTML reports are used to generate simple HTML page with intuitive and simple test result matrix. HTML report is a single page containing all test results and test console output data. Below you can see example HTML report with active test result tool-tip: /media/uploads/PrzemekWirkus/test_report_html.png

All wikipages