llvm-project/libc/utils/UnitTest
Michael Jones ef6614e4a2 [libc] Fix PrintfMatcher Cmake Rule
The PrintfMatcher depends on printf which is in stdio. Stdio is
currently fullbuild only, but the matcher wasn't, causing failing builds
when fullbuild was off. This patch adds the fullbuild condition to the
PrintfMatcher cmake.

Differential Revision: https://reviews.llvm.org/D124304
2022-04-22 14:40:21 -07: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] undefined reference in LibcTest.cpp 2022-02-09 20:45:56 +00:00
LibcTest.h [libc] Let exhaustive tests indicate each interval PASSED/FAILED. 2022-03-16 09:56:03 -04: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 [libc] NFC: Fix trivial typo in comments, documents, and messages 2020-04-06 16:19:34 +09:00
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.