Skip to content

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

Merged
merged 7 commits into from
Oct 4, 2022

Conversation

lforst
Copy link
Contributor

@lforst lforst commented Oct 3, 2022

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.

@lforst lforst force-pushed the lforst-standard-frontend-application-e2e-setup-guide branch from 0857a22 to da6a8f5 Compare October 3, 2022 13:04
`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
Copy link
Contributor Author

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

@lforst lforst added this to the E2E Tests milestone Oct 3, 2022
@lforst lforst mentioned this pull request Oct 3, 2022
2 tasks
@lforst lforst marked this pull request as ready for review October 3, 2022 14:26
@lforst lforst requested review from AbhiPrasad and Lms24 October 3, 2022 14:26
Copy link
Member

@Lms24 Lms24 left a 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?


## Standardized Test Apps

For some of our integration tests we define a standard for test applications as to how they should look and behave.
Copy link
Member

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?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup thank you!

@lforst
Copy link
Contributor Author

lforst commented Oct 3, 2022

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?

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. :)

@lforst lforst merged commit 28c464d into master Oct 4, 2022
@lforst lforst deleted the lforst-standard-frontend-application-e2e-setup-guide branch October 4, 2022 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants