aboutsummaryrefslogtreecommitdiff
path: root/tests/common.test
diff options
context:
space:
mode:
authorKaren Arutyunov <karen@codesynthesis.com>2018-05-15 22:32:38 +0300
committerKaren Arutyunov <karen@codesynthesis.com>2018-05-16 11:46:31 +0300
commite771c6b80168de37b74cc57dec502dfa418a19a6 (patch)
tree1d2c8ba68cd1e1331d45cde2fc76d25eee007c08 /tests/common.test
parent1ffe9fa27ee9829c16446a09aa5bd94bcc60ab68 (diff)
Add some more tests
Diffstat (limited to 'tests/common.test')
-rw-r--r--tests/common.test15
1 files changed, 3 insertions, 12 deletions
diff --git a/tests/common.test b/tests/common.test
index 8578f5c..3aefde4 100644
--- a/tests/common.test
+++ b/tests/common.test
@@ -5,25 +5,16 @@
# Commonly-used variables setup and driver command line.
#
-# Variables for supporting Windows/POSIX testscript variants.
-#
-win32 = ($cxx.target.class == 'windows')
-exe = ($win32 ? '.exe' : '')
-
# Use the same build system driver as the one running the tests (as opposed
-# to one that may or may not be found via PATH). This implies that we don't
-# support cross-testing.
+# to one that may or may not be found via PATH). Note that this implies that
+# we don't support cross-testing.
#
# A common approach will be to run build2 as a sanity check in a directory
-# produced/updated by a command being tested.
+# produced or updated by a command being tested.
#
build = $recall($build.path)
test.options += --build $build
-# @@ It would be nice to query bdep for the bpkg path it uses.
-#
-bpkg = ("$config.bdep.test.bpkg" != '' ? "$config.bdep.test.bpkg" : "bpkg$exe")
-
# Helper commands that can be used by tests to prepare the testing environment
# or validate an outcome of the command being tested. They are likely to get
# additional options and redirects appended prior to use. A common approach