You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that Albacore is not finding the Nunit executable after the noted change of working directory (see Issue 109).
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, shown in issue 109, will now end up in a completely unknown location, assuming it's created at all.
Both rc11 and rc12 fail to find the Nunit executable because the working directory has been changed. rc11 seemingly didn't account for the working dir change at all. rc12 does a bunch of ../../..'s but apparently it isn't correct.
2014-04-07T18:36:23.204638+01:00: executing in directory './../source/App1.Tests/bin/release'
build 07-Apr-2014 12:36:23 ..........\deploy\Tools\NUnit.2.5.10.11092\nunit-console.exe App1.Tests.dll /xml=../Build/Output/unit_test_results.xml
error 07-Apr-2014 12:36:23 rake aborted!
error 07-Apr-2014 12:36:23 Albacore::CommandNotFoundError: Command failed with status (127) - number 127 in particular means that the operating system could not find the executable:
error 07-Apr-2014 12:36:23 ..........\deploy\Tools\NUnit.2.5.10.11092\nunit-console.exe App1.Tests.dll /xml=../Build/Output/unit_test_results.xml
The text was updated successfully, but these errors were encountered:
An alternative way of doing it is to have leave both exe and dll paths alone, and having a method #work_dir= that allows you to change it and 'take care of it yourself'.
I've tried rc12.
The problem is that Albacore is not finding the Nunit executable after the noted change of working directory (see Issue 109).
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, shown in issue 109, will now end up in a completely unknown location, assuming it's created at all.
Both rc11 and rc12 fail to find the Nunit executable because the working directory has been changed. rc11 seemingly didn't account for the working dir change at all. rc12 does a bunch of ../../..'s but apparently it isn't correct.
2014-04-07T18:36:23.204638+01:00: executing in directory './../source/App1.Tests/bin/release' build 07-Apr-2014 12:36:23 ..........\deploy\Tools\NUnit.2.5.10.11092\nunit-console.exe App1.Tests.dll /xml=../Build/Output/unit_test_results.xml error 07-Apr-2014 12:36:23 rake aborted! error 07-Apr-2014 12:36:23 Albacore::CommandNotFoundError: Command failed with status (127) - number 127 in particular means that the operating system could not find the executable: error 07-Apr-2014 12:36:23 ..........\deploy\Tools\NUnit.2.5.10.11092\nunit-console.exe App1.Tests.dll /xml=../Build/Output/unit_test_results.xml
The text was updated successfully, but these errors were encountered: