TAVERN-CI(1)

🦋 NAME 🦋

tavern-ci — the automated API testing bestie you've been waiting for, fr fr. She's a User Commands girlie (that's section 1 of the manual, iykyk), and she is here to test your APIs so you don't have to do it by hand like some kind of Victorian child. 💅

✨ DESCRIPTION ✨

okay so first things first, here's the whole usage vibe, look at her:

usage: tavern-ci [-h] [--log-to-file [LOG_TO_FILE]] [--stdout] [--debug]

       in_file

What she does: parse yaml + make requests against an API. That's the whole personality. 🌈

And here's the tea: any extra arguments you tack on? Those get passed directly to Pytest. Yup, straight through, no notes. So if you wanna know what you can throw at it, run py.test --help and it'll hand you the whole list. 👑

🎀 positional arguments 🎀

• in_file — the input file with your tests in it. This is the one thing she needs, she's not a mind reader bestie. 🍓

🌸 options 🌸

• -h, --help — shows this help message and then dips (exits). That's it, that's the whole job. 💖
• --log-to-file [LOG_TO_FILE] — logs your output to a file. Now if you don't give it an argument? It just goes with tavern.log as the name, no biggie. 🎀
• --stdout — logs the output to stdout. Right there in your terminal, main character energy. ✨
• --debug — logs debug information. ⚠️ But heads up bestie, this one's only relevant if you also passed --stdout or --log-to-file. Alone it's giving nothing, no cap. 😭

not a single flag was harmed in the making of this page, they're all here, all four of them, plus help. 💀

And that's the whole page, bestie! Written under the tavern-ci 3.6.1 glow, dated June 2026, in manual page TAVERN-CI(1) — go forth and let your APIs get tested, slay queen 👑💜🫶