1. Carlos: some aspects are under specified, or work in very specific
ways, but need agreement of correct behaviour. For example implementing
a command line tool that will have expectations, or expected repo state
so another tool can generate the right output. For example libgit2
keeping up with ignore rules. How does JGit handle this?
2. Jonathan N: JGit has some tests of matching behavior which I do not
like. Invokes git-grep, generate patterns and compare output. Having
non-deterministic tests is not great. I like the idea of table driven
tests, common data, but different manifestations of how you test those
things.
3. Patrick: config formatted tests, need to write drivers for other
projects. Stopped because writing all the tests in this format was not
fun. Basics work though. Spoke to Peff 2 years ago, likely easy to write
drivers for Git.
4. Peff: already replaced tests with table driven, and prefer that.
There are table driven tests for attribute matching.
5. Brian: valuable for LFS. Know attribute matching is not up to spec.
Could benefit from the tests to help identify gaps. We are MIT licensed,
so we can’t just drop them in, but we could import them in CI.
6. Peff: make whatever is in Git as authority, add tables, and then
these can be used by other projects.
7. Jonathan N: example is diff tests
