Searching for the following two strings in tests:

• createCollection("test"
• getCollection("test"

Yields the following list of tests making usage of the same collection name:

• jstests/aggregation/expressions/expression_mod.js
• jstests/aggregation/expressions/ts_second_increment.js
• jstests/aggregation/variables/layered_variables.js
• jstests/auth/lib/commands_lib.js
• jstests/core/administrative/profile/profile_agg.js
• jstests/core/administrative/profile/profile_count.js
• jstests/core/administrative/profile/profile_delete.js
• jstests/core/administrative/profile/profile_distinct.js
• jstests/core/administrative/profile/profile_find.js
• jstests/core/administrative/profile/profile_findandmodify.js
• jstests/core/administrative/profile/profile_getmore.js
• jstests/core/administrative/profile/profile_insert.js
• jstests/core/administrative/profile/profile_mapreduce.js
• jstests/core/administrative/profile/profile_update.js
• jstests/core/api/api_params_getmore.js
• jstests/core/api/apitest_db.js
• jstests/core/query/agg_hint.js
• jstests/core/sbe/from_plan_cache_flag.js
• jstests/core/version_api_v1_command_coverage.js
• jstests/fle2/implicit_schema_validation.js
• jstests/noPassthrough/json_schema_validator_logging.js
• jstests/noPassthrough/nested_code_with_scope.js
• jstests/noPassthrough/profile_interrupted_op.js
• jstests/noPassthrough/profile_write_conflict.js
• jstests/noPassthrough/reconfig_restarts_collection_scan.js
• jstests/noPassthrough/set_user_write_block_mode.js
• jstests/noPassthrough/use_disk.js
• jstests/noPassthrough/validate_db_metadata_limits.js
• jstests/noPassthroughWithMongod/randomized_mixed_type_bug.js
• jstests/replsets/create_drop_database_different_casing.js
• jstests/replsets/kill_ttl_on_stepdown.js

We've already seen errors where two tests running in parallel within the same test instance can fail due to one dropping the collection used by the other. We should strive to make these collection names unique if possible.