With InTest 2.0 (the 64 bit version?), it appears the invocation pattern has changed, and now expects the first argument to be the root path of the project under test.
intest PROJECT OPTIONS -using RECIPEFILE -do INSTRUCTIONS
PROJECT is the home folder of the project to be tested
Changes:
Change the signature of the method executeInTestWithArgs to better reflect this change in intest.
All callers updated to pass the extension path.
Added logic to strip the extension path back to the folder project in the new executeInTestForExtension:withArgs method.
Resolves the issue described here.
With InTest 2.0 (the 64 bit version?), it appears the invocation pattern has changed, and now expects the first argument to be the root path of the project under test.
Changes:
executeInTestWithArgs
to better reflect this change inintest
.executeInTestForExtension:withArgs
method.