-
Notifications
You must be signed in to change notification settings - Fork 30
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
Ophan e2e tests and remove Ophan request cancellation #10359
Conversation
Size Change: 0 B Total Size: 749 kB ℹ️ View Unchanged
|
}) => { | ||
const ophanRequestPromise = interceptOphanRequest({ | ||
page, | ||
path: 'img/1', |
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.
Why img/1
and img/2
?
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.
Good question!
Looking at the network requests that Ophan makes:
img/1
is the single 'view' request that conveys the page URL being viewed.img/2
are the multiple 'event' requests that convey individual pieces of data such as abtests, attentionMS, consent and performance metrics.
Its good to raise though. I will ask the Ophan team what their official naming is for these requests.
What does this change?
Following #10330 we can now:
img/1
andimg/2
requests are made to Ophan for articles and fronts including tests when consent is given or rejectedloadPage
utilload
event to ensure all requests have completed when loading pages rather thandomcontentloaded
. Although this adds ~1-5s per test it should improve test stabilityWhy?
Improved test coverage