diff options
| author | unknown <guilhem@gbichot3.local> | 2006-09-15 15:15:24 +0200 |
|---|---|---|
| committer | unknown <guilhem@gbichot3.local> | 2006-09-15 15:15:24 +0200 |
| commit | 6e10407c2b34aad5324a13d5f9243c944614d2a5 (patch) | |
| tree | 4a806d99e2eb9e6c98fe6213c4fa5ea9d6402a44 /unittest | |
| parent | aa856526ee6a99fd09c90228617c0534a7c5d076 (diff) | |
| download | mariadb-git-6e10407c2b34aad5324a13d5f9243c944614d2a5.tar.gz | |
WL#3504 "plugin actions for engines' and plugins' unit tests"
for push in 5.1 (I will inform Trudy).
Storage engines and plugins can now have unit tests to test their components; such
test must be an executable C/C++ program which name ends with '-t' and which is
obeys the mytap protocol, it must be stored in the storage engine's or plugin's
source directory (storage/<engine> or plugin/<plugin>) or any subdirectories of
this.
The top-level Makefile target "test-unit" will run all unit tests: it will scan
the engines' and plugins' directories, recursively, and execute all executable
files which name ends with '-t'."
Makefile.am:
"unittest" directory must be built before "storage" and "plugin"
because the unit tests in these directories may need libmytap.a
which is in unittest/mytap.
config/ac-macros/plugins.m4:
When enabling engine "X", we add "../storage/X" to the unit tests
directories which unittest/unit.pl should traverse looking for
tests to execute. Same for plugins.
unittest/Makefile.am:
Those variables contain all enabled engines and plugins.
Diffstat (limited to 'unittest')
| -rw-r--r-- | unittest/Makefile.am | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/unittest/Makefile.am b/unittest/Makefile.am index f2f7fc0bf7d..7f1dd525d3b 100644 --- a/unittest/Makefile.am +++ b/unittest/Makefile.am @@ -3,7 +3,7 @@ SUBDIRS = mytap . mysys examples EXTRA_DIST = unit.pl CLEANFILES = unit -unittests = mytap mysys +unittests = mytap mysys @mysql_se_unittest_dirs@ @mysql_pg_unittest_dirs@ test: perl unit.pl run $(unittests) |