dbus-test-runner(1)

📦
version 19.04.0 · 2 versions
, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble

✨ dbus-test-runner ✨

okay so welcome to the dbus-test-runner(1) manual page bestie, this is the one that runs a whole bunch of tasks under their own private DBus session bus and honestly? iconic. 🦋

🌸 NAME 🌸

dbus-test-runner — run multiple tasks under an independent DBus session bus 💅

🎀 SYNOPSIS 🎀

dbus-test-runner [ options ]

💖 DESCRIPTION 💖

dbus-test-runner is a simple little executable for running a couple of programs under a new DBus session. like, it's small, it's cute, it does one thing and it ATE. 👑

Use this DBus tool for unit testing of code that accesses DBus at runtime. fr fr, that's the whole vibe.

🙈 HELP OPTIONS 🙈

dbus-test-runner accepts the following help options on the command line:

  • -h, --help — shows you a short help text with the application and help command line options, then dips. bye bestie 👋
  • --help-all — shows the FULL list of available command line options (help, task control, application) and then exits. the whole menu, no gatekeeping ✨
  • --help-task-control — shows just the options that control how a task is handled by the test runner. the task-control-only corner 🎀

🧚 TASK CONTROL OPTIONS 🧚

dbus-test-runner accepts the following task control options on the command line:

  • -t, --task=<executable> — defines a new task to run under our private DBus session. new task, who dis 💅
  • -n, --task-name=<name> — a string to label the output from the previously defined task. defaults to taskN. name your babies 🍼
  • --task-bus={session|system|both} — configures which bus the task expects to connect to. Default: both
  • -r, --ignore-return — do not use the return value of the task to calculate whether the test passes or fails. like, we're not checking the receipts on this one 🙈
  • -i, --invert — inverts the return value of the task before calculating whether the test passes or fails. plot twist energy 🔄
  • -p, --parameter — add a parameter to the call of this utility. may be called as many times as you'd like. go off, stack 'em 🫶
  • -f, --wait-for=<dbus-name> — a dbus-name that should appear on the bus before this task is started. we WAIT for our friends, periodt ⏳
  • -c, --wait-until-complete — signal that we should wait until this task exits even if we don't need the return value. main character stays till the end of the movie 🎬
ngl the original page has a lil stray fragment eturn hanging out in this section (a typo moment, it's giving copy-paste tragedy 😭). we're keeping it exactly as it is because the facts do not change. 💀

🌈 APPLICATION OPTIONS 🌈

dbus-test-runner accepts the following application options on the command line:

  • --dbus-daemon=<executable> — path to the DBus daemon to use. defaults to 'dbus-daemon'.
  • -d, --dbus-config=<config_file> — configuration file for the newly created DBus server. defaults to '/usr/share/dbus-test-runner/session.conf'.
  • --bustle-monitor=<executable> — path to the Bustle DBus Monitor to use. defaults to 'bustle-dbus-monitor'.
  • -b, --bustle-data=<data_file> — a file to write out data from the bustle logger to. spill the tea into a file ☕
  • -m, --max-wait=<seconds> — the maximum amount of time the test runner will wait for the test to complete. default is 30 seconds. tick tock bestie ⏰
  • --keep-env — whether to propagate the execution environment to the dbus-server and all the services activated by it. by default the environment is cleared. so if you want your env vars to come with you, you gotta ask 🥺
  • --bus-type={session|system|both} — configures which buses are represented by the tool to the tasks. Default: session

👀 SEE ALSO 👀

💜 AUTHOR 💜

This manual has been written for the Debian project by Mike Gabriel <mike.gabriel@das-netzwerkteam.de> and may be used by others. shoutout to Mike, absolute legend 🫶

Version 15.04.20141209 · Jan 2015

okay that's the whole page bestie, go forth and run your tasks under your own little DBus session, you're gonna slay 💅✨🌸🦋

📦 where this page comes from