Difference between revisions of "Test API"
(3 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | + | The APIs for testing in C/C++ are documented in the following articles: | |
− | + | * [[Test Point Testing in C/C++|Test Point Testing API]] (for writing native test point validation tests) | |
− | + | * [[Runtime Test Services|Runtime Test Services API]] (for dynamic test result manipulation) | |
− | + | * [[File Transfer Services|File Transfer API]] (for host file manipulation from the device under test) | |
− | + | * [[Test Fixturing in C/C++|Test Fixturing]] (for test unit fixturing in native code) | |
− | + | * [[Test Documentation in C/C++|Test Documentation]] (how to document your native test units) | |
− | + | * [[Test Double|Test Doubles]] (for advanced dependency interception/function mocking in native code) | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
[[Category:Test Units]] | [[Category:Test Units]] |
Latest revision as of 09:16, 7 July 2015
The APIs for testing in C/C++ are documented in the following articles:
- Test Point Testing API (for writing native test point validation tests)
- Runtime Test Services API (for dynamic test result manipulation)
- File Transfer API (for host file manipulation from the device under test)
- Test Fixturing (for test unit fixturing in native code)
- Test Documentation (how to document your native test units)
- Test Doubles (for advanced dependency interception/function mocking in native code)