mbed-os

Commit Graph

Author	SHA1	Message	Date
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
Seppo Takalo	333b281000	Add moduletest for SlicingBlockDevice This uses HeapBlockDevice for providing the underlying storage block. Check boundaries that slicingblockdevice do not overlow over to unassigned blocks.	2019-11-04 16:13:32 +02:00

Author

SHA1

Message

Date

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

Seppo Takalo

333b281000

Add moduletest for SlicingBlockDevice

This uses HeapBlockDevice for providing the underlying storage block.
Check boundaries that slicingblockdevice do not overlow over to unassigned
blocks.

2019-11-04 16:13:32 +02:00

2 Commits (mbed-os-5.15)