summaryrefslogtreecommitdiff
path: root/build2/test/list
diff options
context:
space:
mode:
Diffstat (limited to 'build2/test/list')
-rw-r--r--build2/test/list10
1 files changed, 10 insertions, 0 deletions
diff --git a/build2/test/list b/build2/test/list
new file mode 100644
index 0000000..58b23c7
--- /dev/null
+++ b/build2/test/list
@@ -0,0 +1,10 @@
+- Incremental tests: only run tests that were updated [idea]
+
+ If a test is more than an executable, then tracking its "inputs" (so that we
+ know whether to run it) will be tricky. Such a test will most likely run via
+ testscript so can we capture inputs somehow? This seems to be related to the
+ question of what to attach testscripts to. Maybe we should make them (in
+ source) targets?
+
+ Will also need some kind of switch/override to run all tests (command line
+ config override seems like a natural choice).