App::Y...runner(3pm)

📦
version 1.000172 · 8 versions
, in ubuntu stonking

💖 App::Y...runner — bestie edition 💖

okay so this is App::Yath::Command::runner from the User Contributed Perl Documentation, and it's for internal use only — like, we're in the backstage area of the group chat here, not the main room ✨

🌸 NAME 🌸

App::Yath::Command::runner — for internal use only. that's it. that's the whole name section. she's private, she's exclusive, she's not taking new applications 💅

🦋 DESCRIPTION 🦋

No Description. literally nothing. an empty vibe. the manpage said "No Description" and honestly? respect for the honesty 😭

✨ USAGE ✨

here's how you'd call her:

$ yath [YATH OPTIONS] runner [COMMAND OPTIONS]

👑 YATH OPTIONS 👑

🧚 Developer

  • --dev-lib, --dev-lib=lib, -D, -D=lib, -Dlib — okay so this one adds paths to @INC before loading ANYTHING. like, before anything else gets to load. this is your girl if you're developing yath or yath plugins and you need the yath script to find your local code instead of the installed versions of the exact same code. you can hand it an argument (-Dfoo) for a custom path, or you can just rawdog it as -D with no arg and it'll add lib, blib/lib and blib/arch 🫶
  • --no-dev-lib — the opposite of all that (same bullet family, listed right there in the original, so here she is) 💜
can be specified multiple times, so go off, stack them, she can handle it ⭐

🌈 Environment

  • --persist-dir ARG, --persist-dir=ARG — where to find persistence files.
  • --no-persist-dir — the negation, as the name promises 🙈
  • --persist-file ARG, --persist-file=ARG, --pfile ARG, --pfile=ARG — where to find the persistence file. default is /{system-tempdir}/project-yath-persist.json. if no project is specified it falls back to the current directory. and if the current directory is not writable? it defaults to /tmp/yath-persist.json, which limits you to one persistent runner on your system 😭
  • --no-persist-file — negate it, slay.
  • --project ARG, --project=ARG, --project-name ARG, --project-name=ARG — this gives you a label for your current project/codebase. best used in a .yath.rc file. it's necessary for a persistent runner, no cap 🎀
  • --no-project — the off switch.

🔥 Help and Debugging

  • --show-opts — exit after showing what yath thinks your options mean. like a vibe check on your own flags 👑
  • --no-show-opts — don't do that.
  • --version, -V — exit after showing a helpful usage message.
  • --no-version — the negation, bestie.

🍓 Plugins

  • --no-scan-plugins, --no-no-scan-plugins — normally yath scans for and loads all App::Yath::Plugin::* modules so it can bring in whatever command-line options they provide. this flag disables that whole operation. useful when you have a naughty plugin loading other modules when it absolutely should not 🧚
  • --plugins PLUGIN, --plugins +App::Yath::Plugin::PLUGIN, --plugins PLUGIN=arg1,arg2,..., --plugin PLUGIN, --plugin +App::Yath::Plugin::PLUGIN, --plugin PLUGIN=arg1,arg2,..., -pPLUGIN — load a yath plugin. yes queen 💅
  • --no-plugins — no plugins for you.
can be specified multiple times 💖

💜 COMMAND OPTIONS 💜

🎀 Cover Options

  • --cover-aggregator ByTest, --cover-aggregator ByRun, --cover-aggregator +Custom::Aggregator, --cover-agg ByTest, --cover-agg ByRun, --cover-agg +Custom::Aggregator — choose a custom aggregator subclass ✨
  • --no-cover-aggregator — the off switch for the aggregator.
  • --cover-class ARG, --cover-class=ARG — choose a Test2::Plugin::Cover subclass.
  • --no-cover-class — the negation, obviously.
  • --cover-dirs ARG, --cover-dirs=ARG, --cover-dir ARG, --cover-dir=ARG — NO DESCRIPTION - FIX ME 😭 the manpage really said "figure it out"
  • --no-cover-dirs — the off switch.
can be specified multiple times 🫶
  • --cover-exclude-private — self-explanatory-ish, it's right there in the name, love that for us.
  • --no-cover-exclude-private — un-exclude the private stuff.
  • --cover-files — use Test2::Plugin::Cover to collect coverage data for what files are touched by what tests. unlike Devel::Cover this has very little performance impact (about 4% difference, which is honestly nothing) 🔥
  • --no-cover-files — the off switch.
  • --cover-from path/to/log.jsonl, --cover-from http://example.com/coverage, --cover-from path/to/coverage.jsonl — this can be a test log, a coverage dump (old style json or new jsonl format), or a url to any of the previous. tests will not be run if the file/url is invalid 💀
  • --no-cover-from — the negation.
  • --cover-from-type json, --cover-from-type jsonl, --cover-from-type log — file type for the coverage source. usually it can be detected on its own, but when it cannot you should specify. "json" is old style single-blob coverage data, "jsonl" is the new by-test style, "log" is a logfile from a previous run 🌸
  • --no-cover-from-type — off switch, you know the drill.
  • --cover-manager My::Coverage::Manager — coverage 'from' manager to use when coverage data does not provide one.
  • --no-cover-manager — negated.
  • --cover-maybe-from path/to/log.jsonl, --cover-maybe-from http://example.com/coverage, --cover-maybe-from path/to/coverage.jsonl — same deal as --cover-from, it can be a test log, a coverage dump (old style json or new jsonl format), or a url to any of the previous. but tests will continue even if the coverage file/url is invalid — hence the "maybe", she's forgiving 💖
  • --no-cover-maybe-from — the negation.
  • --cover-maybe-from-type json, --cover-maybe-from-type jsonl, --cover-maybe-from-type log — same as "from_type" but for "maybe_from". defaults to "from_type" if that is specified, otherwise auto-detect 🦋
  • --no-cover-maybe-from-type — the off switch.
  • --cover-metrics — yes. it exists. the original didn't say more, so neither will I 🙈
  • --no-cover-metrics — the negation.
  • --cover-types ARG, --cover-types=ARG, --cover-type ARG, --cover-type=ARG — NO DESCRIPTION - FIX ME 😭
  • --no-cover-types — off switch.
  • --cover-write, --cover-write=coverage.jsonl, --cover-write=coverage.json — create a json or jsonl file of all coverage data seen during the run. (this implies --cover-files) — so it's a package deal, iykyk 👑
  • --no-cover-write — the negation.

🌈 Git Options

  • --git-change-base master, --git-change-base HEAD^, --git-change-base df22abe4 — find files changed by all commits in the current branch, starting from most recent and stopping when a commit is found that is also present in the history of the branch/commit specified as the change base. it's giving archaeology but for your git history ✨
  • --no-git-change-base — the off switch.

⭐ Help and Debugging

  • --dummy, -d — dummy run, do not actually execute anything. she's a rehearsal, not the show 💅
  • --no-dummy — turn it off.
can also be set with the following environment variables: "T2_HARNESS_DUMMY" 💖
  • --help, -h — exit after showing help information.
  • --no-help — no help for you, bestie.
  • --interactive, -i — use interactive mode, 1 test at a time, stdin forwarded to it 🫶
  • --no-interactive — the negation.
  • --keep-dirs, --keep_dir, -k — do not delete directories when done. useful if you want to inspect the directories used for various commands 👀
  • --no-keep-dirs — delete them like normal.
  • --procname-prefix ARG, --procname-prefix=ARG — add a prefix to all proc names (as seen by ps).
  • --no-procname-prefix — the off switch.

🍓 YathUI Options

  • --yathui-api-key ARG, --yathui-api-key=ARG — Yath-UI API key. not necessary if your Yath-UI instance is set to single-user 🔑
  • --no-yathui-api-key — the negation.
  • --yathui-grace — if yath cannot connect to yath-ui it normally throws an error. use this to make it fail gracefully. you get a warning, but things keep going — she's chill like that 💜
  • --no-yathui-grace — let it throw, drama queen.
  • --yathui-long-duration 10 — minimum duration length (seconds) before a test goes from MEDIUM to LONG ⏳
  • --no-yathui-long-duration — the off switch.
  • --yathui-medium-duration 5 — minimum duration length (seconds) before a test goes from SHORT to MEDIUM 🌸
  • --no-yathui-medium-duration — the off switch.
  • --yathui-mode summary, --yathui-mode qvf, --yathui-mode qvfd, --yathui-mode complete — set the upload mode (default 'qvfd') ✨
  • --no-yathui-mode — off.
  • --yathui-project ARG, --yathui-project=ARG — the Yath-UI project for your test results 🎀
  • --no-yathui-project — the negation.
  • --yathui-retry — how many times to try an operation before giving up. she's persistent, periodt 💅
  • --no-yathui-retry — give up immediately, honestly valid.
can be specified multiple times 🫶

🌟 SOURCE 🌟

The source code repository for Test2-Harness can be found at http://github.com/Test-More/Test2-Harness/ — go look, go star it, go lurk 👑

💜 MAINTAINERS 💜

  • Chad Granum <exodist@cpan.org>

🦋 AUTHORS 🦋

  • Chad Granum <exodist@cpan.org>

Copyright 2026 Chad Granum <exodist7@gmail.com>.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

See http://dev.perl.org/licenses/

and that's the whole page, bestie 💖 this was perl v5.40.1, dated 2026-05-10, filed under App::Y...runner(3pm) in the User Contributed Perl Documentation. go forth and run responsibly ✨🫶🌸

📦 where this page comes from