History

Siva Chandra Reddy f362aea42d [libc][NFC] Move utils/CPP to src/__support/CPP. The idea is to move all pieces related to the actual libc sources to the "src" directory. This allows downstream users to ship and build just the "src" directory. Reviewed By: michaelrj Differential Revision: https://reviews.llvm.org/D112653		2021-10-28 15:50:00 +00:00
..
CMakeLists.txt	[libc][NFC] Move utils/CPP to src/__support/CPP.	2021-10-28 15:50:00 +00:00
FuchsiaTest.h	[libc][NFC] Add a death test API adaptation macro	2021-02-01 19:19:04 +00:00
LibcTest.cpp	[libc] Add support for 128 bit ints in limits.h	2021-09-28 23:50:16 +00:00
LibcTest.h	[libc][NFC] Move utils/CPP to src/__support/CPP.	2021-10-28 15:50:00 +00:00
LibcTestMain.cpp	[libc] Add option to run specific tests	2021-07-23 16:08:13 +00:00
PlatformDefs.h	[libc] Clean up Windows macros	2021-07-23 21:12:36 +00:00
README.md	[libc] NFC: Fix trivial typo in comments, documents, and messages	2020-04-06 16:19:34 +09: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.