Usually an FSM workload provides the database and collection to use, and cleans up automatically. The create_database.js test creates and drops databases and collections, because that's the point of the test.

The issue is that the databases are not always always dropped, and on burn-in runs where the test is run multiple times, subsequent runs end up failing due to already existing database/collection.