Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[docs] Fix typos in test folder's README #33976

Merged
merged 1 commit into from Aug 19, 2022
Merged

[docs] Fix typos in test folder's README #33976

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions test/README.md
View file
Open in desktop
Expand Up @@ -7,7 +7,7 @@ Thanks for writing tests! Here's a quick run-down on our current setup.
1. Add a unit test to `packages/*/src/TheUnitInQuestion/TheUnitInQuestion.test.js` or an integration test `packages/*/test/`.
2. Run `yarn t TheUnitInQuestion`.
3. Implement the tested behavior
4. Open a PR once the test passes or you want somebody to review your work
4. Open a PR once the test passes or if you want somebody to review your work

## Tools we use

Expand Down Expand Up @@ -162,7 +162,7 @@ Our tests run on different browsers to increase the coverage:

##### BrowserStack

We only use BrowserStack for non-PR commits to save ressources.
We only use BrowserStack for non-PR commits to save resources.
BrowserStack rarely reports actual issues so we only use it as a stop-gap for releases not merges.

To force a run of BrowserStack on a PR you have to run the pipeline with `browserstack-force` set to `true`.
Expand Down