Prefer solution file name in test process command #233
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the test launch process command, registered when targeting the
test
execution environment, to use only the solution file name rather than the absolute solution file path.The motivation for this change is the same as #138 (though there's no need to change directory in this case, as we're only testing the solution file, which is currently always found in the workspace/build directory root). More specifically, it'll allow running the
test
process type in (currently unsupported) environments, such as local integration tests, or Heroku apps built withCNB_EXEC_ENV=test
usingheroku run test
.This shouldn't change the current behavior in any supported environments (including Heroku CI), which all execute the test command from the working directory containing the solution file.