✅ Deploy Preview for vitest-dev ready!

Name	Link
🔨 Latest commit	cebc0ad
🔍 Latest deploy log	https://app.netlify.com/projects/vitest-dev/deploys/68af2b38bc578f0007a8eaf7
😎 Deploy Preview	https://deploy-preview-8016--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Hi @sheremet-va, I'd like to work on supporting expect assertions on the Iframe.
Is there a fundamental blocker that makes it not possible? At least if the Iframe is on the same domain.

Does it need to be done at the framework adapter level?
Initially I was looking at vitest-browser-react.
If you could give me some pointers on where to start I'd appreciate it.

I promise I won't just do a PR with AI slop 😄 .

Hi @sheremet-va, I'd like to work on supporting expect assertions on the Iframe. Is there a fundamental blocker that makes it not possible? At least if the Iframe is on the same domain.

Does it need to be done at the framework adapter level? Initially I was looking at vitest-browser-react. If you could give me some pointers on where to start I'd appreciate it.

I promise I won't just do a PR with AI slop 😄 .

The locator support is provided via ivya package. The implementation should work the same way as playwright. Playwright does support click here, which suggests that it also supports traversing the DOM. Why it doesn't work at the moment, I don't know.

Basically, to make expect work, we need this to not fail:

const frame = page.frameLocator(page.getByTestId('iframe'))
frame.getByText('Hello World').element() // right now fails