You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the title says, our test encounters the dreaded “Content of the iframe to which you are switching did not load”. It’s not at all clear why: running with the Chrome devtools open, no requests are failing or timing out. (The devtools show the websocket connection as forever “pending”, but forcing it to fail did not make TestCafe think the frame was done loading.)
If I may speculate, I notice that while the parent frame is proxied, the iframe URL is pointing straight to our server, not a proxy. Maybe this is the issue? If so, maybe it is in turn caused by the fact that our iframe src is set by Javascript, not hardcoded in the page? (And if so, maybe a simple MutationObserver on {attributeFilter:['src']} could help?)
Minimal repro:
import{Selector,t}from'testcafe';fixture`Login from login page Elk`.page`https://web.elk.co/login`;test('Login with test account',asynct=>{awaitt.switchToMainWindow().expect(Selector('iframe[id=Content]').exists).ok().switchToIframe('#Content').expect(Selector('#email').exists).ok().expect(Selector('#password').exists).ok();});
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow.
As the title says, our test encounters the dreaded “Content of the iframe to which you are switching did not load”. It’s not at all clear why: running with the Chrome devtools open, no requests are failing or timing out. (The devtools show the websocket connection as forever “pending”, but forcing it to fail did not make TestCafe think the frame was done loading.)
If I may speculate, I notice that while the parent frame is proxied, the iframe URL is pointing straight to our server, not a proxy. Maybe this is the issue? If so, maybe it is in turn caused by the fact that our iframe
src
is set by Javascript, not hardcoded in the page? (And if so, maybe a simpleMutationObserver
on{attributeFilter:['src']}
could help?)Minimal repro:
The text was updated successfully, but these errors were encountered: