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

📦
version 1.000172 · 8 versions
, in ubuntu stonking

🦋 App::Y...::abort(3pm) — User Contributed Perl Documentation

okay bestie, gather round, because this is the page for App::Yath::Command::abort 💅 and yeah it's filed under the 3pm manual section because it's Perl documentation. we're doing this in parts, so buckle up 🎀

✨ NAME ✨

App::Yath::Command::abort — abort all currently running or queued tests without killing the runner 🛑

🌸 DESCRIPTION 🌸

So like, this command? It kills all running tests and clears the queue. that's it, that's the job. but the runner stays alive — it does not close the runner. main character behaviour honestly, it just clears the room without leaving the party 💅

💖 USAGE 💖

$ yath [YATH OPTIONS] abort [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, because it makes sure the yath script finds your local code instead of the installed versions of the same code. you can pass an argument (-Dfoo) to give 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 it falls back to the current directory. and if the current directory isn't writable, it defaults to /tmp/yath-persist.json — which lowkey limits you to one persistent runner on your whole system 😭
  • --project ARG, --project=ARG, --project-name ARG, --project-name=ARG, --no-project — this lets you slap a label on your current project/codebase. best used in a .yath.rc file. and ngl, it's necessary for a persistent runner. periodt.

🔥 Finder Options

  • --finder MyFinder, --finder +Test2::Harness::Finder::MyFinder, --no-finder — specify what Finder subclass to use when searching for files / processing the file list. use the + prefix to give a fully qualified namespace, otherwise the Test2::Harness::Finder::XXX namespace is assumed. ✨

🎀 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 command-line options they may provide. this flag disables that. super useful if you have a naughty plugin that's 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 😭 (not my fault bestie, that's literally what the page says)

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) 🔥
  • --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. 👑 and heads up: 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 can't, 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 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 as above: 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 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 it auto-detects 🌸
  • --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 — don't do fancy text-wrapping, just 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 the 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:: gets 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 overrides the terminal width detection to the number of characters you specify. 📐
  • --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, and also requires a list of changes either from the --changed option, or from 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 gets 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 limits which files are checked for changes — only files that match this pattern will be checked. your pattern gets 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

more coming bestie, don't go anywhere 💅

  • --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 totally overrides the durations listed in the file headers. And bestie, if that durations file or url doesn't work? an exception gets thrown. No soft landing, no apology, just 💀.
  • --durations-threshold ARG, --durations-threshold=ARG, --Dt ARG, --Dt=ARG, --no-durations-threshold — only goes and fetches duration data if you're running at least this many tests. Default is -j value + 1. Like, if it's not worth the fetch, we're not fetching. 💅
  • --exclude-file t/nope.t, --no-exclude-file — yeet a single file out of 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 new-line-separated list of test file names to exclude from testing. Start a line with a # and it gets commented out (this is 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 url with a hash of relative test filenames as keys and 'SHORT', 'MEDIUM', or 'LONG' as values. It overrides durations listed in the file headers. An exception will be thrown if the durations file or url does not work. Same energy as --durations, just with ✨maybe✨ in the name.
  • --no-long, --no-no-long — do not run tests whose duration flag is set to 'LONG'. Skip the long ones, we're busy. 🏃‍♀️
  • --only-long, --no-only-long — only run tests whose duration flag is set to 'LONG'. Long-haul girlies, this one's for you. 👑
  • --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 — like YathUIDB, which will grab a run UUID and derive 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 tests from a previous run, from a log file (or the last log file). Plugins can intercept this, YathUIDB included — it'll grab a run UUID and derive the 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 it, like YathUIDB grabbing a run UUID and deriving the tests from that. 😭
  • --rerun-missed, --rerun-missed=path/to/log.jsonl, --rerun-missed=plugin_specific_string, --no-rerun-missed — run the tests that got missed from a previously aborted/stopped run, taken from a log file (or the last log file). Plugins can intercept this too — YathUIDB will grab a run UUID and derive the 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 tests that passed from a previous run, from a log file (or the last log file). Plugins can intercept this, such as YathUIDB, which grabs a run UUID and derives the 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 retried tests from a previous run, from a log file (or the last log file). Plugins can intercept this — YathUIDB will grab a run UUID and derive 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 at all. 🫶

Can be specified multiple times 🙈

  • --show-changed-files, --no-show-changed-files — print a list of changed files if any are found. Vibe check on your git status, basically. 🌈

✨ Formatter Options ✨

  • --formatter ARG, --formatter=ARG, --no-formatter — NO DESCRIPTION - FIX ME 💀 (yes bestie, that's literally what the page says, I'm not making it up)
  • --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 output from that test gets verbosely output. 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 commits in the current branch, going from most recent and stopping when you hit a commit that's also present in the history of the branch/commit you named as the change base. It's giving "what did we touch since then" energy. 🧚

