-
Notifications
You must be signed in to change notification settings - Fork 829
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.
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
ci: setup buildkite test analytics for cypress and jest tests #7953
ci: setup buildkite test analytics for cypress and jest tests #7953
Conversation
packages/eui/cypress.config.ts
Outdated
? 'buildkite-test-collector/cypress/reporter' | ||
: undefined, | ||
reporterOptions: { | ||
token_name: 'BUILDKITE_ANALYTICS_CYPRESS_TOKEN', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cypress reporter expects token_name
to be passed and reads the token automatically. Jest expects the token to be passed directly in the token
property. Not a perfect API, but it works!
…ing jest and cypress tests
0fb8637
to
b212a51
Compare
b212a51
to
b0df47c
Compare
💚 Build Succeeded
History
cc @tkajtoch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Changeset was easy to follow and I manually verified the analytics ran on the Buildkite UI. This will be a great way to track regressions or flaky tests over time!
Summary
This PR configures Buildkite Test Analytics for EUI's cypress and jest tests.
QA