phpunit bootstrap - Work-around for issues with running phpunit in symlinked dirs #121
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.
There was add an odd phenomenon when an extension is moved to a symlinked dir, e.g.
If you navigated into the folder and called
cv
directly (e.g.cv api contact.get
orcv php:boot
), then it worked fine. However, if you navigated into the same folder and calledphpunit
(which then calledcv php:boot
), then they'd fail. Empirically,phpunit
does the equivalent ofchdir(realpath(getcwd()))
(although I haven't traced how/why).This patch provides a work-around in the template. You may need to update the
tests/phpunit/bootstrap.php
to benefit from it.