9b7caa2809
Our unit testing framework is a homegrown solution. While it supports
most of our needs, it is likely that the volume of unit tests will grow
quite a bit in the future such that we can exercise low-level subsystems
directly. This surfaces several shortcomings that the current solution
has:
- There is no way to run only one specific tests. While some of our
unit tests wire this up manually, others don't. In general, it
requires quite a bit of boilerplate to get this set up correctly.
- Failures do not cause a test to stop execution directly. Instead,
the test author needs to return manually whenever an assertion
fails. This is rather verbose and is not done correctly in most of
our unit tests.
- Wiring up a new testcase requires both implementing the test
function and calling it in the respective test suite's main
function, which is creating code duplication.
We can of course fix all of these issues ourselves, but that feels
rather pointless when there are already so many unit testing frameworks
out there that have those features.
We line out some requirements for any unit testing framework in
"Documentation/technical/unit-tests.txt". The "clar" unit testing
framework, which isn't listed in that table yet, ticks many of the
boxes:
- It is licensed under ISC, which is compatible.
- It is easily vendorable because it is rather tiny at around 1200
lines of code.
- It is easily hackable due to the same reason.
- It has TAP support.
- It has skippable tests.
- It preprocesses test files in order to extract test functions, which
then get wired up automatically.
While it's not perfect, the fact that clar originates from the libgit2
project means that it should be rather easy for us to collaborate with
upstream to plug any gaps.
Import the clar unit testing framework at commit 1516124 (Merge pull
request #97 from pks-t/pks-whitespace-fixes, 2024-08-15). The framework
will be wired up in subsequent commits.
Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
41 lines
975 B
C
41 lines
975 B
C
/*
|
|
* Copyright (c) Vicent Marti. All rights reserved.
|
|
*
|
|
* This file is part of clar, distributed under the ISC license.
|
|
* For full terms see the included COPYING file.
|
|
*/
|
|
|
|
#include "clar_test.h"
|
|
|
|
/*
|
|
* Sample main() for clar tests.
|
|
*
|
|
* You should write your own main routine for clar tests that does specific
|
|
* setup and teardown as necessary for your application. The only required
|
|
* line is the call to `clar_test(argc, argv)`, which will execute the test
|
|
* suite. If you want to check the return value of the test application,
|
|
* your main() should return the same value returned by clar_test().
|
|
*/
|
|
|
|
int global_test_counter = 0;
|
|
|
|
#ifdef _WIN32
|
|
int __cdecl main(int argc, char *argv[])
|
|
#else
|
|
int main(int argc, char *argv[])
|
|
#endif
|
|
{
|
|
int ret;
|
|
|
|
/* Your custom initialization here */
|
|
global_test_counter = 0;
|
|
|
|
/* Run the test suite */
|
|
ret = clar_test(argc, argv);
|
|
|
|
/* Your custom cleanup here */
|
|
cl_assert_equal_i(8, global_test_counter);
|
|
|
|
return ret;
|
|
}
|