💅 Help and Debugging 💅

  • --dummy, -d, --no-dummy — dummy run, do not actually execute anything. (Also settable with the environment variable "T2_HARNESS_DUMMY")
  • --help, -h, --no-help — exit after showing help information. Bye bestie 🫶
  • --interactive, -i, --no-interactive — use interactive mode, one test at a time, with stdin forwarded to it. Just you and the test, one on one. 💖
  • --keep-dirs, --keep_dir, -k, --no-keep-dirs — do not delete directories when done. Super useful if you want to go poke around 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). So ps knows who's who. 👑
  • --summary, --summary=/path/to/summary.json, --no-summary — write out a summary json file. If you don't give a path, 'summary.json' gets used. And heads up, 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. If you don't, it falls 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. This gets overridden by --log-file, if that's 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 will be replaced as per POSIX::strftime. The following special escape sequences are also replaced:
    • (%!P : Project name followed by a ~, if a project is defined, otherwise 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 at all, this is who it'll be from.
  • --notify-email-owner, --no-notify-email-owner — email the owner of broken test files when they fail. 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 go out as a single batch at the end of testing. Toggle this to send failures as they happen instead. 🏃‍♀️
  • --notify-no-batch-slack, --no-notify-no-batch-slack — usually owner failures go out as a single batch at the end of testing. Toggle this to send failures as they happen instead.
  • --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 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 your email/slack notifications. A lil personal touch 🎀
  • --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 — ok so this one just sets the AUTHOR_TESTING environment variable to true. that's it. that's the entire job. she's simple, she's effective 💅
  • --dbi-profiling, --no-dbi-profiling — pulls in Test2::Plugin::DBIProfile so you get database profiling data collected for the whole run. numbers about your database? obsessed. 🍓
  • --env-var VAR=VAL, -EVAR=VAL, -E VAR=VAL, --no-env-var — hands you a way to set environment variables that get applied when each test is run. can be specified multiple times, no cap ✨
  • --event-uuids, --uuids, --no-event-uuids — runs Test2::Plugin::UUID inside tests (default: on). literally free tracking, bestie 🦋
  • --fields name:details, --fields JSON_STRING, -f name:details, -f JSON_STRING, --no-fields — adds custom data to the harness run. can be specified multiple times. put your little details in there, she'll hold them 💖
  • --input ARG, --input=ARG, --no-input — an input string that gets used as standard input for ALL tests. see also --input-file (they're besties, iykyk)
  • --input-file ARG, --input-file=ARG, --no-input-file — points at a file to use as standard input for ALL tests. all of them. every single one. 🫶
  • --io-events, --no-io-events — uses Test2::Plugin::IOEvents inside tests, which turns all your prints into test2 events (default: off). it's giving ~everything is a test event now~ 🌸
  • --link 'https://travis.work/builds/42', --link 'https://jenkins.work/job/42', --link 'https://buildbot.work/builders/foo/builds/42', --no-link — provides one or more links that people can follow to see more about this run. can be specified multiple times. drop the receipts, queen 👑
  • --load ARG, --load=ARG, --load-module ARG, --load-module=ARG, -m ARG, -m=ARG, --no-load — loads a module in each test (after fork). quick note: the import method is not called. can be specified multiple times. very demure, very mindful 🌈
  • --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 — loads a module in each test (after fork), and this time import is called. can be specified multiple times. if the same key is listed more than once, the value lists get appended together ✨
  • --mem-usage, --no-mem-usage — uses Test2::Plugin::MemUsage inside tests (default: on). watching the memory go up in real time 😭
  • --retry ARG, --retry=ARG, -r ARG, -r=ARG, --no-retry — runs any jobs that failed a second time. ⚠️ NOTE: --retry=1 means failing tests will be attempted twice! count carefully bestie, this math is sneaky 💀
  • --retry-isolated, --retry-iso, --no-retry-isolated — if true, then any job retries happen in isolation (as though -j1 was set). alone time. hermit mode. 🧚
  • --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 are run. these can be provided easier using the '::' argument separator. can be specified multiple times.
  • --stream, --no-stream — uses the stream formatter (default is on). ✨
  • --tap, --TAP, ----no-stream, --no-tap — okay so real talk: the TAP format is lossy and clunky. Test2::Harness normally uses a newer streaming format to receive test results. there are old/legacy tests where this causes problems, and in those cases setting --TAP or --no-stream can help. 🙈

✨ YathUI Options ✨

  • --yathui-api-key ARG, --yathui-api-key=ARG, --no-yathui-api-key — your Yath-UI API key. you do not need this if your Yath-UI instance is set to single-user 💜
  • --yathui-coverage, --no-yathui-coverage — polls coverage data from Yath-UI to figure out what tests should be 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 the vibe 💅
  • --yathui-grace, --no-yathui-grace — normally, if yath cannot connect to yath-ui it throws an error. use this and it fails gracefully instead. you still get a warning, but things keep going 🔥
  • --yathui-long-duration 10, --no-yathui-long-duration — the minimum duration length (in seconds) before a test goes from MEDIUM to LONG ⭐
  • --yathui-medium-duration 5, --no-yathui-medium-duration — the minimum duration length (in seconds) before a test goes from SHORT to MEDIUM ⭐
  • --yathui-mode summary, --yathui-mode qvf, --yathui-mode qvfd, --yathui-mode complete, --no-yathui-mode — sets 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. persistence!!! periodt 🫶
  • --yathui-upload, --no-yathui-upload — uploads the log to Yath-UI ☁️
  • --yathui-url http://my-yath-ui.com/..., --uri http://my-yath-ui.com/..., --no-yathui-url — the Yath-UI url 🔗

🌈 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. ⚠️ note that this one literally says "FIX ME" up there in the section title, so, like, she's aware 😭

📦 SOURCE 📦

the source code repository for Test2-Harness lives at http://github.com/Test-More/Test2-Harness/ — go look, go star, go vibe 🧚

👑 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, we ate and left no crumbs 🎀 this was perl v5.40.1, dated 2026-05-10, and you just read App::Y...::abort(3pm) — iconic behavior, go run your tests 👑✨

📦 where this page comes from