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