File: README.md

package info (click to toggle)
llvm-toolchain-11 1%3A11.0.1-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 995,808 kB
  • sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452
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.