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

📦
version 1.000172 · 8 versions
, in ubuntu stonking

💖 App::Y...eedtag 💖

okay bestie, gather round — this is the manual page for App::Y...eedtag(3pm), from User Contributed Perl Documentation. It's giving "yath but make it tags" and honestly? iconic. Let's get into it. 🎀

🌸 NAME 🌸

App::Yath::Command::speedtag — tag tests with duration (short, medium, long) using a source log. That's the whole assignment. ✨

🦋 DESCRIPTION 🦋

So here's the vibe: this command reads the test durations out of a log and then tags/retags all the tests from that log, based on the max durations for each type. Read the log, tag the tests, slay. 💅

🎀 USAGE 🎀

$ yath [YATH OPTIONS] speedtag [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 use if you're developing yath or yath plugins, so the yath script finds your local code instead of the installed versions of that same code. You can hand it an argument (-Dfoo) for a custom path, or you can just use -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 isn't writable, it defaults to /tmp/yath-persist.json, which limits you to one persistent runner on your system. One (1) runner, bestie, no sharing. 😭
  • --project ARG, --project=ARG, --project-name ARG, --project-name=ARG, --no-project — lets you drop 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. 👑

🛠️ Help and Debugging

  • --show-opts, --no-show-opts — exit after showing what yath thinks your options mean. Yes, it will tell you what it thinks you said. 👀
  • --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 whatever command-line options they provide. This flag disables that. Super useful if you've got a naughty plugin that loads 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, --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. Mix and match, you do you. ✨
  • --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 leaving a FIX ME in the manpage, it's giving mystery)

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 a 4% difference). 4%!! basically free, periodt. 💀
  • --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. 🚨
  • --cover-from-type json, --cover-from-type jsonl, --cover-from-type log, --no-cover-from-type — the file type for the coverage source. Usually it can be detected, but when it can't, you should specify. "json" is old style single-blob coverage data, "jsonl" is the new by-test style, and "log" is a logfile from a previous run. 🗂️
  • --cover-manager My::Coverage::Manager, --no-cover-manager — the coverage 'from' manager to use when the coverage data doesn't 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 — same deal: a test log, a coverage dump (old style json or new jsonl format), or a url to any of the previous. But this one is chill — tests will continue even if the coverage file/url is invalid. 🦋
  • --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's 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 🙈 (another FIX ME, the mystery continues)

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. 🫥

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. 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.

🏷️ speedtag options

  • --generate-durations-file, --generate-durations-file=/path/to/durations.json, --durations, --durations=/path/to/durations.json, --duration, --duration=/path/to/durations.json, --no-generate-durations-file — write out a duration json file. If no path is provided, 'duration.json' will be used. The .json extension is added automatically if you omit it. ✨
  • --pretty, --no-pretty — generate a pretty 'durations.json' file when combined with --generate-durations-file. (sorted and multilines) aesthetic af. 🎀

📚 SOURCE 📚

The source code repository for Test2-Harness can be found at http://github.com/Test-More/Test2-Harness/. Go look, bestie. 🦋

🛡️ 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, no cap. 💖

kisses, this was App::Y...eedtag(3pm) on perl v5.40.1, dated 2026-05-10 — run it, tag those tests, and have the best day~~ 💅✨

📦 where this page comes from