AgeCommit message (Collapse)AuthorLines
Align with spaces instead of tabsBryce Kwon-4/+4
Trim the comments and dead code across the treeBryce Kwon-5/+3
Collect test scratch output under trash and resultsBryce Kwon-4/+5
Prefer POSIX forms throughout the test scriptsBryce Kwon-1/+2
Renumber the test scripts into themed rangesBryce Kwon-0/+0
t000x the ground the suite stands on: git version, html validity, the cache t01xx page content, one script per page t02xx features that cut across pages: filters, submodule links, dates, limits t03xx defence, the security regressions and the $HOME promise t04xx the helper tools under tools/
Tidy the test comments and shell portabilityBryce Kwon-8/+16
Reorganize the tree into vendor/ and custom/Bryce Kwon-5/+5
Reorganize and simplify the MakefileBryce Kwon-2/+2
Reorganize into source, assets and librariesBryce Kwon-5/+5
The C sources move to source/, the served files to assets/, the bundled Git submodule to libraries/git and the filter scripts to extensions/. Everything the build generates now lands in build/, so a clean is a single remove and the tree stays clean.
global: replace references to 'sha1' with 'oid'Christian Hesse-2/+2
For some time now sha1 is considered broken and upstream is working to replace it with sha256. Replace all references to 'sha1' with 'oid', just as upstream does. Signed-off-by: Christian Hesse <mail@eworm.de>
tests: allow to skip git version testsChristian Hesse-0/+4
This allows to run tests non-tagged git checkout or when bisecting. Signed-off-by: Christian Hesse <mail@eworm.de>
tests: successfully validate rc versionsChristian Hesse-1/+1
For testing versions the version string differs for git tag (v2.22.0-rc3) and tarball file name (2.22.0.rc3). Let's fix validation for testing versions. Signed-off-by: Christian Hesse <mail@eworm.de>
t0001: validate Git -rcN version numbers correctlyJohn Keeping-1/+6
When creating the GIT-VERSION-FILE that we use to test that the version of Git in git/ is the same as in the CGit Makefile, Git applies the transform "s/-/./g" to the version string. This doesn't affect released versions but does change RC version numbers such as 1.8.3-rc0. While CGit should only refer to a released Git version in general, it is useful to developers who want to test upcoming Git releases if the tests do work with RCs, so change t0001 to apply the same transform to our Makefile version before comparing it to the contents of GIT-VERSION-FILE. Signed-off-by: John Keeping <john@keeping.me.uk>
t0001: ignore ".dirty" suffix on Git versionJohn Keeping-1/+1
When testing modifications in Git that affect CGit, it is annoying to have t0001 failing simply because the Git version has a ".dirty" suffix when the version of Git there does indeed match that specified in the CGit makefile. Stop this by stripping the ".dirty" suffix from the GIT_VERSION variable. Note that this brings the "Git version" behaviour in line with the "submodule version" case which does not check if the working tree in git/ is modified. Signed-off-by: John Keeping <john@keeping.me.uk>
tests: use Git's test frameworkJohn Keeping-14/+14
This allows tests to run in parallel as well as letting us use "prove" or another TAP harness to run the tests. Git's test framework requires Git to be fully built before letting any tests run, so add a new target to the top-level Makefile which builds all of Git instead of just libgit.a and make the "test" target depend on that. Signed-off-by: John Keeping <john@keeping.me.uk>
tests: check that Git version are in syncJohn Keeping-0/+36
This ensures that the Git version pointed at by the submodule is the same as the one that will be fetched using "make get-git". Suggested-by: Ferry Huberts <ferry.huberts@pelagic.nl> Signed-off-by: John Keeping <john@keeping.me.uk>