[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[cme-dev] AllTests test suites
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
just a minor issue that I stumbled upon while going through some of the
CME test cases to get a better idea of what is tested and how.
I have found various versions of this test type. Some AllTests suites
explicitly name the TestCases to be executed, some list TestSuites to be
executed (often in other projects), some execute a query on the
classpath to find all suitable test cases.
All manual approaches are, of course, prone to error since it is
possible to forget to add a test case to the suite.
If there is interest in changing the structure in the suites to
automatically scan directories for suitable test cases, I'd do that quickly.
This unification would also allow for quicker instantiation of
structures like this:
org.eclipse.a
org.eclipse.a.test
org.eclipse.a.b
org.eclipse.a.b.test
...
which keep the test "closer" to the tested classes but are a pain to
write when you have to add them manually to a suite.
The current classes I have for this (wrote them ages ago) do only scan
from one root directory down, so the "suite calls suite" would coexist
with the "scan all below 'bin' and find all suitable test cases"
scenario. If required, an extended version that scans a number of
projects would be easy to write, though.
Juri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCVUQBdlXiXRccbPMRAjiZAJ9vKhn8SPntFklRDr1pCUVcyQGAqgCfYRij
vaK8YPeqiEMAZlqc4w9j4uw=
=20lB
-----END PGP SIGNATURE-----
