Summary: Given that the e2e tests are quite flaky, we want to reduce the flakyness making them non land blocking. The idea is to: 1. always have them green in CircleCI 2. store the test logs in CircleCI artifacts, so we can explore them if needed. 3. use danger to read the artifacts from CircleCI and post a message to inform the user whether the Test ends up successfully or not. ## Changelog: [Internal] - Make e2e tests non land-blocking. Use Danger to report the status of the E2E jobs Pull Request resolved: https://github.com/facebook/react-native/pull/39129 Test Plan: CircleCI stays green, logs are uploaded as artifacts. Reviewed By: rshest Differential Revision: D48642955 Pulled By: cipolleschi fbshipit-source-id: 185862f46c47d59f949743a9b893162b2bb3a651
Danger
Danger is a JavaScript runtime which helps you provide continuous feedback inside GitHub. It's used inside Github Actions to analyze the contents of a GitHub pull request.
If you want to test changes to Danger, I'd recommend checking out an existing PR and then running the danger pr command.
You'll need a GitHub Public Access Token (PAT). It will look like ghp_<REDACTED>.
So, for example:
DANGER_GITHUB_API_TOKEN=ghp_<REDACTED> yarn danger pr https://github.com/facebook/react-native/pull/1234
Code Analysis Bot
The code analysis bot provides lint and other results as inline reviews on GitHub. It runs as part of the Circle CI analysis workflow.
If you want to test changes to the Code Analysis Bot, I'd recommend checking out an existing PR and then running the analyze pr command.
You'll need a GitHub token. You can re-use this one: 312d354b5c36f082cfe9 07973d757026bdd9f196 (just remove the space).
So, for example:
GITHUB_TOKEN=[ENV_ABOVE] GITHUB_PR_NUMBER=1234 yarn lint-ci