[test_runner] Parameterize test_runner working directory change

[mobill]

Please parameterize the working directory change in test_runner.

In rc12, test_runner changes the working directory to the directory specified for the test assembly. I do not want the working directory to change.

assemblies:

"../source/App1/Tests/Unit/App1.Tests/bin/release/App1.Tests.dll",
"../source/App2/Tests/Unit/App2.Tests/bin/release/App2.Tests.dll"


rakefile working dir:

c:\build-dir\job\deploy


resulting command line in rc12:

..........\deploy\Tools\NUnit.2.5.10.11092\nunit-console.exe App1.Tests.dll /xml=../Build/Output/unit_test_results.xml


should be:

Tools\NUnit.2.5.10.11092\nunit-console.exe ../source/App1/Tests/Unit/App1.Tests/bin/release/App1.Tests.dll /xml=../Build/Output/unit_test_results.xml


See issues 109 and 110

I understand your point about the test data location, but you're assuming that test data will be local to the test assembly. Forcing the working directory just isn't a good solution. It is hidden, unexpected behavior. It should be parameterized and under my control.

NOTE the results xml file specified in the command parameter will now end up in a completely unknown location, assuming it's created at all.

[haf]

Ok, I've gone through this a bit more methodologically and this is the intended behaviour. There's always a fallback on simply calling the executable directly, like so:

system 'src/packages/NUnit.Tools.2.6.3/tools/nunit-console.exe',
       'src/lib.dll',
        clr_command: true

I'm remaking this a feature request. I'm open to pull requests if you want a flag that modifies the default behaviour.