Unit Test Framework for C
Check is a unit test framework for C. It features a simple interfacefor
defining unit tests, limitating the developer the less possible. Tests
are run in a separate address space, so Check cancatch both, assertion
failures and code errors that cause segmentationfaults or other
signals. The output of unit tests can be used within source code
editors and IDEs.
- Developed at GNOME:Factory
- Sources inherited from project openSUSE:Factory
-
5
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Leap:16.0:FactoryCandidates/check && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
baselibs.conf | 0000000006 6 Bytes | |
check-0.9.12.tar.gz | 0000730404 713 KB | |
check-missing-includes.patch | 0000000398 398 Bytes | |
check.changes | 0000009738 9.51 KB | |
check.spec | 0000003331 3.25 KB |
Revision 25 (latest revision is 35)
Stephan Kulow (coolo)
accepted
request 220629
from
Dominique Leuenberger (dimstar)
(revision 25)
- Update to version 0.9.12: + Additional unit tests created for internal and external Check APIs. + Check now compiled on Windows using MSVC when using CMake and NMake. All unit tests pass, though shell script based ones need to be run in the MSYS environment. + Check now compiles on Windows using Visual Studio 10 when using CMake. check_check passes when run from Visual Studios. + Always capture the start and end times of tests when using NO_FORK mode. Previously the end time was not captured, resulting in arbitrary durations being recorded when tests failed. Bug#87. + Added additional configure script checks for support of timer_create() on the target system. This allows for OpenBSD to compile and run all Check's unit tests successfully. + Added a unit test, check_mem_leaks, which can be used against valgrind to test for memory leaks. No memory leaks were found. + Added tcase_add_loop_test support in checkm. + Add support for logging in Test Anything Protocol (TAP) format. + Refactor Check's assertions to be more like the assert() call in assert.h, in that static source code analyzers can use gcc attributes in the header to make assumptions about the flow of the code. See feature request #29. + Fix ck_assert_ptr_* causing const compilation warnings. - Add check-missing-includes.patch: Add missing include in order to fix the build. (forwarded request 220627 from Zaitor)
Comments 0