NOSE2-3(1)
π NOSE2-3(1) π
okay bestie, welcome to nose2-3 β yes that's the whole NAME section, it's literally just its own name, main character energy fr. Let's get into it π«Ά
β¨ DESCRIPTION β¨
so here's the vibe, the usage goes a lil something like this:
usage: nose2 [-s START_DIR] [-t TOP_LEVEL_DIRECTORY] [--config [CONFIG]]
[--no-user-config] [--no-plugins] [--plugin PLUGINS]
[--exclude-plugin EXCLUDE_PLUGINS] [--verbosity VERBOSITY]
[--verbose] [--quiet] [--log-level LOG_LEVEL] [-B] [--coverage
PATH] [--coverage-report TYPE] [--coverage-config FILE] [-C] [-D]
[-F] [--pretty-assert] [-h] [testNames [testNames ...]]
πΈ positional arguments πΈ
testNamesβ the test names you wanna run. that's it, that's the whole job π
π optional arguments π
-s START_DIR,--start-dir START_DIRβ the directory where discovery kicks off. defaults to'.'bestie, she starts right where you're standing.-t TOP_LEVEL_DIRECTORY,--top-level-directory TOP_LEVEL_DIRECTORY,--project-directory TOP_LEVEL_DIRECTORYβ the top level directory of your project. if you don't say anything, it just defaults to the start dir, lowkey effortless.--config [CONFIG],-c [CONFIG]β config files to load, if they exist. and the defaults?'unittest.cfg'and'nose2.cfg'sitting in the start directory. iconic behavior honestly.--no-user-configβ do NOT load user config files. not today.--no-pluginsβ do not load ANY plugins. π¨ but like, real talk: Warning: nose2 does not do anything if no plugins are loaded. so yeah. it's giving "i'm nothing without my plugins". don't do this unless you know what you're doing.--plugin PLUGINSβ load this plugin module. yes queen, load her up.--exclude-plugin EXCLUDE_PLUGINSβ do not load this plugin module. sorry babe, not you.--verbosity VERBOSITYβ set the starting verbosity level as an int. and listen, this applies before-vand-q, so it's the opening act, not the headliner.--verbose,-vβ prints test case names and statuses. and the way that you can stack multiple'-v's for higher verbosity?? obsessed. go off, add more.--quiet,-qβ reduces verbosity. multiple'-q's = lower and lower verbosity. shhh π€«--log-level LOG_LEVELβ sets the logging level for messages logged to the console.-h,--helpβ show this help message and dip. classic.
π plugin arguments π
these are the command-line arguments added by plugins, aka the glow-ups:
-B,--output-bufferβ enable output buffer. buffering ON β¨--coverage PATHβ measure coverage for a filesystem path. and you can pass it more than once, multi-allowed bestie π«Ά--coverage-report TYPEβ generate selected reports. available types are:term,term-missing,annotate,html,xml. also multi-allowed, collect 'em all.--coverage-config FILEβ config file for coverage. default is:.coveragerc-C,--with-coverageβ turn on coverage reporting. periodt.-D,--debuggerβ enterpdbon test fail or error. dropping straight into the debugger, no cap.-F,--fail-fastβ stop the test run after the first error or failure. no second chances, we're moving on π--pretty-assertβ add pretty output for"assert"statements. make your failures cute, you deserve it π
also just a lil reminder from me to you: --no-plugins means nose2 does literally nothing. like, nothing nothing. so maybe don't βπ
and that's the whole page, bestie!! this was nose2-3 0.9.2-1, dated September 2020 β thank you for coming to my ted talk, ily, go run your tests πβ¨π¦π
π¦ where this page comes from
- ubuntu jammy: python3-nose2 0.9.2-1 Β· BSD-2-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms