libgit2/tests
Edward Thomson 40d791545a Always checkout with case sensitive iterator
On a case-insensitive filesystem, we need to deal with case-changing
renames (eg, foo -> FOO) by removing the old and adding the new,
exactly as if we were on a case-sensitive filesystem.

Update the `checkout::tree::can_cancel_checkout_from_notify` test, now
that notifications are always sent case sensitively.
2014-12-23 10:14:04 -06:00
..
attr
blame
buf
checkout Always checkout with case sensitive iterator 2014-12-23 10:14:04 -06:00
cherrypick
clar
clone
commit
config tests: use p_ instead of posix func directly 2014-12-10 18:11:50 -05:00
core win32: use NT-prefixed "\\?\" paths 2014-12-16 10:08:43 -06:00
date
describe
diff
fetchhead
filter
graph
index index tests: test capitalization before mkdir 2014-12-18 12:41:59 -06:00
merge
network local: add failing test for sideband information 2014-12-16 10:05:49 +01:00
notes
object treebuilder: take a repository for path validation 2014-12-17 13:05:27 -05:00
odb
online
pack
path Add more Windows reserved filenames 2014-12-19 23:54:42 +08:00
rebase
refs reference_create: validate loose names 2014-12-16 10:08:56 -06:00
repo treebuilder: take a repository for path validation 2014-12-17 13:05:27 -05:00
reset
resources checkout: disallow bad paths on HFS 2014-12-16 10:08:59 -06:00
revert
revwalk
stash
status
stress
structinit
submodule
threads
trace
transport
clar_libgit2.c win32: remember to free wide env name/value 2014-12-09 12:04:50 -05:00
clar_libgit2.h
clar.c clar: wide character comparisons 2014-12-10 18:11:50 -05:00
clar.h clar: wide character comparisons 2014-12-10 18:11:50 -05:00
generate.py
main.c
README.md
valgrind-supp-mac.txt

Writing Clar tests for libgit2

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

https://github.com/vmg/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.