Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

screen.openTestingPlayground()? 🤔

See original GitHub issue

Ok ok, get here’s my idea… Often I tell people: “Add a screen.debug() and copy/paste the HTML output into testing-playground.com”

What if…

screen.openTestingPlayground()

And it just opened a testing playground with all their HTML set in there automatically??? Thoughts on this idea? Good/bad? I’m sure it could be improved… Just a random thought I had.

cc @smeijer

Issue Analytics

State:
Created 3 years ago
Reactions:14
Comments:14 (10 by maintainers)

Top GitHub Comments

2reactions

pavellozcommented, Jul 19, 2022

I started to use logPlaygroundUrl and i quickly found that im copying and pasting the url to see whats what. Immediately i tried to write a helper to open (npm package open) the url automatically in the browser.

Any chance of exposing the URL under some method, or maybe even better, passing { open: true } into screen.logTestingPlaygroundURL() to save a lot of time and clicks?

2reactions

balavishnuvjcommented, Oct 12, 2020

has anyone picked this up? If not, I can pick it up 😃