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
This opens the playground with the exact dom that's being tested. If, as you're changing code it would open that somewhere and keep updating... it would greatly speed up testing the frontend.
Today I'm logging the URL, and clicking the link every time I need to see changes.
It could be, perhaps, a tab running like an iframe inside the tests explorer that opens in the browser. Each change changes the value that reloads the page.
The text was updated successfully, but these errors were encountered:
Thanks for the feature suggestion. This is something we had briefly considered in the past, but we're not entirely sure how expensive this would be or how much overhead it would add.
Marking as a feature request, and we will evaluate in our future planning.
Issue description or question
Testing Library has this convenience:
https://testing-library.com/docs/dom-testing-library/api-debugging/#screenlogtestingplaygroundurl
This opens the playground with the exact dom that's being tested. If, as you're changing code it would open that somewhere and keep updating... it would greatly speed up testing the frontend.
Today I'm logging the URL, and clicking the link every time I need to see changes.
It could be, perhaps, a tab running like an iframe inside the tests explorer that opens in the browser. Each change changes the value that reloads the page.
The text was updated successfully, but these errors were encountered: