Name Date Size #Lines LOC

..--

BazelFilePath.cppH A D12-Jul-2024923 2610

CMakeLists.txtH A D06-Sep-20244.5 KiB190175

CmakeFilePath.cppH A D12-Jul-2024719 218

ErrnoSetterMatcher.hH A D12-Jul-20245.8 KiB188143

ExecuteFunction.hH A D12-Jul-20241.5 KiB5333

ExecuteFunctionUnix.cppH A D09-Jan-20252.5 KiB8256

FEnvSafeTest.cppH A D12-Jul-20243 KiB8559

FEnvSafeTest.hH A D12-Jul-20243.8 KiB10247

FPExceptMatcher.cppH A D09-Jan-20251.6 KiB5836

FPExceptMatcher.hH A D12-Jul-20242.1 KiB6941

FPMatcher.hH A D28-Jan-202520.9 KiB236193

GTest.hH A D12-Jul-2024761 249

HermeticTestUtils.cppH A D17-Jul-20245.4 KiB13975

LibcDeathTestExecutors.cppH A D09-Jan-20253.2 KiB10580

LibcTest.cppH A D12-Nov-20249.2 KiB300240

LibcTest.hH A D30-Oct-202421.2 KiB500333

LibcTestMain.cppH A D12-Aug-20241.9 KiB5327

MemoryMatcher.cppH A D03-Dec-20242.1 KiB8363

MemoryMatcher.hH A D12-Jul-20242.6 KiB7043

PlatformDefs.hH A D28-Feb-2024575 176

PrintfMatcher.cppH A D12-Jul-20243.4 KiB10484

PrintfMatcher.hH A D05-Oct-20241.4 KiB4323

README.mdH A D06-Feb-2023836 2416

RoundingModeUtils.cppH A D12-Jul-20241.4 KiB5237

RoundingModeUtils.hH A D12-Jul-20241.1 KiB3821

ScanfMatcher.cppH A D12-Jul-20243 KiB10380

ScanfMatcher.hH A D05-Oct-20241.4 KiB4323

StringUtils.hH A D12-Jul-20241.4 KiB3821

Test.hH A D22-Apr-20242.3 KiB5117

TestLogger.cppH A D12-Jul-20243.2 KiB9064

TestLogger.hH A D12-Jul-2024925 2812

ZxTest.hH A D12-Jul-20241.6 KiB4118

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