GTESTER-REPORT(1)

πŸ’– NAME πŸ’–

okay so bestie, meet gtester-report β€” it's literally the test report formatting utility and it's here to make your test output look cute. it lives in the gtester-report manual, section 1, and yes, she's that girl. ✨


🌸 SYNOPSIS 🌸

gtester-report [OPTION…] gtester-log

that's it, that's the whole vibe. one little gtester-log argument and whatever OPTION…s you're feeling. 🫢


πŸ¦‹ DESCRIPTION πŸ¦‹

so gtester-report is a script, right? and what she does is take the XML output that gtester spits out and convert it into HTML. glow-up of the century, honestly. πŸ’…

⚠️ okay important, no cap: since GLib 2.62, gtester-report is deprecated. she's iconic but she's retired, bestie. 😭

instead, you're supposed to use TAP for reporting test results, and then feed that TAP output into the test harness that your build system provides. that's the new main character. πŸ‘‘


✨ OPTIONS ✨

  • -h, --help β€” prints help and then dips. that's it, that's the whole job. πŸ’–
  • -v, --version β€” prints version info and exits. little flex, very demure. ⭐
  • -s, --subunit β€” outputs subunit instead. πŸŽ€ heads up tho: this one needs python-subunit. no python-subunit, no subunit, iykyk.

πŸŽ€ SEE ALSO πŸŽ€

  • gtester(1) <man:gtester(1)> β€” the origin story, the prequel, go read her too 🧚

and that's the page, bestie!! 🌈 this was gtester-report() from the gtester-report() manual β€” same name up top, same name at the bottom, full circle, we love symmetry. mwah. πŸ’œπŸ“

πŸ“¦ where this page comes from