I'm building (nearly) identical assemblies that each target .net 40 and .net 45. My unit tests are duplicated in two different test projects. Unfortunately, now that I've added a load test as well, I'm getting this message:
In attempting to load TraceLogging_ExecuteAction_IDConsistent from Factory45.test.dll, it was determined that a test with the same id named TraceLogging_ExecuteAction_IDConsistent in Factory40.test.dll already exists in the catalog. If you retry, TraceLogging_ExecuteAction_IDConsistent from Factory45.test.dll will have its id replaced by a new one.
I would like to avoid instability in my test projects / load tests. Do I really need to explicitly rename the tests in the two projects?
That would really be awful if I must rename, because I am currently sharing the test files. One test project "owns" the test file, and the other test project merely points to the same files using a file-link. That gives me a two-for-one test setup.
I'm using VS 2012. Any other solutions?
Aucun commentaire:
Enregistrer un commentaire