test(tracing): Add integration tests for pageload and navigation
#4376
Conversation
size-limit report
|
| trace_id: '12312012123120121231201212312012', | ||
| }); | ||
|
|
||
| expect(eventData.spans?.length).toBeGreaterThan(0); |
There was a problem hiding this comment.
Can we assert that navigation transactions won't have the same trace ID and parent span ID?
There was a problem hiding this comment.
👍 adding the assertions to navigation tests at -> packages/integration-tests/suites/tracing/browsertracing/navigation/test.ts
There was a problem hiding this comment.
This is also needed for the meta tests, to make sure that navigation transactions don't continue a transaction from the meta header.
| // This is the `pageload` transaction | ||
| await getSentryTransactionRequest(page, url); | ||
|
|
||
| const navigationRequest = await getSentryTransactionRequest(page, `${url}#foo`); |
There was a problem hiding this comment.
I'd rather us use the multiple transactions helper here.
I would also like to see some more assertions to show the differences between pageload and navigation transactions.
There was a problem hiding this comment.
I'd rather us use the multiple transactions helper here.
My intention here is to initiate a navigation (to #foo) after the pageload transaction, so it's not possible to use the helper as it operates on a single URL for all requests.
… into onur/tests-browsertracing
…n` transactions.
Part of: #4262