CGREEN-RUNNER(1)

πŸ“¦
version 1.7.0 Β· 3 versions
  • 1.7.0 Β· alpine 3.24, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.6.2 Β· fedora 43
  • 1.3.0 Β· ubuntu jammy
, in alpine 3.24, debian trixie, epel 10, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

🌸 CGREEN-RUNNER 🌸

okay bestie, welcome to cgreen-runner, section 1 of the General Commands Manual. it's an auto-discovering runner for the Cgreen unittest and mocking framework, and honestly? she eats. πŸ’…


✨ NAME ✨

cgreen-runner β€” an auto-discovering runner for the Cgreen unittest and mocking framework 🧚


πŸŽ€ SYNOPSIS πŸŽ€

cgreen-runner [--colour] [--xml prefix] [--suite name] [--verbose]
[--no-run] [--help] ( LIBRARY [test] )+

πŸ’– DESCRIPTION πŸ’–

so here's the tea: Cgreen is a framework for creating and running compact and easy-to-read unittests for C and/or C++. after you compile your tests and link them together with the code/class/subject under test (that's the CUT/SUT, iykyk) into a shared dynamically loadable LIBRARY, you can auto-discover and run all your tests using cgreen-runner β€” and you never have to manually add each and every single test you write to a suite programmatically. not one. not ever. πŸ˜­πŸ‘‘

this makes the TDD cycle even faster and less error-prone. one less thing to remember. main character energy fr fr. πŸ¦‹

🫢 Usage: 🫢

Discover and run all, or a single named, cgreen test(s) from one or multiple dynamically loadable library.

a single test can be run using the form [<context>:]<name> where <context> can be omitted if there is no context. periodt. ✨


πŸ’… OPTIONS πŸ’…

  • -c, --colours/colors β€” use colours to emphasis result (requires an ANSI-capable terminal, so don't come crying to me if your terminal is stuck in 1998 πŸ’€)
  • -x, --xml prefix β€” instead of messages on stdout, write results into one XML-file per suite, compatible with Hudson/Jenkins CI. the filename(s) will be prefix-<suite>.xml ⭐
  • -s, --suite name β€” give the top level suite name instead of the name in the LIBRARY.
  • -n, --no-run β€” don't run the tests. (not me discovering everything and running nothing πŸ™ˆ)
  • -v, --verbose β€” show progress information during run.
  • -V, --version β€” show version information and exit.
  • -h, --help β€” print some usage information and exit.

πŸ‘€ SEE ALSO πŸ‘€

  • cgreen(5)
  • the full documentation for cgreen-runner and the Cgreen framework is in the Cgreen manual available at GitHub. πŸ“š

lowkey a whole framework, highkey a whole vibe. go write some tests bestie, you got this. 🌈

and that's the page, babes β€” brought to you by cgreen-runner out of the General Commands Manual, section 1. mwah, bye! πŸ’–πŸŽ€πŸŒΈ