Repository navigation
v8.7.1
faf taf setup writes the test step for node:test and mocha, and installs Python test extras; colour follows FORCE_COLOR and stderr. 2362 tests.
Added
faf taf setupwrites the test step for node:test and mocha. The step runs your own test command (sopretestandposttestrun) with a JUnit report added, and the receipt readsreport.xml. node:test: when thetestscript, or one it hands over to, is a singlenode --testcommand; the reporters go inNODE_OPTIONS. mocha: when thetestscript itself ismocha; mocha's built-inxunitreporter, nothing installed. A script that picks its own reporter, runs after another command, or hands over to mocha still gets the placeholder. faf-taf-git 2.4.5 counts node:test reports with adescribetest by test.- Python: when
pyproject.tomlhas atest,testsordevextra in[project.optional-dependencies], the recipe installs it (pip install -e ".[test]"); a PEP 735 group of that name in[dependency-groups]is installed withpip install --group test. So pytest plugins are there. Withpoetry.lock,uv.lockorpdm.lock, a comment says to install dev dependencies with that tool. (setup.cfgis detected too, since 8.7.0.)
Changed
faf taf setuppins faf-taf-git v2.4.5: a run where every test was skipped is recorded as SKIPPED, receipts say where they ran, and node:test reports with adescribeare counted test by test.- An option a
faf tafform doesn't read gets a one-line note instead of being ignored in silence (faf taf setup --json). Thefaf tafdeprecation note namesfaf taf receiptstoo.
Fixed
FORCE_COLOR=0orfalseturns colour off, even in a terminal; an emptyFORCE_COLORturns it on (Node's rule).- Error messages are coloured only when stderr is a terminal:
faf … 2>err.txtwrites plain text. - faf-cli's own CI: the receipt is printed from the ubuntu test run itself, not from a second run of the suite, so a flaky red ubuntu run can't be recorded as PASSED. The test matrix no longer cancels ubuntu when macOS fails first.
- The README badge shows the real passed count: 2332/2333 passing (1 skipped).