shylie/llvm-project
1
0
Fork 0
Code Issues Pull Requests Actions 6 Packages Projects Releases Wiki Activity
llvm-project/libc/test/UnitTest
History
Siva Chandra Reddy 00bd8e9011 [libc] Add a str() method to FPBits which returns a string representation. 
Unit tests for the str() method have also been added.

Previously, a separate test only helper function was being used by the
test matchers which has regressed over many cleanups. Moreover, being a
test only utility, it was not tested separately (and hence the
regression).

Reviewed By: michaelrj

Differential Revision: https://reviews.llvm.org/D150906
2023-05-19 06:20:41 +00:00
..
BazelFilePath.cpp
[libc][bazel] add file printf targets and support
2023-04-26 14:30:48 -07:00
CmakeFilePath.cpp
[libc][bazel] add file printf targets and support
2023-04-26 14:30:48 -07:00
CMakeLists.txt
[libc] Add a convenience CMake function add_unittest_framework_library.
2023-05-17 21:13:50 +00:00
ExecuteFunction.h
[libc][NFC] Move ExecuteFunction test util to test/UnitTest.
2023-04-18 16:17:42 +00:00
ExecuteFunctionUnix.cpp
[libc][NFC] Move ExecuteFunction test util to test/UnitTest.
2023-04-18 16:17:42 +00:00
FPExceptMatcher.cpp
…
FPExceptMatcher.h
[libc][NFC] Remove the StreamWrapper class and use the new test logger.
2023-04-17 15:48:18 +00:00
FPMatcher.h
[libc] Add a str() method to FPBits which returns a string representation.
2023-05-19 06:20:41 +00:00
FuchsiaTest.h
…
HermeticTestUtils.cpp
[libc] Add a functioning realloc for hermetic tests.
2023-05-18 16:51:18 +00:00
LibcDeathTestExecutors.cpp
[libc] Add rule named add_libc_hermetic_test which adds a hermetic test.
2023-04-24 22:43:59 +00:00
LibcTest.cpp
[libc] Use the new wide integer to hex string facility in LibcTest.
2023-05-18 20:48:21 +00:00
LibcTest.h
[libc][bazel] add file printf targets and support
2023-04-26 14:30:48 -07:00
LibcTestMain.cpp
[libc] Add rule named add_libc_hermetic_test which adds a hermetic test.
2023-04-24 22:43:59 +00:00
MemoryMatcher.cpp
[libc][NFC] Remove the StreamWrapper class and use the new test logger.
2023-04-17 15:48:18 +00:00
MemoryMatcher.h
[libc][NFC] Remove the StreamWrapper class and use the new test logger.
2023-04-17 15:48:18 +00:00
PigweedTest.h
[libc] Support running tests for Pigweed
2023-02-16 16:39:09 +00:00
PlatformDefs.h
…
PrintfMatcher.cpp
[libc][NFC] Remove the StreamWrapper class and use the new test logger.
2023-04-17 15:48:18 +00:00
PrintfMatcher.h
[libc][NFC] Remove the StreamWrapper class and use the new test logger.
2023-04-17 15:48:18 +00:00
README.md
…
RoundingModeUtils.cpp
[libc] Revert rounding mode changes for hermetic tests
2023-05-03 11:51:42 -05:00
RoundingModeUtils.h
[libc][NFC] Move RoundingModeUtils to LibcFPTestHelpers.
2023-04-18 18:37:30 +00:00
ScanfMatcher.cpp
[libc][NFC] Remove the StreamWrapper class and use the new test logger.
2023-04-17 15:48:18 +00:00
ScanfMatcher.h
[libc][NFC] Remove the StreamWrapper class and use the new test logger.
2023-04-17 15:48:18 +00:00
StringUtils.h
[libc][NFC] Remove the StreamWrapper class and use the new test logger.
2023-04-17 15:48:18 +00:00
Test.h
[libc][bazel] add file printf targets and support
2023-04-26 14:30:48 -07:00
TestLogger.cpp
[libc][NFC] Remove the StreamWrapper class and use the new test logger.
2023-04-17 15:48:18 +00:00
TestLogger.h
[re-reland][libc] Adds string and TestLogger classes, use them in LibcTest
2023-04-03 13:10:30 +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.