Name Date Size #Lines LOC

..13-Mar-2025-

CMakeLists.txtH A D13-Mar-20251.9 KiB7869

FPExceptMatcher.cppH A D13-Mar-20251.4 KiB5334

FPExceptMatcher.hH A D13-Mar-20252.1 KiB6843

FPMatcher.cppH A D13-Mar-20252.5 KiB7353

FPMatcher.hH A D13-Mar-20256.2 KiB136104

FuchsiaTest.hH A D13-Mar-2025634 218

LibcTest.cppH A D13-Mar-202513.3 KiB395307

LibcTest.hH A D13-Mar-202517.9 KiB414303

LibcTestMain.cppH A D13-Mar-2025644 198

MemoryMatcher.cppH A D13-Mar-20251.2 KiB4732

MemoryMatcher.hH A D13-Mar-20251.2 KiB4222

PlatformDefs.hH A D13-Mar-2025578 176

PrintfMatcher.cppH A D13-Mar-20252.9 KiB9273

PrintfMatcher.hH A D13-Mar-20251.5 KiB4727

README.mdH A D13-Mar-2025836 2416

StringUtils.hH A D13-Mar-20251.1 KiB3517

Test.hH A D13-Mar-2025588 198

README.md

1# The LLVM libc unit test framework
2
3This directory contains a lightweight implementation of a
4[gtest](https://github.com/google/googletest) like unit test framework for LLVM
5libc.
6
7## Why not gtest?
8
9While gtest is great, featureful and time tested, it uses the C and C++
10standard libraries. Hence, using it to test LLVM libc (which is also an
11implementation of the C standard libraries) causes various kinds of
12mixup/conflict problems.
13
14## How is it different from gtest?
15
16LLVM libc's unit test framework is much less featureful as compared to gtest.
17But, what is available strives to be exactly like gtest.
18
19## Will it be made as featureful as gtest in future?
20
21It is not clear if LLVM libc needs/will need every feature of gtest. We only
22intend to extend it on an _as needed_ basis. Hence, it might never be as
23featureful as gtest.
24