DBUS-TEST-RUNNER(1)

✨ DBUS-TEST-RUNNER ✨

okay bestie, gather round, because this is the manual page for dbus-test-runner version 19.04.0, and it's literally about running a whole bunch of tasks under their own independent DBus session bus. no cap. 💅

---

🌸 DESCRIPTION 🌸

🦋 Usage:

dbus-test-runner [OPTION?] - run multiple tasks under an independent DBus session bus

like... that's the whole vibe. you give it tasks, it gives them a private lil DBus session to play in. iconic. ✨

---

🎀 Help Options:

• -h, --help — shows the help options. the classic. the moment. 🫶
• --help-all — shows all the help options, not just the cute ones.
• --help-task-control — spills the tea on the options that control how a task gets handled by the test runner.

---

👑 Task control options

these are the ones that decide how each task gets treated. main character energy only. 💖

• -t, --task=executable — defines a new task to run under our private DBus session. yes, our session. we're sharing. 🥰
• -n, --task-name=name — a string to label the output from the previously defined task. defaults to taskN if you don't say anything. (it's giving unnamed group chat member, ngl.)
• --task-bus={session|system|both} — configures which bus the task expects to connect to. default: both. so generous of it fr fr.
• -r, --ignore-return — do not use the return value of the task to calculate whether the test passes or fails. we're not judging here. 🙈
• -i, --invert-return — inverts the return value of the task before calculating whether the test passes or fails. flipped. reversed. slay.
• -p, --parameter — adds a parameter to the call of this utility. may be called as many times as you'd like. go off, honestly. 💅
• -f, --wait-for=dbus-name — a dbus-name that should appear on the bus before this task is started. we wait for the name to walk in. 🚶♀️✨
• -c, --wait-until-complete — signals that we should wait until this task exits, even if we don't actually need the return value. just vibes. just patience. 🧘♀️

---

🌈 Application Options:

the big-picture settings. the ~setup~. 🌟

• --dbus-daemon=executable — path to the DBus deamon to use. defaults to 'dbus-daemon'. (yes, the original says "deamon". we respect the typo. it's canon now. 😭)
• -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. write it down, bestie, we're documenting everything. 📝
• -m, --max-wait=seconds — the maximum amount of time the test runner will wait for the test to complete. default is 30 seconds. after that? we're moving on. ⏰
• --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 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.

💀 heads up: --keep-env is opt-in for a reason — by default the environment is cleared, so don't be shocked when your vars ghost you.

---

and that's the whole page, bestie. no notes. go run your tasks under a private bus and thrive. 🦋

🌸✨ mwah ✨🌸 — this has been dbus-test-runner version 19.04.0, dated July 2025. periodt. 💜