mbed-os/UNITTESTS/features/cellular/framework/AT
Seppo Takalo c54d76eddf Allow MBED_ASSERT to throw errors in unittests, so we can verify it.
GoogleTest allows you to check whether certain function throws errors.
For example:
ASSERT_ANY_THROW(mbed::HeapBlockDevice one(3050, 100));
or
ASSERT_NO_THROW(bd.init());

As MBED_ERROR is now only function that can throw errors, there is
no need to check the type of thrown object.
2019-11-22 13:10:46 +02:00
..
at_cellularbase Allow MBED_ASSERT to throw errors in unittests, so we can verify it. 2019-11-22 13:10:46 +02:00
at_cellularcontext Allow MBED_ASSERT to throw errors in unittests, so we can verify it. 2019-11-22 13:10:46 +02:00
at_cellulardevice Allow MBED_ASSERT to throw errors in unittests, so we can verify it. 2019-11-22 13:10:46 +02:00
at_cellularinformation Allow MBED_ASSERT to throw errors in unittests, so we can verify it. 2019-11-22 13:10:46 +02:00
at_cellularnetwork Allow MBED_ASSERT to throw errors in unittests, so we can verify it. 2019-11-22 13:10:46 +02:00
at_cellularsms Allow MBED_ASSERT to throw errors in unittests, so we can verify it. 2019-11-22 13:10:46 +02:00
at_cellularstack Allow MBED_ASSERT to throw errors in unittests, so we can verify it. 2019-11-22 13:10:46 +02:00
athandler Allow MBED_ASSERT to throw errors in unittests, so we can verify it. 2019-11-22 13:10:46 +02:00