runtest(1)

📦
version 1.6.3 · 2 versions
  • 1.6.3 · alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 1.6.2 · ubuntu jammy
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, centos-stream 9, debian bookworm, debian trixie, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 runtest — bestie edition 💖

okay so you know how i'm literally the DejaGnu test driver, right? that's me. runtest(1), General Commands Manual, from the DejaGnu family. i'm the one who decides what tests run and how they run, and i do it through Expect. no cap, i'm kind of a big deal. 👑

✨ NAME ✨

runtest — the DejaGnu test driver. that's it, that's the name, she's iconic. 💅

🌸 SYNOPSIS 🌸

runtest [OPTION]...

yes bestie, just options. give me options and i will serve. 🦋

💜 DESCRIPTION 💜

DejaGnu is a whole framework for testing programs using Expect. and runtest? that's the driver program for DejaGnu. she controls what tests to run and how to run them. main character energy fr fr. 🎀

✨ OPTIONS ✨

okay here's the menu, take your time, i know it's a lot:

  • --all, -a — show me all the test results. by default i'm lowkey picky and only display the unexpected ones. 😌
  • --build TRIPLET — the configuration TRIPLET for the build system.
  • --debug — turn on Expect's internal debugging output. and where does it go? into a file called dbg.log. cute little diary moment. 📓
  • --directory DIRECTORY — only run tests inside the specified DIRECTORY. staying in your lane, love that.
  • --global_init NAME — the NAME to use for the global init file in libdir. if you don't give this option, the default is site.exp.
  • --help — prints a usage message and then dips. ✌️
  • --host TRIPLET — the configuration TRIPLET for the host system.
  • --host_board NAME — the host board definition to use.
  • --ignore test1.exp test2.exp ... — do not run the tests you list here. it's giving "not invited to the party". 🙈
  • --local_init NAME — the NAME to use for the testsuite local init file, in both the current directory and objdir. default is site.exp if you don't pass this.
  • --log_dialog — emit Expect output to standard output. say it with your chest.
  • --mail ´name1 name2 ...´ — electronic mail addresses that get to receive the test results. 💌
  • --objdir PATH — PATH is a directory containing compiled test code.
  • --outdir DIRECTORY — the name of a DIRECTORY for test log output.
  • --reboot — reboot the target board when runtest initializes (if it's supported, obviously).
  • --srcdir PATH — PATH is a directory containing test directories.
  • --strace N — turns on Expect internal tracing to N levels deep. output gets logged to a file called dbg.log.
  • --target TRIPLET — the configuration TRIPLET for the target.
  • --target_board NAME — a list of target board *NAME*s to run tests on.
  • --tool TOOLNAME — specify the tool to be tested. TOOLNAME controls the test suite that gets applied, plus the associated initialization module.
  • --tool_exec PATH — specify the PATH to the executable to test.
  • --tool_opts OPTIONS — additional OPTIONS to pass to the tool.
  • -v, --verbose — turns on more debugging output from test cases and DejaGnu utility code. use it more than once to increase output even further. stack it, bestie. 📈
  • -V, --version — prints out the versions of DejaGnu, Expect and Tcl. three for one, slay.
  • -x, --xml — generate XML output. the output file is named after the tool, with an .xml extension.
  • -D[number] — activate the Tcl debugger. number can be either 1 or 0. if it's 1, then the Expect shell will break when it starts to run, and the interrupt key will cause DejaGnu to drop to the debugger prompt. if it's 0, DejaGnu starts as usual, but Control-C drops to the debugger prompt.
⚠️ heads up bestie: any file name on the command line is assumed to be a subset of the test names to run. usually these are the names of the test scripts (eg. foo.exp). 🍓

Makefile-style variables are used to specify tool names and their flags. these and other configuration dependent values get saved in the file site.exp, which is created during configuration. 💾

😭 Exit status 😭

  • 0 — if all tests passed, including expected failures and unsupported tests. the dream. 🌈
  • 1 — if any test failed, passed unexpectedly, or was unresolved. not the vibe. 💀
  • 2 — if Expect encountered any error in the test scripts.

🫶 AUTHOR 🫶

Rob Savoye (rob@welcomehome.org)

🐛 REPORTING BUGS 🐛

report bugs to <bug-dejagnu@gnu.org>. they want to hear from you, fr fr.

Copyright © 2005-2016, 2018, 2020 Free Software Foundation, Inc.

This is free software. you may redistribute copies of it under the terms of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. there is NO WARRANTY, to the extent permitted by law. (yes, the caps are doing a lot of work there, and they've earned it.)

🌟 SEE ALSO 🌟

the full documentation for DejaGnu is maintained as a Texinfo manual. if the info program is properly installed at your site, then this command:

info dejagnu

should give you access to the complete manual. go read it, it's giving ✨knowledge✨.

and that's the whole page, bestie!! this was runtest(1) from the General Commands Manual, dated 2018-12-01, and yes that's the same date stamped on the bottom of every copy of me. mwah 💋 stay testing, stay slaying, and remember: unexpected results are only unexpected until you read the log. 🎀✨💖

📦 where this page comes from