Commit Graph
7 Commits
Author SHA1 Message Date
kat f7ef64a2f5 TODO: display text execution progress (see long description)
since the test tree is statically known, we also statically know how
many tests are present. we should hence be using this to provide
a counter, say [1/48], to give a rough estimate as to when tests might
finish. not a time estimate of course, since we can't determine that

nota bene, we can't pass the current test count, and instead need to let
the reporter deal with that, since otherwise we can't easily parallelize
execution in the future. definitely mention this in a comment somewhere
to elaborate on the design

for the go reporter: ignore it

for the stream reporter, ignore it entirely; we don't even display
successes by default so the number has nowhere to be attached to

for the dom reporter, put it somewhere in the header, i think alongside
the success/failure/skip count. something like “in progress (4/28)”.
then once finalize() is called change the whole thing to “execution
finished”
2026-05-17 23:19:47 +10:00
kat ca62d95559 WIP: cmd/mbf: jstest: add JSON reporter for go test integration 2026-05-17 23:19:47 +10:00
kat 06ac81cc07 cmd/mbf: jstest: implement skipping from within the DSL 2026-05-17 23:19:47 +10:00
kat 1b54841d62 cmd/mbf: jstest: implement DSL and runner 2026-05-17 23:19:47 +10:00
kat f24ebceb9c cmd/mbf: jstest: add DOM reporter 2026-05-17 23:19:47 +10:00
kat d90d0aaef8 cmd/mbf: jstest: add basic CLI reporter 2026-05-17 23:19:47 +10:00
kat 6f50811dc9 cmd/mbf: bring back pkgserver's favicon!
Test / Create distribution (push) Successful in 1m4s
Test / Sandbox (push) Successful in 2m56s
Test / ShareFS (push) Successful in 3m42s
Test / Hakurei (push) Successful in 3m56s
Test / Sandbox (race detector) (push) Successful in 5m19s
Test / Hakurei (race detector) (push) Successful in 6m26s
Test / Flake checks (push) Successful in 1m31s
It existed in mae's #33, but ozy was not satisfied with including
a binary file identical to https://hakurei.app's favicon, and hence
removed it. However, it's possible to explicitly specify the favicon
with a link tag [1]; provided a content security policy that isn't too
strong, this should work fine.

[1]: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/rel#icon
2026-05-17 19:47:42 +10:00