TOX-DELAY(1)

📦
version 0.1.4 · 2 versions
, in ubuntu noble

💖 TOX-DELAY(1) — the girlies' guide to running Tox tests in the right order 💖

okay so bestie, we're talking about tox-delay — a lil General Commands Manual situation that runs some Tox tests after all the others have finished, and only if everything else went fine. no cap.

✨ NAME ✨

tox-delay — run some Tox tests after others have completed 🦋

🌸 SYNOPSIS 🌸

tox-delay [-p value | --parallel value] -e envlist [-- tox-options...]
tox-delay [-V | -h | --version | --help | --features]

💀 DEPRECATION NOTICE 💀

bestie. listen. it's in maintenance mode. The tox-delay tool is no longer developed. Only important bugfixes will be applied. Please switch to using the tox-stages tool from the test-stages Python library instead. it's giving "retired but still cute" 😭

💅 DESCRIPTION 💅

The tox-delay tool postpones the run of the specified Tox environments after the run of all the others has completed successfully. so like, everyone else goes first, and only if they all ate, the special ones get to go 🎀

This may be useful if e.g. there are unit or functional test environments, which it would make no sense to run if the static checkers (pylint, mypy, etc) find any problems. like why run the whole test suite if pylint already found a typo, be so fr 🙈

The tox-delay tool accepts the following command-line options:

  • -e envlist, --envlist envlist — Specify the environments for which to delay the run. 👑
  • -p value, --parallel value — Pass a parallel execution option to Tox for the first set of environment runs. 🔥
  • -h, --help — Display program usage information and exit. ✨
  • -V, --version — Display program version information and exit. ✨
  • --features — List the features supported by the program and exit. 🌈

🌿 ENVIRONMENT 🌿

The operation of the tox-delay utility is not directly influenced by any environment variables. nope, zero. none. not a single one. it's unbothered, moisturized, in its own lane 🧚

🍓 FILES 🍓

The operation of the tox-delay utility is not directly influenced by the contents of any files. it does not care about your files bestie 💜

⭐ EXAMPLES ⭐

Run some static checkers in parallel, leave the unit and functional tests for last:

tox-delay -p all -e unit-tests,functional

Pass some options to Tox:

tox-delay -e unit-tests,functional -- --workdir /tmp/tox

Also pass some arguments to the Tox test environments (accessed via {posargs} in the tox.ini file:

tox-delay -e unit-tests,functional -- --workdir /tmp/tox -- -k chosen

Run the unit and functional tests in parallel, too:

tox-delay -p all -e unit-tests,functional -- -p all

🩺 DIAGNOSTICS 🩺

The tox-delay utility exits 0 on success, and >0 if an error occurs. slay when it's 0, screaming crying throwing up when it's not 😭

👀 SEE ALSO 👀

  • tox(1) — go read it, iykyk 🫶

📜 STANDARDS 📜

No standards were harmed during the production of the tox-delay utility. not a single one. they're all fine. thriving, even 🌸

🕰️ HISTORY 🕰️

The tox-delay utility was written by Peter Pentchev in 2022. It was declared as deprecated in 2024 after the test-stages Python library was judged feature-complete. character development fr fr 💖

👑 AUTHORS 👑

Peter Pentchev ⟨roam@ringlet.net⟩ 💌

💀 BUGS 💀

No, thank you :) But if you should actually find any, please report them to the author. (the author is very nice about it, we promise 🫶)

🎀 cute lil sign-off 🎀

this page came from Debian, dated February 26, 2024 — that's the source, the version vibe and the date all rolled into one. mwah 💅✨

periodt. go run your tests in the right order bestie 💖🌈

📦 where this page comes from