Skip to content

Latest commit

 

History

History
120 lines (73 loc) · 4.11 KB

Run_Subcommand.rst

File metadata and controls

120 lines (73 loc) · 4.11 KB
Raw

Running Test with buildtest (_buildtest run)

.. program-output:: cat scripts/Run_Subcommand/help.txt

Interactive Testing (_buildtest run --interactive)

buildtest comes with a menu driven test that can be used as an alternate method to ctest. Just run _buildtest run --interactive after you created a few tests and follow the prompt to navigate to the appropriate test

.. program-output:: cat scripts/How_to_use_buildtest/runtest.txt

Running Individual Tests (_buildtest run --testname)

You may run individual tests via buildtest using option --testname.

(buildtest-0.5.0) [siddis14@adwnode1 buildtest-framework]$ _buildtest run --testname  /tmp/buildtest-tests/system/gcc/which__usr_bin_gcc.sh
Executing Test: /tmp/buildtest-tests/system/gcc/which__usr_bin_gcc.sh >/dev/null 2>&1
---------------------------------------------------------
Test Successful
---------------------------------------------------------

Run an Application Test Suite (_buildtest run --software)

buildtest can run test written in $BUILDTEST_TESTDIR for a particular application specified by option --software. The choice field for this option is populated based on directories found in $BUILDTEST_TESTDIR which were created by subsequent runs of _buildtest build -s <application>.

(buildtest) [siddis14@adwnode11 buildtest-framework]$ ./_buildtest run --software
GCC/6.4.0-2.28             GCCcore/6.4.0              Perl/5.26.0-GCCcore-6.4.0

Shown below is an output of _buildtest run --software GCCcore/6.4.0 which attempts to run all tests for application GCCcore/6.4.0

.. program-output:: tail -n 15 scripts/Run_Subcommand/app_GCCcore.txt

Run a System Package Test Suite (_buildtest run --package)

Similarly, buildtest run --package is used to run test suite for system packages that were built by option _buildtest build --package <package>

Shown below is an output of _buildtest run --package gcc

.. program-output:: cat scripts/Run_Subcommand/systempkg_gcc.txt

Running tests via CTest

buildtest is setup automatically to run ctest utility. In order to use ctest you should try to create an empty directory relative to $BUILDTEST_TESTDIR. Assuming $BUILDTEST_TESTDIR is /tmp/buildtest-tests then you can do the following

mkdir -p /tmp/build
cd /tmp/build
cmake ..

The output from cmake should look something like this

.. program-output:: cat scripts/Run_Subcommand/cmake-build.txt

There should be a file /tmp/CMakeLists.txt generated by buildtest which is used to find all subdirectories in BUILDTEST_TESTDIR to get ctest to find and run all the tests.

cmake will generate some make files in /tmp/build then you can run the test by running the following

ctest .

Note

You want to make sure you run ctest . in the build directory since ctest will generate bunch of scripts in the directory you ran cmake

.. program-output:: cat scripts/Run_Subcommand/run-GCCcore-6.4.0.txt

Output Test Results (--output)

By default output of test is disabled when using _buildtest run command. To enable output specify --output yes when running a test to view the output to STDOUT.

Example below illustrates when output is enabled.

(buildtest) [siddis14@adwnode1 buildtest-framework]$ _buildtest run -t /tmp/buildtest-tests/ebapp/GCCcore/6.4.0/hello.c.sh --output yes
Executing Test: /tmp/buildtest-tests/ebapp/GCCcore/6.4.0/hello.c.sh >/dev/stdout 2>&1
---------------------------------------------------------
hello world

Test Successful
---------------------------------------------------------

This option can work with other run options like --software, --package, --all-software and --all-package