# utest: Asynchronous C++ Test Harness
This test harness allows you to execute a specified series of (asynchronous) C++ test cases with sensible default reporting and useful customization options.
Please note that this is a purposefully lean test harness, only dealing with test execution and providing default reporting handlers. It specifically does not support auto-discovery of test cases and does not provide you with test macros or other convenience functions.
Instead, the macros in the [unity module](https://github.com/ARMmbed/mbed-os/tree/master/features/frameworks/unity) can be used for this purpose. However, you are not required to use these, and can use your own macros if you wish.
Furthermore, test failure recovery through the use of exceptions or `longjmp` is not supported; the test will either continue and ignore failures or die by busy-waiting.
## Theory of Operation
A test specification contains a setup handler, several test cases and a teardown handler.
Each test case contains a textual description, setup, teardown and failure handler as well as the actual test handler.
The order of handler execution is:
1. Test setup handler.
1. For each test case:
1. Test case setup handler.
1. Test case execution handler.
1. (wait for timeout or callback validation in case of an asynchronous test case.)
1. (repeat test case execution handler if specified.)
1. Test case teardown handler.
1. Test teardown handler.
## Example
The following example showcases a lot of functionality and proper integration with the [Greentea test tool](https://github.com/ARMmbed/mbed-os-tools/tree/master/packages/mbed-greentea), while making use of the [unity test macros](https://github.com/ARMmbed/mbed-os/tree/master/features/frameworks/unity):
```cpp
#include "mbed.h"
#include "greentea-client/test_env.h"
#include "utest/utest.h"
#include "unity/unity.h"
using namespace utest::v1;
void test_simple() {
TEST_ASSERT_EQUAL(0, 0);
printf("Simple test called\n");
}
status_t test_repeats_setup(const Case *const source, const size_t index_of_case) {
// Call the default handler for proper reporting
status_t status = greentea_case_setup_handler(source, index_of_case);
printf("Setting up for '%s'\n", source->get_description());
return status;
}
control_t test_repeats(const size_t call_count) {
printf("Called for the %u. time\n", call_count);
TEST_ASSERT_NOT_EQUAL(3, call_count);
// Specify how often this test is repeated ie. n total calls
return (call_count < 2) ? CaseRepeatAll : CaseNext;
}
void test_callback_validate() {
// You may also use assertions here!
TEST_ASSERT_EQUAL_PTR(0, 0);
// Validate the callback
Harness::validate_callback();
}
control_t test_asynchronous() {
TEST_ASSERT_TRUE_MESSAGE(true, "(true == false) o_O");
// Set up a callback in the future. This may also be an interrupt!
EventQueue *queue = mbed_event_queue();
queue->call_in(100, test_callback_validate);
// Set a 200ms timeout starting from now
return CaseTimeout(200);
}
control_t test_asynchronous_timeout(const size_t call_count) {
TEST_ASSERT_TRUE_MESSAGE(true, "(true == false) o_O");
// Set a 200ms timeout starting from now,
// but automatically repeat only this handler on timeout.
if (call_count >= 5) {
// but after the 5th call, the callback finally gets validated
EventQueue *queue = mbed_event_queue();
queue->call_in(100, test_callback_validate);
}
return CaseRepeatHandlerOnTimeout(200);
}
// Custom setup handler required for proper Greentea support
status_t greentea_setup(const size_t number_of_cases) {
GREENTEA_SETUP(20, "default_auto");
// Call the default reporting function
return greentea_test_setup_handler(number_of_cases);
}
// Specify all your test cases here
Case cases[] = {
Case("Simple Test", test_simple),
Case("Repeating Test", test_repeats_setup, test_repeats),
Case("Asynchronous Test (200ms timeout)", test_asynchronous),
Case("Asynchronous Timeout Repeat", test_asynchronous_timeout)
};
// Declare your test specification with a custom setup handler
Specification specification(greentea_setup, cases);
int main()
{ // Run the test specification
Harness::run(specification);
}
```
Running this test will output the following:
```
{{timeout;20}}
{{host_test_name;default_auto}}
{{description;utest greentea example}}
{{test_id;MBED_OS}}
{{start}}
>>> Running 4 test cases...
>>> Running case #1: 'Simple Test'...
Simple test called
>>> 'Simple Test': 1 passed, 0 failed
>>> Running case #2: 'Repeating Test'...
Setting up for 'Repeating Test'
Called for the 1. time
>>> 'Repeating Test': 1 passed, 0 failed
>>> Running case #2: 'Repeating Test'...
Setting up for 'Repeating Test'
Called for the 2. time
>>> 'Repeating Test': 2 passed, 0 failed
>>> Running case #3: 'Asynchronous Test (200ms timeout)'...
>>> 'Asynchronous Test (200ms timeout)': 1 passed, 0 failed
>>> Running case #4: 'Asynchronous Timeout Repeat'...
>>> failure with reason 'Ignored: Timed Out'
>>> failure with reason 'Ignored: Timed Out'
>>> failure with reason 'Ignored: Timed Out'
>>> failure with reason 'Ignored: Timed Out'
>>> failure with reason 'Ignored: Timed Out'
>>> 'Asynchronous Timeout Repeat': 1 passed, 0 failed
>>> Test cases: 4 passed, 0 failed
{{success}}
{{end}}
```
## Detailed Description
### Handlers
There are five handler types you can, but do not have to, override to customize operation.
Please see the `utest/types.h` file for a detailed description.
1. `status_t test_setup_handler_t(const size_t number_of_cases)`: called before execution of any test case.
1. `void test_teardown_handler_t(const size_t passed, const size_t failed, const failure_t failure)`: called after execution of all test cases, and if testing is aborted.
1. `void test_failure_handler_t(const failure_t failure)`: called whenever a failure occurs anywhere in the specification.
1. `status_t case_setup_handler_t(const Case *const source, const size_t index_of_case)`: called before execution of each test case.
1. `status_t case_teardown_handler_t(const Case *const source, const size_t passed, const size_t failed, const failure_t reason)`: called after execution of each test case, and if testing is aborted.
1. `status_t case_failure_handler_t(const Case *const source, const failure_t reason)`: called whenever a failure occurs during the execution of a test case.
All handlers are defaulted for integration with the [Greentea testing tool](https://github.com/ARMmbed/mbed-os-tools/tree/master/packages/mbed-greentea).
### Test Case Handlers
There are three test case handlers:
1. `void case_handler_t(void)`: executes once, if the case setup succeeded.
1. `control_t case_control_handler_t(void)`: executes (asynchronously) as many times as you specify, if the case setup succeeded.
1. `control_t case_call_count_handler_t(const size_t call_count)`: executes (asynchronously) as many times as you specify, if the case setup succeeded.
To specify a test case you must wrap it into a `Case` class: `Case("mandatory description", case_handler)`. You may override the setup, teardown and failure handlers in this wrapper class as well.
The `Case` constructor is overloaded to allow you a comfortable declaration of all your callbacks and the order of arguments is:
1. Description (required).
1. Setup handler (optional).
1. Test case handler (required).
1. Teardown handler (optional).
1. Failure handler (optional).
#### Test Case Attributes
You can modify test case behavior by returning `control_t` modifiers:
- `CaseNext`: never repeats and immediately moves to next test case
- `CaseNoRepeat`: never repeats.
- `CaseRepeatAll`: repeats test case **with** setup and teardown handlers.
(源码)基于mbed OS和utest库的嵌入式系统HAL测试框架.zip （342个子文件） 
unity.c 42KB pithy.c 35KB mbed_printf_implementation.c 26KB mbed_ticker_api.c 20KB mbed_trace.c 17KB mbed_printf_armlink_overrides.c 9KB mbed_mpu_v7m.c 9KB mbed_boot.c 8KB mbed_mpu_v8m.c 8KB mbed_error.c 8KB mbed_pinmap_common.c 7KB mbed_gpio.c 6KB mbed_application.c 6KB mbed_wait_api_no_rtos.c 5KB mbed_itm_api.c 4KB mbed_compat.c 4KB mbed_critical.c 4KB mbed_printf_wrapper.c 4KB mbed_us_ticker_api.c 4KB mbed_lp_ticker_api.c 3KB main.c 3KB mbed_critical_section_api.c 3KB mbed_mpu_mgmt.c 3KB main.c 3KB main.c 2KB main.c 2KB main.c 2KB mbed_flash_api.c 2KB main.c 2KB main.c 2KB greentea_custom_io.c 1KB main.c 1KB mbed_assert.c 1KB mbed_gpio_irq.c 830B mbed_toolchain.cmake 6KB mbed_greentea.cmake 3KB GCC_ARM.cmake 3KB app.cmake 3KB debug.cmake 3KB release.cmake 3KB develop.cmake 3KB mbed_set_linker_script.cmake 3KB ARM.cmake 3KB CheckPythonPackage.cmake 3KB mbed_profile.cmake 2KB Cortex-M33-NS.cmake 2KB Cortex-M33.cmake 2KB Cortex-M55.cmake 2KB Cortex-M33FE-NS.cmake 1KB Cortex-M33F-NS.cmake 1KB Cortex-M4.cmake 1KB Cortex-M33FE.cmake 1KB Cortex-A9.cmake 1KB Cortex-M33F.cmake 1KB Cortex-M7F.cmake 1KB Cortex-M4F.cmake 1KB Cortex-M7FD.cmake 1KB Cortex-M23-NS.cmake 1KB Cortex-M7.cmake 1KB Cortex-M0+.cmake 1KB Cortex-M23.cmake 1KB Cortex-M3.cmake 1KB Cortex-M1.cmake 1KB Cortex-M0.cmake 1KB mbed_set_post_build.cmake 1004B main.cpp 83KB main.cpp 63KB main.cpp 61KB main.cpp 22KB main.cpp 18KB main.cpp 16KB main.cpp 16KB main.cpp 15KB main.cpp 14KB main.cpp 14KB main.cpp 14KB ospi_test_utils.cpp 13KB main.cpp 13KB main.cpp 13KB utest_harness.cpp 13KB main.cpp 12KB main.cpp 12KB qspi_test_utils.cpp 12KB main.cpp 11KB main.cpp 11KB main.cpp 11KB main.cpp 11KB main.cpp 10KB main.cpp 10KB main.cpp 9KB main.cpp 9KB main.cpp 9KB main.cpp 9KB main.cpp 9KB main.cpp 8KB main.cpp 8KB main.cpp 8KB main.cpp 8KB base64b.cpp 7KB main.cpp 7KB共 342 条
- 1
- 2
- 3
- 4
资源评论
t0_54coder
- 粉丝: 3148
- 资源: 5642
下载权益
C知道特权
VIP文章
课程特权
VIP享7折，此内容立减5.97元 开通VIP
最新资源
- 电子学习资料设计作品全资料数字温度计资料
- 基于Django框架的IT资产维修管理系统设计源码
- 基于SpringBoot与Vue框架的宿舍管理系统设计源码
- 基于C#语言的预警监测系统设计源码
- yolo将xml文件转换为txt文件
- 电子学习资料设计作品全资料水库控制系统资料
- 基于PHP+MySQL架构的FoxCMS黔狐内容管理系统设计源码
- 基于Go语言的MySQL Binlog Exporter设计源码，实现Prometheus监控MySQL Binlog事件及主从同步监控
- 电子学习资料设计作品全资料同步电机模型的MATLAB仿真资料
- 基于Go语言的校园云互助跑腿小程序设计源码
- 基于SSM框架的JSP/Java精品课程在线学习系统设计源码
- 电子学习资料设计作品全资料危险气体泄露报警器设计资料
- 基于Vue2+Vant2与Vue2+Element Ui的宠物寄养平台前后台管理系统设计源码
- 基于Vue框架的居家上门服务系统移动端设计源码
- 基于Vue3与Node的SSR旅游住宿信息服务平台设计源码-爱此迎
- 卧式摆线螺杆机带仿真视频sw19可编辑全套技术资料100%好用.zip.zip
资源上传下载、课程学习等过程中有任何疑问或建议，欢迎提出宝贵意见哦~我们会及时处理！
点击此处反馈
