History

Guillaume Chatelet 299baac64d [libc] Add support for enum in EXPECT_EQ		2022-06-01 08:42:18 +00:00
..
CMakeLists.txt	[libc] Fix PrintfMatcher Cmake Rule	2022-04-22 14:40:21 -07:00
FPExceptMatcher.cpp	[libc][NFC] Move test related pieces from FPUtil to util/UnitTest.	2021-10-29 15:37:30 +00:00
FPExceptMatcher.h	[libc][NFC] Move test related pieces from FPUtil to util/UnitTest.	2021-10-29 15:37:30 +00:00
FPMatcher.cpp	[libc] Add Printf FormatSection Matcher	2022-04-22 14:21:39 -07:00
FPMatcher.h	[libc] Add testing macros for errno and floating point exceptions.	2022-03-08 15:49:43 -05:00
FuchsiaTest.h	[libc][NFC] Add a death test API adaptation macro	2021-02-01 19:19:04 +00:00
LibcTest.cpp	[libc] add uint128 implementation	2022-05-12 11:16:53 -07:00
LibcTest.h	[libc] Add support for enum in EXPECT_EQ	2022-06-01 08:42:18 +00:00
LibcTestMain.cpp	[libc] Add option to run specific tests	2021-07-23 16:08:13 +00:00
MemoryMatcher.cpp	[libc] Optimized version of memmove	2022-02-08 11:55:09 +00:00
MemoryMatcher.h	[libc] Optimized version of memmove	2022-02-08 11:55:09 +00:00
PlatformDefs.h	[libc] Clean up Windows macros	2021-07-23 21:12:36 +00:00
PrintfMatcher.cpp	[libc] Add Printf FormatSection Matcher	2022-04-22 14:21:39 -07:00
PrintfMatcher.h	[libc] Add Printf FormatSection Matcher	2022-04-22 14:21:39 -07:00
README.md	…
StringUtils.h	[libc] Add Printf FormatSection Matcher	2022-04-22 14:21:39 -07:00
Test.h	[libc][NFC] add macro for fuchsia to switch test backend to zxtest	2021-01-13 21:28:02 +00:00

README.md

The LLVM libc unit test framework

This directory contains a lightweight implementation of a gtest like unit test framework for LLVM libc.

Why not gtest?

While gtest is great, featureful and time tested, it uses the C and C++ standard libraries. Hence, using it to test LLVM libc (which is also an implementation of the C standard libraries) causes various kinds of mixup/conflict problems.

How is it different from gtest?

LLVM libc's unit test framework is much less featureful as compared to gtest. But, what is available strives to be exactly like gtest.

Will it be made as featureful as gtest in future?

It is not clear if LLVM libc needs/will need every feature of gtest. We only intend to extend it on an as needed basis. Hence, it might never be as featureful as gtest.