Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
## What's the problem this PR addresses? I'm reviewing our tests and came upon some of them that could be dumbed down. I prefer to make them test as little things as possible to avoid something breaking due to unrelated parts of the code changing (I'm working on switching some implementations, and limiting test dependencies make things considerably easier / more fun to work on). ## How did you fix it? No big changes - it's mostly things like using the `dependencies` rather than calling `yarn add` and avoiding to rely on cache paths to check whether something got properly installed. ## Checklist <!--- Don't worry if you miss something, chores are automatically tested. --> <!--- This checklist exists to help you remember doing the chores when you submit a PR. --> <!--- Put an `x` in all the boxes that apply. --> - [x] I have read the [Contributing Guide](https://yarnpkg.com/advanced/contributing). <!-- See https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released for more details. --> <!-- Check with `yarn version check` and fix with `yarn version check -i` --> - [x] I have set the packages that need to be released for my changes to be effective. <!-- The "Testing chores" workflow validates that your PR follows our guidelines. --> <!-- If it doesn't pass, click on it to see details as to what your PR might be missing. --> - [x] I will check that all automated PR checks pass before the PR gets reviewed.
- Loading branch information