LIFT(1)

📦
version 2.6.2 · 2 versions
, in debian trixie, ubuntu resolute, ubuntu stonking

✨ LIFT(1) ✨

okay bestie, welcome to the lift manual page (that's the "1" — it means user commands, iykyk) 💅 Grab a snack, we're gonna run some tests together 🧚

🌸 NAME 🌸

lift — run a Lift test suite, bestie 🫶

🦋 SYNOPSIS 🦋

lift [OPTION]... [TEST]...

✨ DESCRIPTION ✨

So like. The lift command runs all of a Lift test suite, or just parts of it — your call, main character 💖 By default, with no option at all, lift runs all the tests it discovers in the current directory and its sub-directories. Sneaky little explorer. It finds everything. Obsessed. 🔥

And for the lore: Lift stands for Lift Integration-Functional Testing. Iconic acronym, no cap. 👑

🎀 OPTIONS 🎀

  • -h, --help — shows you a help message and then dips out. exit. bye. 👋
  • -V, --version — tells you which version of lift you've got. vibe check on your install ✨
  • -q, --quiet — does NOT print the output of tests as they run. Silent. Stealth mode. 🤫
  • -d, --detailed-summary — prints the output of the failed tests in the final summary. so you know exactly what went wrong 😭
  • -n, --no-color — turns off the colored output. Maybe useful, like, for example if colors are messing with your terminal 💀
  • --regex — processes TEST strings as standard Python regex. There's more deets below, keep scrolling bestie 👇
  • --no-upper-inheritance — does NOT load remotes/environment from upper-level lift.yaml files. By default lift goes looking for lift.yaml files in upper-level folders so it can find settings to inherit for the current test file. This option disables that whole behavior and treats the current test directory as a top-level one. Cutting the family off, respectfully. 🙈
  • --put-remotes-in-environment — every defined remote gets passed to the tests as an environment variable, in this exact form: LIFT_REMOTE_remotename=login:password@host. Note that the password (and its ":" separator) won't be there at all if it wasn't defined in the first place. SECURITY WARNING: do NOT use this option if some of your binary tests can't be trusted to keep those credentials to themselves. Like, fr fr, this one is serious. 🔒
bestie. the credentials one. be careful. that's it, that's the note. 💜
  • -f FOLDER, --folder FOLDER — specify the root folder that tests will be looked for in. Defaults to the current working directory. 📁
  • -r REMOTE, --remote REMOTE — define a remote. The value should be in the form: REMOTENAME=USERNAME:PASSWORD@HOST. Note that the PASSWORD field (along with the ":" separator) is optional if SSH keys are properly set up — queen behavior, honestly 🔑 You can use this option multiple times to define multiple remotes. And remotes defined via this option supersede those defined via lift.yaml files. this one wins, periodt. 👑
  • --with-xunit — gives you the test results in the standard XUnit XML format 📄
  • --xunit-file XUNIT_FILE — specifies the path of the XML file where the XUnit report gets stored. The default is lift.xml in the current working directory. 🗂️

🌈 RUN SPECIFIC TESTS 🌈

You can pick specific tests to run right there on the command line, no big deal 💅 Just use the test string format that shows up in the normal lift output, like:

"FOLDER/TEST_NAME"

If you set the --regex option, expressions get matched as standard Python regex. For example, .*foo will match all tests containing the word "foo". cute right 🍓

Head to <http://docs.python.org/library/re.html> for more info on the Python regex syntax, if you wanna go full nerd mode (we love that here) 📚✨

💜 SEE ALSO 💜

For the test suite definition, see lift.yaml (1) 🦋

⭐ AUTHOR ⭐

Written an maintained by Nicolas Delvaux <contact@nicolas-delvaux.org> 🫶 (yes, "an" — that's how it's written, and we respect the original ✨)

GPL2+ 📜

and that's the whole page bestie!! mwah 💖 this was the Lift Manual, version 2.5.0 — go run some tests and slay 💅🌸✨

📦 where this page comes from