The FSM test suite is now being used for other purposes:

• Powercycle testing
• Backup/restore
• Upgrade/downgrade

It provides very good coverage of many DB operations.

Issues that limits invoking the suite to run against a MongoDB cluster more than one at a time include:

• Database names may conflict
  • Some database names are created in the workload, others are assigned from a global function
• Database cleanup
• Resource limitations
  • Too many open files
  • Too much disk space
  • Too much memory

This task will eliminate any database naming conflicts and add a cleanup option to ensure that the database cleanup is done only for those that were created by the FSM test harness.