bdep-test(1)

💖 bdep-test(1) — General Commands Manual 💖

okay bestie, welcome to bdep-test, part of the bdep family of manual pages 🫶 pull up a chair, grab a boba, and let's get into it.

---

✨ NAME ✨

bdep-test — test project in build configurations 💅

---

🎀 SYNOPSIS 🎀

bdep test [options] [pkg-spec] [cfg-spec] [cfg-var...]

cfg-spec = (@cfg-name | --config|-c cfg-dir)... | --all|-a
pkg-spec = (--directory|-d pkg-dir)... | prj-spec
prj-spec = --directory|-d prj-dir

---

🌸 DESCRIPTION 🌸

So the test command tests the project packages in one or more build configurations. Iconic. And here's the tea: you can also test the immediate or all dependencies of the project packages by passing --immediate|-i or --recursive|-r, respectively. Two little flags, so much power 🔥

Underneath, test executes the bpkg-pkg-test(1) command, which itself is not much more than the build system test operation (peep b(1) for the details, iykyk). So the real main character energy of this command is that it lets you refer to build configurations by names and to project packages implicitly via the current working directory — plus it tests dependencies for you. Chef's kiss 👑

If no project or package directory is specified, then the current working directory is assumed. No cap. And if no configuration is specified, then the default configurations are assumed. Wanna know the details on specifying projects and configurations? Go read bdep-projects-configs(1), bestie 📖 Optional cfg-var... are the additional configuration variables to pass to the build system.

---

✨ TEST OPTIONS ✨

• --immediate, -i — Also test immediate dependencies. like, just the close ones 🫶
• --recursive, -r — Also test all dependencies, recursively. the whole friend group, everyone gets tested 💜
• --all, -a — Use all build configurations. all of them. periodt.
• --config, -c dir — Specify the build configuration as a directory.
• --directory, -d dir — Assume project/package is in the specified directory rather than in the current working directory. (not me being in the wrong folder 😭)
• --config-name, -n name — Specify the build configuration as a name.
• --config-id num — Specify the build configuration as an id.

---

💖 COMMON OPTIONS 💖

These are the common options, summarized below with a more detailed description available in bdep-common-options(1) ✨

• -v — Print essential underlying commands being executed. lowkey spy mode 👀
• -V — Print all underlying commands being executed. highkey spy mode, full transparency 🌈
• --quiet, -q — Run quietly, only printing error messages. shhh 🤫
• --verbose level — Set the diagnostics verbosity to level between 0 and 6.
• --stdout-format format — Representation format to use for printing to stdout.
• --jobs, -j num — Number of jobs to perform in parallel.
• --progress — Display progress indicators for long-lasting operations, such as network transfers, building, etc. the little bars, we love them 🍓
• --no-progress — Suppress progress indicators for long-lasting operations, such as network transfers, building, etc.
• --diag-color — Use color in diagnostics. 🌈
• --no-diag-color — Don't use color in diagnostics. 💀
• --bpkg path — The package manager program to be used for build configuration management.
• --bpkg-option opt — Additional option to be passed to the package manager program.
• --build path — The build program to be used to build packages.
• --build-option opt — Additional option to be passed to the build program.
• --curl path — The curl program to be used for network operations.
• --curl-option opt — Additional option to be passed to the curl program.
• --pager path — The pager program to be used to show long text.
• --pager-option opt — Additional option to be passed to the pager program.
• --options-file file — Read additional options from file.
• --default-options dir — The directory to load additional default options files from.
• --no-default-options — Don't load default options files.

---

🦋 DEFAULT OPTIONS FILES 🦋

Go read bdep-default-options-files(1) for the full overview of the default options files, bestie. For the test command specifically, the search start directory is the project directory 📁✨

These are the options files that get searched for in each directory, and if found, loaded in the order listed:

bdep.options
bdep-test.options

And the following test command options cannot be specified in the default options files:

• --directory, -d

bestie this is a whole vibe check: those default options files simply do not get to decide --directory|-d for you. nope. 🙈

---

💀 BUGS 💀

Send bug reports to the users@build2.org mailing list 📧

---

👑 COPYRIGHT 👑

Copyright (c) 2014-2024 the build2 authors.

Permission is granted to copy, distribute and/or modify this document under the terms of the MIT License.

---

and that's the whole page, bestie 💖 this was bdep version 0.17.0, dated June 2024, and it's the bdep-test(1) manual page, fr fr. slay, go test something ✨🎀🦋