TESTSOLV(1)

🎀 TESTSOLV(1) 🎀

okay so this is the TESTSOLV(1) page from the LIBSOLV manual, and bestie, it's short but it serves. let's go 💅

✨ NAME ✨

testsolv — run a libsolv testcase through the solver 🦋

🌸 SYNOPSIS 🌸

testsolv [OPTIONS] TESTCASE

💖 DESCRIPTION 💖

so like, the testsolv tools let you run a testcase, right? and a testcase can come from two places:

• you can hand-craft one yourself, if you're trying to test some specific feature 👑
• or it can be written by libsolv's testcase_write function ✨

and the whole point? it's so useful for evaluating bug reports about the solver. like, someone files a bug, you turn it into a testcase, you run it, boom. ate. 💅

here's the options, one by one, no skips:

• -v — cranks the debug level of the solver up. and the way that you can pass it multiple times to keep piling on more and more debug data? iconic. specify it again and again, get more and more output, no cap 📈
• -r — writes the output in testcase format instead of human-readable text. why do you care? because that output can then be dropped straight into the result section of the test case 🎀 and if you give the -r option twice, the output gets formatted for verbatim inclusion. two r's, different vibe, iykyk
• -l PKGSPEC — instead of actually running the solver, it just lists the packages in the repositories. like, just show me what's there 👀
• -s SOLUTIONSPEC — this one lives in the solver test suite, and it's for testing the calculated solutions to the problems that got encountered 🧠

fr fr, if you're chasing down a solver bug report, this is the tool. don't skip it.

🌈 AUTHOR 🌈

Michael Schroeder <mls@suse.de> — the icon, the moment, the main character 🫶

and that's the whole page, bestie!! this was libsolv, version dated 03/25/2024, page TESTSOLV(1) — mwah, go run some testcases, you got this 💖🎀✨