-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[Feature] coverage per frame #3920
Comments
No deliberate decision to not support it, but no intention either. What's your code coverage use case if you don't mind sharing? We can rarely see coverage used with the end-to-end testing, so any details will help. |
I'm working on the next version of my The idea is to run tests in UI in dev flavor (see some control panel, test outcomes/elements in the working panel, re-run and debug via the dev-tools), and also in CI flavor - almost the same, but just run all of the tests once and report. Report should give coverage per test. UI/dev mode also allows to re-run a single test ad-hoc just in the browser and see the results/debug. For both those use-cases it would be perfect to load and run each test-run in it's own Until that is possible (if any), my plan is to split the code and for the CI flavor run each test in its own Page, but obviously I'd prefer to have a unified flow logic as much as possible. |
Coverage per frame is a major effort. JavaScript VMs usually share the scripts cache between frames from the same origin, and collecting separate coverage for them might be very hard. I would not expect this feature any time soon, sorry. |
Understandable, thanks. |
Right now
coverage
property is found on thePage
object, but not on theFrame
object.Since there are obvious use-cases, where scripts can be loaded specifically in the frames - any intention (or deliberate decision to not) to add a capability of collecting coverage on the
Frame
level?The text was updated successfully, but these errors were encountered: