Utility function for abstraction of test result output format. More...
Utility function for abstraction of test result output format.
The TURO module provides an abstraction layer allowing salient data to be provided for tests independent of format or medium. The intention is to have a test that expects some data, for example, reading some registers, output the results in a know way, for example json. This should help keeping the test results stable and not lock anyone into a particular format. If JSON is too heavy all tests using this can be swapped out for something lighter, for example CBOR. Then the tests should not have to be adapted. There can also be python layers that coordinate the output results, ideally done with riotctrl.
Only one implementation should be selected, for example, test_utils_result_output_json.
Some of the design decisions include:
USEMODULE
:test_utils_result_output_check
: Test result output structuretest_utils_result_output_json
: Test result output with JSONtest_utils_result_output_txt
: Test result output plain textSome limitations are:
Modules | |
Test Utils Result Output Helpers | |
Common functions and helpers that all implementations can use. | |
Test Utils Result Output Implementation API | |
The turo API that must have an implementation. | |
Test result output plain text | |
Enable this module to have results output as text. | |
Test result output structure | |
Enable this module to check the result structure. | |
Test result output with JSON | |
Enable this module to have results output as json. | |
Files | |
file | result_output.h |
Provides abstraction and convention for output of test results. | |