-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
It needs to be easier to implement tests of individual modules, and get those tests executed by the automated build framework. We may already have some of the requisite parts on hand, or could get them by making small modifications to existing systems. Other parts may require (or deserve) significant development effort.
Features of such a system include:
- Ability to write tests in C++ of individual C++ classes/minor components.
- Quick compile and linking time of such tests (for dev-test cycle).
- Ability to identify those tests to the automated test system, for execution during automated build.
- Ability to write tests in a scripting language (python?) when that is a more appropriate way to test module functionality (i.e., testing crash/abend paths).
- is related to
-
SERVER-5998 smoke.py should consult build/unittests.txt to figure out what tests to run.
- Closed
- related to
-
SERVER-13576 Add lightweight instrumentation 'probes' for unit tests
- Closed