Unify E2E tests & ensure they test everything we care about

[mydea]

We want to have unified guides for E2E tests to ensure we capture the same things for the different types of E2E apps.

[s1gr1d]

Some ideas for a test base:

Test Param Route

'/test-param-success/:param'
'/test-param-failure/:param'

Test Non-Param Route (optional, as already covered by param tests)

'/test-success'
'/test-failure'

Test Manual Span Creation (startSpan)

'/test-manual-success'
'/test-manual-failure'

Some more ideas:

• Test Redirect
• Test Local Variables

[Lms24]

This is great! Let's keep in mind that in general we have 3 classes of SDKs we should cater to:

• backend SDKs - I think your proposal covers them well. We probably don't need the non-param routes but that's fine. I'd probably add distributed tracing (e.g. test request w/ incoming tracing headers, test attaching tracing hearders to outgoing requests).

For later:

• frontend SDKs - here we should test more stuff like pageloads && navigations
• meta/fullstack SDKs - here we should test both sides + distributed tracing.

[s1gr1d]

@luca added some points about standardized test apps already: https://github.com/getsentry/sentry-javascript/blob/3a1f0287aef3b24f05b7d0cf7d0383b5c907b13a/dev-packages/e2e-tests/README.md#standardized-test-apps