-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Testing Infrastructure
I'm told by judah.schvimer that it is sometimes useful to be able to correlate a process via its command line arguments to the test that started the process. Currently we achieve this by passing a "name" to ReplicaSetTest and ShardingTest. This has a few downsides relative to having resmoke inject the test name:
- It is optional so not every test passes it in
- The name may not exactly match the test name
- There is nothing to prevent two tests from passing the same name
- This is actually the default state since most tests start as a copy of another
- Updating the name manually when writing or renaming tests is busywork
Injecting the test name can be done in a few ways:
- Adding a --comment argument to mongo binaries that is ignored and can be repeated
- Setting a default name that ReplSetTest and ShardingTest use by default if none is passed in
- Adding the test name to the dbpath prefix passed to tests
- related to
-
SERVER-27766 ReplicaSetTest should use jsTest.name() as the default for the name
- Closed