App::Y...nd::run(3pm)

📦
version 1.000172 · 8 versions
, in ubuntu stonking

💖 NAME 💖

App::Yath::Command::run — bestie, this is the run command, and it is literally here to run your tests using the persistent test runner 👑

(also hiii, you're reading the manual page App::Yath::Command::run(3pm) from the User Contributed Perl Documentation — it also answers to App::Yath::run(3pm), and this is part 1 of 3, so there is more coming, do not go anywhere 🫶)

🦋 DESCRIPTION 🦋

okay so picture this: you've already got a persistent instance up and running (that's a whole separate thing — check the start command for the deets on how to launch a persistant instance, and yes, that's how it's spelled here, we keep it exactly as written, no notes 💅). This command runs your tests through that already-started persistent instance. that's it, that's the vibe, iconic ✨

🎀 USAGE 🎀

$ yath [YATH OPTIONS] run [COMMAND OPTIONS]

✨ YATH OPTIONS ✨

Developer

  • --dev-lib, --dev-lib=lib, -D, -D=lib, -Dlib, --no-dev-lib — drops paths into @INC before loading ANYTHING. This is the one you reach for if you're developing yath or yath plugins, so your yath script finds the local code instead of the installed versions of the same code. You can hand it an argument (-Dfoo) to provide a custom path, or you can just use -D without an 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 will fall back to the current directory. And if the current directory is not writable it will default to /tmp/yath-persist.json, which limits you to one persistent runner on your system 😭
  • --project ARG, --project=ARG, --project-name ARG, --project-name=ARG, --no-project — this lets you provide a label for your current project/codebase. Best used in a .yath.rc file. And heads up, this is necessary for a persistent runner. no label, no runner, fr fr 🫶

Finder Options

  • --finder MyFinder, --finder +Test2::Harness::Finder::MyFinder, --no-finder — pick which Finder subclass gets used when searching for files / processing the file list. Use the + prefix to specify a fully qualified namespace, otherwise the Test2::Harness::Finder::XXX namespace is assumed. periodt 🔍

