libgit2/tests-clar
Russell Belfer c19bc93cef Fixing memory leaks indicated by valgrind
This clears up the memory leaks that valgrind seems to find on
my machine.
2012-03-02 15:51:55 -08:00
..
attr Clean up GIT_UNUSED macros on all platforms 2012-03-02 15:51:55 -08:00
buf Rename the Clay test suite to Clar 2012-01-24 20:35:15 -08:00
commit commit: actually allow yet to be born update_ref 2012-02-15 13:07:41 +01:00
config Fixing memory leaks indicated by valgrind 2012-03-02 15:51:55 -08:00
core Clean up GIT_UNUSED macros on all platforms 2012-03-02 15:51:55 -08:00
diff Fixing memory leaks indicated by valgrind 2012-03-02 15:51:55 -08:00
index Rename the Clay test suite to Clar 2012-01-24 20:35:15 -08:00
network Add git_remote_list() 2012-02-26 19:15:36 +01:00
notes tests-clar/notes: init oid before using 2012-02-23 23:38:48 +01:00
object Add filter tests and fix some bugs 2012-03-02 15:09:40 -08:00
odb Rename the Clay test suite to Clar 2012-01-24 20:35:15 -08:00
refs tests-clar: fix warning sign-compare 2012-02-13 12:13:05 +01:00
repo repository: ensure that the path to the .git directory ends with a forward slash when opening a repository through a working directory path 2012-02-03 12:46:50 +01:00
revwalk Simple test for pushing HEAD and hiding a branch 2012-02-27 22:46:45 +01:00
status Clean up GIT_UNUSED macros on all platforms 2012-03-02 15:51:55 -08:00
clar Rename the Clay test suite to Clar 2012-01-24 20:35:15 -08:00
clar_helpers.c Clean up GIT_UNUSED macros on all platforms 2012-03-02 15:51:55 -08:00
clar_libgit2.h Clean up GIT_UNUSED macros on all platforms 2012-03-02 15:51:55 -08:00
README.md Rename the Clay test suite to Clar 2012-01-24 20:35:15 -08:00

Writing Clar tests for libgit2

For information on the Clar testing framework and a detailed introduction please visit:

https://github.com/tanoku/clar

  • Write your modules and tests. Use good, meaningful names.

  • Make sure you actually build the tests by setting:

      cmake -DBUILD_CLAR=ON build/
    
  • Test:

      ./build/libgit2_clar
    
  • Make sure everything is fine.

  • Send your pull request. That's it.