-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
test(e2e): Add standard frontend test app specification #5874
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
test(e2e): Add standard frontend test app specification #5874
Conversation
0857a22
to
da6a8f5
Compare
`standard-frontend-nextjs`. | ||
- A page at path `/` | ||
- Having a `<input type="button" id="exception-button">` that captures an Exception when clicked. The returned | ||
`eventId` from the `Sentry.captureException()` call must be written to `window.capturedExceptionId`. It doesn not |
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.
We write it to window.capturedExceptionId
so we can read it with playwrights waitForFunction
https://playwright.dev/docs/api/class-page#page-wait-for-function
…ntend-application-e2e-setup-guide
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.
Looks good to me. Just to confirm: This gives us standardized test apps against which we can run a set of standardized tests (coming soon I guess)? Do we need to add anything to these apps to test sessions/release health?
packages/e2e-tests/README.md
Outdated
|
||
## Standardized Test Apps | ||
|
||
For some of our integration tests we define a standard for test applications as to how they should look and behave. |
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.
Shouldn't this be "end-to-end" tests?
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.
Yup thank you!
Correct, I will add the actual tests in a follow-up PR. As for release health: Thanks for reminding me, I thought we were good on that front but I needed to add a release value so that sessions are sent. :) |
Ref: #5855
Adds a specification on how to configure standardized frontend test applications for our E2E tests and also adds a React test application that conforms to that standard.