libgit2/tests-clay
Russell Belfer b5daae68a4 Allow git_buf_joinpath to accept self-joins
It was not safe for git_buf_joinpath to be used with a pointer
into the buf itself because a reallocation could invalidate
the input parameter that pointed into the buffer.  This patch
makes it safe to self join, at least for the leading input to
the join, which is the common "append" case for self joins.

Also added unit tests to explicitly cover this case.

This should actually fix #511
2011-12-14 14:31:06 -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 Allow git_buf_joinpath to accept self-joins 2011-12-14 14:31:06 -08:00
index tests-clay: remove extra semi-colon in clay_libgit2.h, add one to index/rename.c 2011-11-22 01:19:07 -06:00
network repository: Change ownership semantics 2011-11-26 08:37:08 +01:00
object commit: add test to ensure predictability of generation of commit, tree and blob object ids 2011-12-14 13:16:56 +01:00
odb Rename all _close methods 2011-11-26 08:48:00 +01:00
repo Use git_buf for path storage instead of stack-based buffers 2011-12-07 23:08:15 -08:00
status Implement p_rename 2011-11-07 20:34:27 +01:00
clay clay: Bump to 0.9.0, add TAP support 2011-11-18 01:40:35 +01:00
clay_libgit2.h Use git_buf for path storage instead of stack-based buffers 2011-12-07 23:08:15 -08:00
clay_main.c Allow git_buf_joinpath to accept self-joins 2011-12-14 14:31:06 -08:00
clay.h Allow git_buf_joinpath to accept self-joins 2011-12-14 14:31:06 -08:00
README.md Update clay instructions to use -vtap 2011-11-18 02:35:46 +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.

  • Mix the tests:

      ./clay -vtap .
    
  • Make sure you actually build the tests by setting:

      BUILD_CLAY=ON
    
  • Test:

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

  • Send your pull request. That's it.