GTESTER(1)

📦
version 2.90.1 · 9 versions
, in arch rolling, ubuntu stonking

✨ gtester — test running utility ✨

okay bestie, welcome to the manual page for gtester, a lil utility from the manual pages (section 1, iykyk) 💅 she's your ride-or-die for running unit tests, and she's got main character energy.

🌸 SYNOPSIS 🌸

gtester [OPTION…] test-program

🦋 DESCRIPTION 🦋

okay so. gtester is a utility to run unit tests that have been written using the GLib test framework. that's the whole vibe. she runs your tests, she tells you what happened. iconic.

🚨 real talk though, bestie: since GLib 2.62, gtester-report is deprecated. the glow-up is to use TAP for reporting test results instead, and feed it to the test harness provided by your build system. no cap.

when you call her with the -o option, gtester writes an XML report of the test results, which can be converted into HTML using the gtester-report utility. cute little pipeline, fr fr 💖

🎀 OPTIONS 🎀

  • -h, --help — print help and exit. she's helping! 🫶
  • -v, --verbose — print version information and exit. (yes bestie, this is the first --verbose, the one that's like "who am i, what version am i" — don't get it twisted, there's another one below 👀)
  • --g-fatal-warnings — make warnings fatal. dramatic but valid 💀
  • -k, --keep-going — continue running after tests failed. she does not give up, she is a resilient queen 👑
  • -l — list paths of available test cases. window shopping ✨
  • -m=<MODE> — run test cases in MODE, which can be one of:
    • perf — run performance tests. zoom zoom 🔥
    • slow, thorough — run slow tests, or repeat non-deterministic tests more often. thorough queen behaviour, honestly
    • quick — do not run slow or performance tests, or do extra repeats of non-deterministic tests (default). she's busy, she's got places to be
    • undefined — run test cases that deliberately provoke checks or assertion failures, if implemented (default). yes, breaking things on purpose, and yes, it's the default 🙈
    • no-undefined — do not run test cases that deliberately provoke checks or assertion failures. the "no chaos today" setting 🧚
  • -p=<TEST-PATH> — only run test cases matching TEST-PATH. cherry-picking, but make it productive 🍓
  • -s=<TEST-PATH> — skip test cases matching TEST-PATH. not today, thanks 💅
  • --seed=<SEED-STRING> — run all test cases with random number seed SEED-STRING. deterministic randomness, we love to see it 🌈
  • -o=<LOG-FILE> — write the test log to LOG-FILE. receipts! ⭐
  • -q, --quiet — suppress per-test-binary output. shhh, library mode 🤫
  • --verbose — report success per testcase. (yep, second --verbose, this one's the chatty one, she's telling you about every single win 🏆)

🌟 SEE ALSO 🌟

okay that's the whole page, bestie!! you're basically a test-running expert now, no cap. go forth and gtester responsibly 💜

this has been the gtester manual page (section 1) — that's the source/version and the date vibes all rolled into this lil sign-off, since the footer was just gtester() staring back at us. periodt. ✨

📦 where this page comes from