Use `b info` command to check if package project/subprojects can be tested

1 files changed, 7 insertions, 5 deletions

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 <package-name>/<package-version>
 #
 bpkg -v update <package-name>
 
+# if the test operation is supported by the package:
+#
 # bpkg.test.test
 #
 bpkg -v test <package-name>
@@ -789,7 +791,7 @@ bpkg -v test <package-name>
   #
   bpkg -v install <package-name>
 
-  # 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{<config-arg>} 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},