Hi

Problem:

The developers make and maintain the unit tests. The tester (with VS2005 4 Testers) or architect (me with the team suite) maintain the testlists and TestRunConfig.

Input files to the tests are put in a \TestData dir under each test project. I set up the TestRunConfig to deploy the input files. Everything works nicely on my system and the build machine but not on the developer boxes! The input files are simply not deployed. Furthermore the TestRunConfigs are not under the control of the developers that develop the unit tests!

Is there something I'm missing here?

Brumlemann
Solution Architect

Luis:

TS on the build machine (old habit from the Beta days. Probably should replace it with VS4Testers to stay compliant with our licensing. Will do it I promise but not right now :).

Thats why the tests are working nicely in conjunction with the .testrunconfig there. The problem arises on the dev boxes. Yes, they have the .testrunconfig (it's under our single solution), but it seems to be ignored.

MS has not, as we know, included the functionality to manage this config or the .vsmdi files in TS4Devs. Actually they're all XMLs so with a bit of insight they can do it. And herein lies the rub (as Hamlet would put it) and, methinks, the reason why MS didn't nicify the XML in these files. They did it so you can only edit them with an expensive tool. Am I right Bill? Huh? Huh? Oh, that's right, he's retired :)

So the question is why doesnt the default .testrunconfig apply on dev boxes? The consequence is that developers needing file input in tests have to, in the test code, enter an obscure and uncertain relative path (../../<ProjectDir>/TestData/<NameOfFile> or similar>) to get to the file with the input for the test. They then have to remove this path before checkin to make it compliant with the build machine or theyre superior The Architect (yours truly).

Then again, there might be something I'm missing here. If so, please enlighten me.

Brumlemann
Solution Architect