Help and Debugging

  • --show-opts, --no-show-opts — exit after showing what yath thinks your options mean. like a lil vibe check on your flags 👀
  • --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 in order to bring in command-line options they may provide. This flag disables that. Super useful if you have a naughty plugin that is loading other modules when it 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. 📊
  • --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 😭 (yes bestie, that is literally what the page says, I am not about to invent something). 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. ⚠️
  • --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 even if the coverage file/url is invalid. (and yes — "coninue" — that's the typo straight off the page and honestly? keeping it exactly as written, 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). 🎀

Display Options

  • --color, --no-color — turn color on, default is true if STDOUT is a TTY. 🌈
  • --hide-runner-output, --no-hide-runner-output — hide output from the runner, showing only test output. (See Also truncate_runner_output.)
  • --no-final-table, --no-no-final-table — when printing final results, don't use table-style display. 🙅
  • --no-wrap, --no-no-wrap — do not do fancy text-wrapping, let the terminal handle it.
  • --progress, --no-progress — toggle progress indicators. On by default if STDOUT is a TTY. You can use --no-progress to disable the 'events seen' counter and buffered event pre-display. ✨
  • --quiet, -q, --no-quiet — be very quiet. Can be specified multiple times 🤫
  • --renderers +My::Renderer, --renderers Renderer=arg1,arg2,..., --renderer +My::Renderer, --renderer Renderer=arg1,arg2,..., --no-renderers — specify renderers, (Default: "Formatter=Test2"). Use "+" to give a fully qualified module name. Without "+", "Test2::Harness::Renderer::" will be prepended to your argument. Can be specified multiple times. If the same key is listed multiple times the value lists will be appended together. 🧚
  • --show-times, -T, --no-show-times — show the timing data for each job. ⏱️
  • --term-width 80, --term-width 200, --term-size 80, --term-size 200, --no-term-width — alternative to setting $TABLE_TERM_SIZE. Setting this will override the terminal width detection to the number of characters specified.
  • --truncate-runner-output, --no-truncate-runner-output — only show runner output that was generated after the current command. This is only useful with a persistent runner.
  • --verbose, -v, --no-verbose — be more verbose. Can be specified multiple times 🗣️

Finder Options

  • --changed path/to/file, --no-changed — specify one or more files as having been changed. Can be specified multiple times
  • --changed-only, --no-changed-only — only search for tests for changed files (Requires a coverage data source, also requires a list of changes either from the --changed option, or a plugin that implements changed_files() or changed_diff()). 👀
  • --changes-diff path/to/diff.diff, --no-changes-diff — path to a diff file that should be used to find changed files for use with --changed-only. This must be in the same format as git diff -W --minimal -U1000000. 🩷
  • --changes-exclude-file path/to/file, --no-changes-exclude-file — specify one or more files to ignore when looking at changes. Can be specified multiple times 🙈
  • --changes-exclude-loads, --no-changes-exclude-loads — exclude coverage tests which only load changed files, but never call code from them. (default: off)
  • --changes-exclude-nonsub, --no-changes-exclude-nonsub — exclude changes outside of subroutines (perl files only) (default: off)
  • --changes-exclude-opens, --no-changes-exclude-opens — exclude coverage tests which only open() changed files, but never call code from them. (default: off)
  • --changes-exclude-pattern '(apple|pear|orange)', --no-changes-exclude-pattern — ignore files matching this pattern when looking for changes. Your pattern will be inserted unmodified into a $file =~ m/$pattern/ check. Can be specified multiple times 🍎🍐🍊
  • --changes-filter-file path/to/file, --no-changes-filter-file — specify one or more files to check for changes. Changes to other files will be ignored. Can be specified multiple times
  • --changes-filter-pattern '(apple|pear|orange)', --no-changes-filter-pattern — specify a pattern for change checking. When only running tests for changed files this will limit which files are checked for changes. Only files that match this pattern will be checked. Your pattern will be inserted unmodified into a $file =~ m/$pattern/ check. Can be specified multiple times
  • --changes-include-whitespace, --no-changes-include-whitespace — include changed lines that are whitespace only (default: off)
  • --changes-plugin Git, --changes-plugin +App::Yath::Plugin::Git, --no-changes-plugin — what plugin should be used to detect changed files. 🔍
  • --default-at-search ARG, --default-at-search=ARG, --no-default-at-search — specify the default file/dir search when 'AUTHOR_TESTING' is set. Defaults to './xt'. The default AT search is only used if no files were specified at the command line. Can be specified multiple times
  • --default-search ARG, --default-search=ARG, --no-default-search — specify the default file/dir search. Defaults to './t', './t2', and 'test.pl'. The default search is only used if no files were specified at the command line. Can be specified multiple times 🎯

okay that's everything in part 1 bestie, hold on tight because there is more coming 🫶

  • --durations file.json, --durations http://example.com/durations.json, --no-durations — point this at a json file or a url that holds a hash where the keys are relative test filenames and the values are 'SHORT', 'MEDIUM', or 'LONG'. This overrides the durations that were listed in the file headers. If the durations file or url doesn't work, an exception gets thrown. no cap, it will yell 💅
  • --durations-threshold ARG, --durations-threshold=ARG, --Dt ARG, --Dt=ARG, --no-durations-threshold — only bother fetching duration data if you're running at least this many tests. Default is (-j value + 1). 🧮
  • --exclude-file t/nope.t, --no-exclude-file — exclude a file from testing 🙈

Can be specified multiple times

  • --exclude-list file.txt, --exclude-list http://example.com/exclusions.txt, --no-exclude-list — point at a file or url that has a newline-separated list of test file names to exclude from testing. Start a line with # and it gets commented out (that's for compatibility with Test2::Aggregate list files, iykyk). 📝

Can be specified multiple times

  • --exclude-pattern t/nope.t, --no-exclude-pattern — exclude a pattern from testing, matched using m/$PATTERN/ 🎯

Can be specified multiple times

  • --extension ARG, --extension=ARG, --ext ARG, --ext=ARG, --no-extension — tell it which test filename extensions are valid, default: t and t2 ✨

Can be specified multiple times

  • --maybe-durations file.json, --maybe-durations http://example.com/durations.json, --no-maybe-durations — point at a json file or a url with a hash where the keys are relative test filenames and the values are 'SHORT', 'MEDIUM', or 'LONG'. This overrides the durations listed in the file headers. An exception gets thrown if the durations file or url doesn't work. same energy as --durations, just vibing under a different name fr fr
  • --no-long, --no-no-long — do not run tests that have their duration flag set to 'LONG' 🛑
  • --only-long, --no-only-long — only run tests that have their duration flag set to 'LONG' 👑
  • --rerun, --rerun=path/to/log.jsonl, --rerun=plugin_specific_string, --no-rerun — re-run tests from a previous run, pulled from a log file (or the last log file if you don't name one). Plugins can intercept this — for example YathUIDB, which grabs a run UUID and derives the tests to re-run from that. 🔁
  • --rerun-all, --rerun-all=path/to/log.jsonl, --rerun-all=plugin_specific_string, --no-rerun-all — re-run all the tests from a previous run, from a log file (or the last log file). Plugins can intercept this, like YathUIDB, which grabs a run UUID and derives tests to re-run from that. 💖
  • --rerun-failed, --rerun-failed=path/to/log.jsonl, --rerun-failed=plugin_specific_string, --no-rerun-failed — re-run the failed tests from a previous run, from a log file (or the last log file). Plugins can intercept this, like YathUIDB, which grabs a run UUID and derives tests to re-run from that. 😭
  • --rerun-missed, --rerun-missed=path/to/log.jsonl, --rerun-missed=plugin_specific_string, --no-rerun-missed — run the tests that got missed by a previously aborted/stopped run, from a log file (or the last log file). Plugins can intercept this, like YathUIDB, which grabs a run UUID and derives tests to re-run from that. 🫥
  • --rerun-modes failed,missed,..., --rerun-modes all, --rerun-modes failed, --rerun-modes missed, --rerun-modes passed, --rerun-modes retried, --rerun-mode failed,missed,..., --rerun-mode all, --rerun-mode failed, --rerun-mode missed, --rerun-mode passed, --rerun-mode retried, --no-rerun-modes — pick which test categories actually get run 🎛️

Can be specified multiple times

  • --rerun-passed, --rerun-passed=path/to/log.jsonl, --rerun-passed=plugin_specific_string, --no-rerun-passed — re-run the passed tests from a previous run, from a log file (or the last log file). Plugins can intercept this, like YathUIDB, which grabs a run UUID and derives tests to re-run from that. 🌈
  • --rerun-plugin Foo, --rerun-plugin +App::Yath::Plugin::Foo, --no-rerun-plugin — which plugin(s) should be used for rerun (it'll fall back to other plugins if the listed ones decline the value, this is just used to set an order of priority) 🧚

Can be specified multiple times

  • --rerun-retried, --rerun-retried=path/to/log.jsonl, --rerun-retried=plugin_specific_string, --no-rerun-retried — re-run the tests that got retried in a previous run, from a log file (or the last log file). Plugins can intercept this, like YathUIDB, which grabs a run UUID and derives tests to re-run from that. 🔄
  • --search ARG, --search=ARG, --no-search — a list of tests and test directories to use instead of the default search paths. Lowkey you can usually just list these as plain command line arguments without the --search prefix. 🔍

Can be specified multiple times

  • --show-changed-files, --no-show-changed-files — print a list of changed files if any are found 📂

✨ Formatter Options ✨

  • --formatter ARG, --formatter=ARG, --no-formatter — the manpage literally just says NO DESCRIPTION - FIX ME 💀 keeping it 100, that's all it says, so that's all I'm telling you
  • --qvf, --no-qvf — [Q]uiet, but [V]erbose on [F]ailure. Hide all output from tests when they pass, except to say they passed. But if a test fails, then ALL the output from that test gets verbosely dumped out. iconic behaviour honestly 💅
  • --show-job-end, --no-show-job-end — show output when a job ends. (Default: on) 🏁
  • --show-job-info, --no-show-job-info — show the job configuration when a job starts. (Default: off, unless -vv) 📋
  • --show-job-launch, --no-show-job-launch — show output for the start of a job. (Default: off unless -v) 🚀
  • --show-run-info, --no-show-run-info — show the run configuration when a run starts. (Default: off, unless -vv) 🎬

🌸 Git Options 🌸

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

🎀 Help and Debugging 🎀

  • --dummy, -d, --no-dummy — dummy run, it doesn't 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, with stdin forwarded to it 🎮
  • --keep-dirs, --keep_dir, -k, --no-keep-dirs — do not delete directories when done. super useful if you wanna go snooping through the directories that various commands used. 🔎
  • --procname-prefix ARG, --procname-prefix=ARG, --no-procname-prefix — add a prefix to all proc names (as seen by ps). 🏷️
  • --summary, --summary=/path/to/summary.json, --no-summary — write out a summary json file; if you don't give it a path, 'summary.json' gets used. The .json extension is added automatically if you omit it. 📊

💜 Logging Options 💜

  • --bzip2, --bz2, --bzip2_log, -B, --no-bzip2 — use bzip2 compression when writing the log. This option implies -L. The .bz2 prefix is added to the log file name for you. 🗜️
  • --gzip, --gz, --gzip_log, -G, --no-gzip — use gzip compression when writing the log. This option implies -L. The .gz prefix is added to the log file name for you. 🗜️
  • --log, -L, --no-log — turn on logging 📓
  • --log-dir ARG, --log-dir=ARG, --no-log-dir — specify a log directory. Will fall back to the system temp dir. 📁
  • --log-file ARG, --log-file=ARG, -F ARG, -F=ARG, --no-log-file — specify the name of the log file. This option implies -L. 📝
  • --log-file-format ARG, --log-file-format=ARG, --lff ARG, --lff=ARG, --no-log-file-format — specify the format for automatically-generated log files. Overridden by --log-file, if given. This option implies -L (Default: $YATH_LOG_FILE_FORMAT, if that is set, or else "%!P%Y-%m-%d~%H:%M:%S~%!U~%!p.jsonl"). This is a string where percent-escape sequences get replaced as per POSIX::strftime. These special escape sequences also get replaced: (%!P : project name followed by a ~, if a project is defined, otherwise an empty string) (%!U : the unique test run ID) (%!p : the process ID) (%!S : the number of seconds since local midnight UTC) ⏰

Can also be set with the following environment variables: YATH_LOG_FILE_FORMAT, TEST2_HARNESS_LOG_FORMAT

🔔 Notification Options 🔔

  • --notify-email foo@example.com, --no-notify-email — email the test results to the specified email address(es) 📧

Can be specified multiple times

  • --notify-email-fail foo@example.com, --no-notify-email-fail — email the failing results to the specified email address(es) 😬

Can be specified multiple times

  • --notify-email-from foo@example.com, --no-notify-email-from — if any email gets sent, this is who it will be from ✉️
  • --notify-email-owner, --no-notify-email-owner — email the owner of the broken test files upon failure. Add # HARNESS-META-OWNER foo@example.com to the top of a test file to give it an owner. 👤
  • --notify-no-batch-email, --no-notify-no-batch-email — usually owner failures get sent as a single batch at the end of testing. Toggle this to send failures as they happen. ⚡
  • --notify-no-batch-slack, --no-notify-no-batch-slack — usually owner failures get sent as a single batch at the end of testing. Toggle this to send failures as they happen. ⚡
  • --notify-slack '#foo', --notify-slack '@bar', --no-notify-slack — send results to a slack channel and/or user 💬

Can be specified multiple times

  • --notify-slack-fail '#foo', --notify-slack-fail '@bar', --no-notify-slack-fail — send the failing results to a slack channel and/or user 💔

Can be specified multiple times

  • --notify-slack-owner, --no-notify-slack-owner — send slack notifications to the slack channels/users listed in the test meta-data when tests fail. 📨
  • --notify-slack-url https://hooks.slack.com/..., --no-notify-slack-url — specify an API endpoint for slack webhook integrations. 🔗
  • --notify-text ARG, --notify-text=ARG, --message ARG, --message=ARG, --msg ARG, --msg=ARG, --no-notify-text — add a custom text snippet to email/slack notifications ✍️
  • --notify-text-module ARG, --notify-text-module=ARG, --message_module ARG, --message_module=ARG, --no-notify-text-module — use the specified module to generate messages for emails and/or slack. 🧩

⭐ Run Options ⭐

  • --author-testing, -A, --no-author-testing — this flips the AUTHOR_TESTING environment variable to true. Yeah bestie, some tests literally will not run unless they know you're the author, and this is how you tell them. 💖
  • --dbi-profiling, --no-dbi-profiling — pulls in Test2::Plugin::DBIProfile so you're collecting database profiling data while the tests run. Gotta see where the queries are eating your time, fr fr. 🔥
  • --env-var VAR=VAL, -EVAR=VAL, -E VAR=VAL, --no-env-var — sets environment variables that get applied when each test runs. 🌈

Can be specified multiple times, so stack 'em up.

  • --event-uuids, --uuids, --no-event-uuids — uses Test2::Plugin::UUID inside tests. Default: on. The UUIDs are giving uniqueness, and honestly? Iconic. ✨
  • --fields name:details, --fields JSON_STRING, -f name:details, -f JSON_STRING, --no-fields — adds custom data to the harness run. Very main-character of you to leave your own little notes in there. 💅

Can be specified multiple times.

  • --input ARG, --input=ARG, --no-input — an input string used as standard input for ALL tests. Literally all of them. Also check out --input-file if a string isn't enough. 🎀
  • --input-file ARG, --input-file=ARG, --no-input-file — same energy, but you point at a file, and that file becomes standard input for ALL tests. 📁
  • --io-events, --no-io-events — uses Test2::Plugin::IOEvents inside tests, which turns all prints into test2 events. Default: off. So if you don't set this, your prints stay prints. 🦋
  • --link 'https://travis.work/builds/42', --link 'https://jenkins.work/job/42', --link 'https://buildbot.work/builders/foo/builds/42', --no-link — drops one or more links so people can go look at more info about this run. Sharing is caring, bestie. 🫶

Can be specified multiple times.

  • --load ARG, --load=ARG, --load-module ARG, --load-module=ARG, -m ARG, -m=ARG, --no-load — loads a module in each test, and this happens after fork. The import method is not called. Not even a little bit. 👀

Can be specified multiple times.

  • --load-import Module, --load-import Module=import_arg1,arg2,..., --loadim Module, --loadim Module=import_arg1,arg2,..., -M Module, -M Module=import_arg1,arg2,..., --no-load-import — also loads a module in each test after fork, but this time import is called. 🌸

Can be specified multiple times. And heads up: if the same key shows up multiple times, the value lists get appended together. No overwriting, just vibes stacking. ✨

  • --mem-usage, --no-mem-usage — uses Test2::Plugin::MemUsage inside tests. Default: on. Watching the memory like 👀💀
  • --retry ARG, --retry=ARG, -r ARG, -r=ARG, --no-retry — runs any job that failed a second time. And please clock this: --retry=1 means failing tests get attempted twice! The number isn't "extra tries", it's total tries. Not me learning this the hard way. 😭
  • --retry-isolated, --retry-iso, --no-retry-isolated — if true, any job retries happen in isolation, like -j1 was set. Alone time for the retry, as it deserves. 🧘
  • --run-id, --id, --no-run-id — sets a specific run-id. Default: a UUID. 🆔
  • --test-args ARG, --test-args=ARG, --no-test-args — arguments to pass in as @ARGV for all tests that run. And the easy-mode version is using the '::' argument separator. 💅

Can be specified multiple times.

  • --stream, --no-stream — uses the stream formatter. Default is on. Stream it, obviously. 📡
  • --tap, --TAP, ----no-stream, --no-tap — okay so listen. The TAP format is lossy and clunky, no shade to TAP but it's true. Test2::Harness normally uses a newer streaming format to receive test results. But there are old/legacy tests out there where that newer thing causes problems, and in those cases setting --TAP or --no-stream can help. 🛟
Yes, ----no-stream really has four dashes up there. Copy it exactly, bestie. Do not "fix" it. 🙈

✨ YathUI Options ✨

  • --yathui-api-key ARG, --yathui-api-key=ARG, --no-yathui-api-key — your Yath-UI API key. You don't need it if your Yath-UI instance is set to single-user. 🔑
  • --yathui-coverage, --no-yathui-coverage — polls coverage data from Yath-UI to figure out which tests should run for changed files. Smart girl behavior. 👑
  • --yathui-durations, --no-yathui-durations — polls duration data from Yath-UI to help order tests efficiently. Efficiency is a love language. ⏱️
  • --yathui-grace, --no-yathui-grace — normally if yath can't connect to yath-ui it throws an error. Turn this on and it fails gracefully instead: you get a warning, but things keep going. 🦋
  • --yathui-long-duration 10, --no-yathui-long-duration — the minimum duration length, in seconds, before a test graduates from MEDIUM to LONG. Glow-up thresholds. ✨
  • --yathui-medium-duration 5, --no-yathui-medium-duration — the minimum duration length, in seconds, before a test goes from SHORT to MEDIUM. The middle child zone. 🎀
  • --yathui-mode summary, --yathui-mode qvf, --yathui-mode qvfd, --yathui-mode complete, --no-yathui-mode — sets the upload mode. Default is 'qvfd'. That's the one. 💖
  • --yathui-project ARG, --yathui-project=ARG, --no-yathui-project — the Yath-UI project your test results belong to. 🗂️
  • --yathui-retry, --no-yathui-retry — how many times to try an operation before giving up. Persistence, but make it bounded. 💪

Can be specified multiple times.

NO CATEGORY - FIX ME

  • --check-reload-state, --no-check-reload-state — aborts the run if there are unfixes reload errors, and shows a confirmation dialogue for unfixed reload warnings. It is, genuinely, checking on the reload state. 🚨
unfixes and unfixed — that's exactly how it's written in the original, so we are keeping it exactly, no cap.

🌟 SOURCE 🌟

The source code repository for Test2-Harness can be found at http://github.com/Test-More/Test2-Harness/. Go look, bestie, it's all right there. 🫶

👑 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 made it to the end of part three 🎉🦋✨ This came from perl v5.40.1, generated 2026-05-10, and it's the App::Y...nd::run(3pm) page from the User Contributed Perl Documentation. You're officially fluent now. Slay. 💅🌈

📦 where this page comes from