Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Idea: To debug a failing test, be able to "browse()" into the app #85

Open
daattali opened this issue Feb 10, 2017 · 1 comment · May be fixed by #348
Open

Idea: To debug a failing test, be able to "browse()" into the app #85

daattali opened this issue Feb 10, 2017 · 1 comment · May be fixed by #348
Labels
chromium 📺 Features that will require a chromium backend feature a feature request or enhancement

Comments

@daattali
Copy link
Contributor

daattali commented Feb 10, 2017 •
edited by bborgesr
Loading

Related to #26

If a regular unit test (outside of shiny) fails, an easy way to debug it is to put a browse() statement just before the offending line, so that you can see exactly what the state is.

It would be great to be able to replicate that behaviour when testing shiny apps. One idea is to let you launch the app in a "spectator" mode where the app actually launches in a proper browser with UI, and you can click a button to say "run the next command in the test script" or inspect the state of everything. Another idea is to be able to place a shinytest::browse_app() command inside the test script, and when this command is reached then the app is launched and lets the user see the current state.

Perhaps this is too ambitious :)
@hadley hadley added chromium 📺 Features that will require a chromium backend feature a feature request or enhancement labels Aug 8, 2020
@warnes
Copy link

warnes commented Aug 13, 2020

Another option, perhaps simpler?, would be to run the shiny app in the main RStudio UI, even though the client is running in a headless slave process. This way one could set breakpoints etc to debug the app while the test script executes.

Failing that, could we at least get a traceback in the error response?

@warnes warnes linked a pull request Aug 18, 2020 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chromium 📺 Features that will require a chromium backend feature a feature request or enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Allow connecting to an existing Shiny instance cogentherapeutics/shinytest
3 participants
@hadley @daattali @warnes