Fix testdata project path in Yarn tests #40
Merged
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.
dev
branch.go vet ./...
.go fmt ./...
.This PR fixs testdata project path in yarn tests. The local path for the tests projects was changed during the migration to security-cli but the path wasn't changed in the tests.
The tests currently pass in Prod since the machine that runs the tests contains lower yarn version (Yarn 1), that enables running 'install' on an empty directory, which causes the tests to pass without actually checking what the test is intended to check.
This is not allowed in higher yarn versions.