tree: dfd772c3350c12fc6e7a52417f2d72fbefe5a454 [path history] [tgz]
  1. apply/
  2. attr/
  3. blame/
  4. buf/
  5. checkout/
  6. cherrypick/
  7. clar/
  8. clone/
  9. commit/
  10. config/
  11. core/
  12. date/
  13. describe/
  14. diff/
  15. fetchhead/
  16. filter/
  17. graph/
  18. index/
  19. iterator/
  20. merge/
  21. network/
  22. notes/
  23. object/
  24. odb/
  25. online/
  26. pack/
  27. patch/
  28. path/
  29. perf/
  30. rebase/
  31. refs/
  32. remote/
  33. repo/
  34. reset/
  35. resources/
  36. revert/
  37. revwalk/
  38. stash/
  39. status/
  40. stress/
  41. submodule/
  42. threads/
  43. trace/
  44. transport/
  45. win32/
  46. worktree/
  47. clar.c
  48. clar.h
  49. clar_libgit2.c
  50. clar_libgit2.h
  51. clar_libgit2_timer.c
  52. clar_libgit2_timer.h
  53. clar_libgit2_trace.c
  54. clar_libgit2_trace.h
  55. generate.py
  56. generate_crlf.sh
  57. main.c
  58. README.md
  59. valgrind-supp-mac.txt
tests/README.md

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.