From a3a07e76263db6a2ecc44865fb92107e672a109b Mon Sep 17 00:00:00 2001 From: Karen Arutyunov Date: Wed, 16 Jan 2019 13:20:33 +0300 Subject: Use `b info` command to check if package project/subprojects can be tested --- doc/manual.cli | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'doc/manual.cli') diff --git a/doc/manual.cli b/doc/manual.cli index c0d9b35..6865f1c 100644 --- a/doc/manual.cli +++ b/doc/manual.cli @@ -778,6 +778,8 @@ bpkg -v build --yes --configure-only / # bpkg -v update +# if the test operation is supported by the package: +# # bpkg.test.test # bpkg -v test @@ -789,7 +791,7 @@ bpkg -v test # bpkg -v install - # if package contains tests/ subproject: + # if the package contains subprojects that support the test operation: # { # b.test-installed.create @@ -950,10 +952,10 @@ linux*-gcc_8 linux-gcc_8 x86_64-linux-gnu \"all gcc-8+:gcc-7+\" If the \c{} list contains the \c{config.install.root} variable that applies to the \c{bpkg.configure.create} step, then in addition to -building and running tests, the \c{bbot} worker will also test installing and -uninstalling each package. Furthermore, if the package contains the \c{tests} -subdirectory that is a subproject, then the worker will additionally build and -run tests against the installation. +building and possibly running tests, the \c{bbot} worker will also test +installing and uninstalling each package. Furthermore, if the package contains +subprojects that support the test operation, then the worker will additionally +build such subprojects against the installation and run their tests. Two types of installations can be tested: \i{system} and \i{private}. A system installation uses a well-known location, such as \c{/usr} or \c{/usr/local}, -- cgit v1.1