-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
-
Labels:None
-
Fully Compatible
-
CAP - 3.1.7
The FSM test suite is now being used for other purposes:
- Powercycle testing
- Backup/restore
It provides very good coverage of many DB operations. One issue that that conflicts wiht these others tests is that as the workloads complete the cleanup drops all databases, including ones not used in the FSM suite. A cleanupOptions object will be used to change the behavior of this cleanup:
- {dropOnlyCreatedDatabases: true}
- {dropDatabaseBlacklist: [] }
If the dropOnlyCreatedDatabases option is false, the behavior remains as is. If true, then the dropAllDatabases will only drop databases that have been created during the FSM testing. This requires another mechanism to register which databases are created.
The second option, dropDatabaseBlacklist, is more straight forward and permits the blacklist to be defined of which databases are not dropped. Note that this extends the existing blacklist from ['admin', 'config', 'local', '$external'].
- related to
-
SERVER-20469 FSM tests - capability to run more than one instance at the same time
- Closed