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