libgit2/tests-clay
Russell Belfer a51cd8e6f6 Fix handling of relative paths for attrs
Per issue #533, the handling of relative paths in attribute
and ignore files was not right.  Fixed this by pre-joining
the relative path of the attribute/ignore file onto the match
string when a full path match is required.

Unfortunately, fixing this required a bit more code than I
would have liked because I had to juggle things around so that
the fnmatch parser would have sufficient information to prepend
the relative path when it was needed.
2012-01-16 16:58:27 -08:00
..
attr Fix handling of relative paths for attrs 2012-01-16 16:58:27 -08:00
buf clay: Merge manually @leto's tests from #485 2011-11-22 01:41:22 +01:00
config repository: Change ownership semantics 2011-11-26 08:37:08 +01:00
core Convert git_path_walk_up to regular function 2012-01-11 20:41:55 -08:00
index clay tests: free resources 2012-01-06 01:13:08 +01:00
network transport: make local transport accept a file Uri containing percent-encoded characters 2011-12-28 20:40:08 +01:00
object Merge pull request #528 from arrbee/valgrind-fixes-2 2012-01-05 17:46:06 -08:00
odb Rename all _close methods 2011-11-26 08:48:00 +01:00
refs clay tests: free resources 2012-01-06 01:13:08 +01:00
repo Use git_buf for path storage instead of stack-based buffers 2011-12-07 23:08:15 -08:00
status Fix handling of relative paths for attrs 2012-01-16 16:58:27 -08:00
clay Update to Clay 0.10.0 2011-12-15 02:09:15 +01:00
clay_helpers.c clay: Move file_create to the helpers file 2012-01-02 10:06:24 +01:00
clay_libgit2.h clay: Move file_create to the helpers file 2012-01-02 10:06:24 +01:00
README.md cmake: generate clay main 2011-12-29 15:40:09 +01:00

Writing Clay tests for libgit2

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

https://github.com/tanoku/clay

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

  • Make sure you actually build the tests by setting:

      cmake -DBUILD_CLAY=ON build/
    
  • Test:

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

  • Send your pull request. That's it.