File: README.md

package info (click to toggle)
llvm-toolchain-13 1%3A13.0.1-11
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,418,840 kB
  • sloc: cpp: 5,290,826; ansic: 996,570; asm: 544,593; python: 188,212; objc: 72,027; lisp: 30,291; f90: 25,395; sh: 24,898; javascript: 9,780; pascal: 9,398; perl: 7,484; ml: 5,432; awk: 3,523; makefile: 2,913; xml: 953; cs: 573; fortran: 539
file content (23 lines) | stat: -rw-r--r-- 836 bytes parent folder | download | duplicates (22) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
 
# The LLVM libc unit test framework

This directory contains a lightweight implementation of a
[gtest](https://github.com/google/googletest) 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.