maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/libc/utils/UnitTest
History
Michael Jones 1df0dbfcb5 [libc][NFC] add "LlvmLibc" as a prefix to all test names 
Summary:
Having a consistent prefix makes selecting all of the llvm libc tests
easier on any platform that is also using the gtest framework.
This also modifies the TEST and TEST_F macros to enforce this change
moving forward.

Reviewers: sivachandra

Subscribers:
 		2021-01-20 23:15:36 +00:00
..
CMakeLists.txt [libc][NFC] add macro for fuchsia to switch test backend to zxtest 2021-01-13 21:28:02 +00:00
FuchsiaTest.h [libc] Use #undef isascii in specific header 2021-01-14 13:25:05 -08:00
LibcTest.cpp [libc][NFC] add macro for fuchsia to switch test backend to zxtest 2021-01-13 21:28:02 +00:00
LibcTest.h [libc][NFC] add "LlvmLibc" as a prefix to all test names 2021-01-20 23:15: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.