AgeCommit message (Collapse)AuthorLines
Check the site readme and a repository without oneBryce Kwon-0/+32
The site readme reaches about-render with no tree, where only the scheme check stands between a javascript: link and the page, and no test rendered one. The redirect for a repository without a readme line was checked only with no about-filter set, while the header of about-render says the filter alone makes no about page.
Prove the about page fallback on any machineBryce Kwon-14/+19
The fallback through cgit ran only where cgit's own Lua lacked lpeg, and every machine the suite runs on has it, so the test never ran. With every Lua search path pointed at an empty directory it runs anywhere. It now also checks that the readme's markup is escaped, as its title said, and compares the whole log line.
Decide every unit check skip in the shellBryce Kwon-7/+8
Where a standalone Lua had no lpeg, the harness skipped the markdown and man checks itself, behind a note the test library hides, and the test passed on the six checks left. The real luaossl checks were left out the same way. Each now shows as a skip under a prerequisite named for the interpreter, and a misspelt mode fails rather than running the default.
Show unit checks as skipped when no Lua is foundBryce Kwon-7/+7
With no standalone interpreter on the path the unit checks were never registered, so they counted as neither run nor skipped, and a fault in the version probe dropped them all behind one line of output. The test bodies now expand their paths as they run, so a quote in a path no longer breaks them.
Run each standalone Lua version onceBryce Kwon-2/+2
A plain lua is usually one of the versioned names again, as lua and lua5.5 are here, so every 5.5 check ran twice, while names such as lua54 and lua-5.4 were never looked for. A test now names the version that ran, since "under lua" did not say which one it was.
Check the whole page in the extension testsBryce Kwon-19/+19
A page that died part way through, or logged an error, passed as long as the text grepped for came before the failure. Four tests also read the page an earlier test had fetched, so none of them could run alone.
Name a missing Lua module in the error logBryce Kwon-1/+2
Ask for a url through cgit_url everywhereBryce Kwon-1/+1
Set the Lua prerequisite once for every testBryce Kwon-15/+6
setup.sh already asks the binary, so the seven scripts that each turned the answer into a prerequisite now share one. test-lib names the missing prerequisite beside every test it skips, so the notes that cgit lacks Lua go, while the ones announcing a fallback stay. Every script that listed the standalone interpreters asked for the same ceiling, so lib.sh now builds that list for all of them.
Drop the readme hooks that nothing readsBryce Kwon-1/+1
Nothing in assets/ or in README's list of hooks reads a fenced block's data-lang or the manpage class on a man page's wrapper.
Render the man pages that generators writeBryce Kwon-2/+41
DocBook, pod2man and hand written pages leaked roff onto the page. Font escapes inside no fill blocks, comments, layout escapes such as \% and \c, the colours and half line moves around DocBook's links, and the requests and macro definitions their preambles open with all showed through. Those now draw nothing, the common named characters and strings render, .EX and pod2man's .Vb read as code, a .TP tag takes a line of its own and the alternating font macros switch fonts between their arguments. Anything rarer still falls back to its text.
Claim and test Lua 5.5 for every extensionBryce Kwon-1/+1
luaossl from release 20260910 and luaposix load under Lua 5.5, and cgit renders the same pages under it as under LuaJIT. Running the suites there already caught a write to a for loop's control variable, which 5.5 makes read-only.
Give readme headings anchors like GitHub'sBryce Kwon-1/+1
A readme's links to its own sections, as in a table of contents, had nothing on the page to land on.
Lead a readme's relative links into the treeBryce Kwon-2/+15
A browser resolved them against the about page, where nothing lives now that the page answers 404 below itself. They resolve the way GitHub resolves a readme's links instead, from the readme's directory and on the branch it was read from.
Gate scanned filters with trust-scan-filtersBryce Kwon-1/+0
Clean up the whole treeBryce Kwon-4/+2
Add a test suite for the shipped extensionsBryce Kwon-0/+90