TAPPY(1)

✨ NAME ✨

okay so bestie, this is the manual page for tappy — a tap consumer for python 💅

---

🌸 SYNOPSIS 🌸

tappy [options] <pathname> [<pathname> ...]

---

🦋 DESCRIPTION 🦋

So like, the tappy command takes all the tap files you hand it as *pathname*s and eats them, then spits out output that looks basically like what the regular text test-runner from python's unittest module would give you. iconic behavior tbh.

And listen — if a pathname points to a directory, tappy will go rummaging around in that directory looking for *.tap files to consume. she's thorough like that 🕵️‍♀️

Here's the vibe: say you've got a tool that consumes the unittest regular output, but you're lowkey wishing you could use the TAP protocol to better integrate with other tools?? yeah. you can use tappy to replay tests from .tap files, without having to actually run the tests again. and that is much faster, no cap. ⚡

She's also an example of how to use the tap consumer API provided by the tap module, iykyk. 💖

⚠️ WARNING ⚠️

tappy's output will differ from the standard unittest output. for real. indeed it cannot reproduce error and failure messages (e.g. stack traces, ...) that are not recorded in tap files. so like, if it's not in the tap file, it's simply not there, bestie 😭 don't come for her.

---

💅 OPTIONS 💅

• -h, --help — show a short description and option list, then exit. cute lil escape hatch 🚪
• -v, --verbose — produce verbose output. she will tell you everything 🗣️

---

👑 AUTHOR 👑

The tappy and the tap modules were written by Matt LAYMAN (https://github.com/python-tap/tappy). 🫶

This manual page was written Nicolas CANIART, for the Debian project.

---

🎀 COPYRIGHT 🎀

Matt Layman and contributors

---

and that's the whole page, bestie — version 3.2.1, dated Jan 30, 2025 🌈 happy tapping, mwah 💖✨