We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
{shinytest2}
ui.R
server.R
As mentioned here, creating an issue to track this.
To reproduce this issue, run record_test() in this folder.
record_test()
Testing the exact same app works when it is only in a single app.R file.
app.R
What I see locally:
> record_test() Error in `app_initialize()`: ! Chromote: timed out waiting for response to command Target.createTarget ℹ You can inspect the failed AppDriver object via `rlang::last_error()$app` ℹ AppDriver logs: {shinytest2} R info 13:19:39.33 Start AppDriver initialization {shinytest2} R info 13:19:39.33 Starting Shiny app {shinytest2} R info 13:19:39.76 Creating new ChromoteSession {shinytest2} R info 13:19:49.76 Error while initializing AppDriver: Chromote: timed out waiting for response to command Target.createTarget {shiny} R error ----------- Loading required package: shiny {shiny} R error ----------- Running application in test mode. {shiny} R error ----------- {shiny} R error ----------- Listening on http://127.0.0.1:3797 Caused by error: ! Chromote: timed out waiting for response to command Target.createTarget Run `rlang::last_error()` to see where the error occurred.
Session info
Created on 2022-08-06 by the reprex package (v2.0.1)
The text was updated successfully, but these errors were encountered:
Add test app from #244
e6e6e75
Successfully merging a pull request may close this issue.
As mentioned here, creating an issue to track this.
To reproduce this issue, run
record_test()
in this folder.Testing the exact same app works when it is only in a single
app.R
file.What I see locally:
Session info
Created on 2022-08-06 by the reprex package (v2.0.1)
The text was updated successfully, but these errors were encountered: