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

📦
version 1.000172 · 8 versions
, in ubuntu stonking

💖 App::Y...::which(3pm) 💖

okay bestie, pull up a chair, we're reading the manual page for App::Y...::which(3pm) and honestly? it's giving "small but mighty". no cap. 🎀

🌸 NAME 🌸

App::Yath::Command::which — the lil command that locates the persistent test runner for you. it's basically the Find My Friends of your test runners. 🔍✨

🦋 DESCRIPTION 🦋

it will tell you about any persistent runners it can find. that's the whole vibe. it just knows where they're hiding. 🔥

💅 USAGE 💅

$ yath [YATH OPTIONS] which [COMMAND OPTIONS]

✨ YATH OPTIONS ✨

🧚 Developer

  • --dev-lib, --dev-lib=lib, -D, -D=lib, -Dlib, --no-dev-lib — adds paths to @INC before loading ANYTHING. this is the one you want if you're developing yath or yath plugins, so the yath script finds your local code instead of the installed versions of the same code. you can hand it an argument (-Dfoo) for a custom path, or you can just do -D with no arg to add lib, blib/lib and blib/arch. 👑

can be specified multiple times.

🌈 Environment

  • --persist-dir ARG, --persist-dir=ARG, --no-persist-dir — where to find persistence files.
  • --persist-file ARG, --persist-file=ARG, --pfile ARG, --pfile=ARG, --no-persist-file — where to find the persistence file. the default is /{system-tempdir}/project-yath-persist.json. if no project is specified then it falls back to the current directory. and if the current directory is not writable it defaults to /tmp/yath-persist.json, which — fair warning bestie — limits you to one persistent runner on your system. one. single. runner. 💀
  • --project ARG, --project=ARG, --project-name ARG, --project-name=ARG, --no-project — lets you provide a label for your current project/codebase. best used in a .yath.rc file. this is necessary for a persistent runner, so don't skip it fr fr.

🫶 Help and Debugging

  • --show-opts, --no-show-opts — exit after showing what yath thinks your options mean.
  • --version, -V, --no-version — exit after showing a helpful usage message.

🎀 Plugins

  • --no-scan-plugins, --no-no-scan-plugins — normally yath scans for and loads all App::Yath::Plugin::* modules so it can bring in any command-line options they provide. this flag disables that. super useful if you have a naughty plugin that's loading other modules when it should not be. 🙈
  • --plugins PLUGIN, --plugins +App::Yath::Plugin::PLUGIN, --plugins PLUGIN=arg1,arg2,..., --plugin PLUGIN, --plugin +App::Yath::Plugin::PLUGIN, --plugin PLUGIN=arg1,arg2,..., -pPLUGIN, --no-plugins — load a yath plugin.

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, --no-cover-aggregator — choose a custom aggregator subclass.
  • --cover-class ARG, --cover-class=ARG, --no-cover-class — choose a Test2::Plugin::Cover subclass.
  • --cover-dirs ARG, --cover-dirs=ARG, --cover-dir ARG, --cover-dir=ARG, --no-cover-dirs — NO DESCRIPTION - FIX ME 😭 (not me reading a manpage with a TODO in it)

can be specified multiple times.

  • --cover-exclude-private, --no-cover-exclude-private, --cover-files, --no-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). slay. ✨
  • --cover-from path/to/log.jsonl, --cover-from http://example.com/coverage, --cover-from path/to/coverage.jsonl, --no-cover-from — 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. so like, get it right. 🚨
  • --cover-from-type json, --cover-from-type jsonl, --cover-from-type log, --no-cover-from-type — file type for the coverage source. usually it can be detected, but when it cannot be, 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.
  • --cover-manager My::Coverage::Manager, --no-cover-manager — coverage 'from' manager to use when coverage data does not provide one.
  • --cover-maybe-from path/to/log.jsonl, --cover-maybe-from http://example.com/coverage, --cover-maybe-from path/to/coverage.jsonl, --no-cover-maybe-from — 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 coninue if even if the coverage file/url is invalid. (yes, that's a typo in the original — I love it, I'm keeping it, it's iconic 🫶)
  • --cover-maybe-from-type json, --cover-maybe-from-type jsonl, --cover-maybe-from-type log, --no-cover-maybe-from-type — same as "from_type" but for "maybe_from". defaults to "from_type" if that is specified, otherwise auto-detect.
  • --cover-metrics, --no-cover-metrics, --cover-types ARG, --cover-types=ARG, --cover-type ARG, --cover-type=ARG, --no-cover-types — NO DESCRIPTION - FIX ME

can be specified multiple times.

  • --cover-write, --cover-write=coverage.jsonl, --cover-write=coverage.json, --no-cover-write — create a json or jsonl file of all coverage data seen during the run (this implies --cover-files). 🔥

🐚 Git Options

  • --git-change-base master, --git-change-base HEAD^, --git-change-base df22abe4, --no-git-change-base — find files changed by all commits in the current branch from most recent, stopping when a commit is found that is also present in the history of the branch/commit specified as the change base.

👑 Help and Debugging

  • --dummy, -d, --no-dummy — dummy run, do not actually execute anything. nothing happens and yet everything happens. 💅

can also be set with the following environment variables: "T2_HARNESS_DUMMY"

  • --help, -h, --no-help — exit after showing help information.
  • --interactive, -i, --no-interactive — use interactive mode, 1 test at a time, stdin forwarded to it.
  • --keep-dirs, --keep_dir, -k, --no-keep-dirs — do not delete directories when done. useful if you want to inspect the directories used for various commands.
  • --procname-prefix ARG, --procname-prefix=ARG, --no-procname-prefix — add a prefix to all proc names (as seen by ps).

⭐ YathUI Options

  • --yathui-api-key ARG, --yathui-api-key=ARG, --no-yathui-api-key — Yath-UI API key. this is not necessary if your Yath-UI instance is set to single-user.
  • --yathui-grace, --no-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. 🌈
  • --yathui-long-duration 10, --no-yathui-long-duration — minimum duration length (seconds) before a test goes from MEDIUM to LONG.
  • --yathui-medium-duration 5, --no-yathui-medium-duration — minimum duration length (seconds) before a test goes from SHORT to MEDIUM.
  • --yathui-mode summary, --yathui-mode qvf, --yathui-mode qvfd, --yathui-mode complete, --no-yathui-mode — set the upload mode (default 'qvfd').
  • --yathui-project ARG, --yathui-project=ARG, --no-yathui-project — the Yath-UI project for your test results.
  • --yathui-retry, --no-yathui-retry — how many times to try an operation before giving up.

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, it's free real estate. 🫶

💖 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, you ate it, you understood it, you're literally the main character of persistent test runner location now. 💅✨

now go forth and vibe check those runners. this was App::Y...::which(3pm) from perl v5.40.1, dated 2026-05-10 — mwah, no notes, periodt. 👑🌸💜

📦 where this page comes from