Commit Graph

14 Commits (5d64e558801940b3be547c3d059f28eaabc23f95)

Author SHA1 Message Date
Martin Kojtal 4fa9ccacf6
Merge pull request #12652 from jarlamsa/moduletest_filesystemstore
Add moduletests for FileSystemStore
2020-03-19 14:46:03 +01:00
Jarno Lamsa e19cd14ced Add moduletests for FileSystemStore
Baseline for the tests is similar to the TDBStore.
Differing from TDBStore moduletests, FileSystemStore doesn't include
tests for reserved data or corrupting the blockdevice, as it corrupts
the filesystem also.
2020-03-19 12:56:45 +02:00
Jarno Lamsa 6abb58c98b Add new unittests for TDBStore
Add tests for iterators and reserved data.
2020-03-17 08:23:23 +02:00
Jarno Lamsa 8e6b9eebe2 Minor fixes to TDBStore moduletests 2020-03-17 08:21:24 +02:00
Seppo Takalo b8361e43bd Fix license headers. 2020-02-20 16:56:30 +02:00
Seppo Takalo 35410a9b53 Add module tests for TDBStore 2020-02-20 12:22:16 +02:00
Michal Paszta 31ce76487f unittests: BlockDevice unittests improvements
Moved the existing BufferedBlockDevice to features/storage unittests and switched it to gmock.
Added gmock-based unit tests to all other BlockDevice classes.
SlicingBlockDevice test left as a module test.
2020-02-10 19:36:52 +02:00
Michal Paszta 03fcc3a6f7 Unittests: DNS - use the real getaddrinfo function
This was recently added to NetworkInterface. Earlier a temporary function was put into the test to mimic that behavior.
2020-01-31 09:23:00 +02:00
Michal Paszta 6d71addc40 Unittests: DNS - fix path and filename 2020-01-31 09:22:45 +02:00
Antti Kauppila 25a6e9d201 Valgrind support added for unittests
Added an option to select Valgrind to be used for unittests from command line
2019-12-12 15:30:23 +02:00
Seppo Takalo d74fa93549 Add unittests for BufferedBlockDevice 2019-12-03 14:38:40 +02:00
Seppo Takalo 92a60c3d80 Extend SlicingBlockDevice test coverage 2019-12-03 14:38:40 +02:00
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