-
-
Notifications
You must be signed in to change notification settings - Fork 49
Allow normal shiny app (Teal as a Shiny Module) to use TealAppDriver
#1629
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
base: main
Are you sure you want to change the base?
Conversation
@vedha I don't know whether it is needed, maybe we can remove constructor entirely and do this in tests: app_dr <- shinytest2::AppDriver$new( # or TealAppDriver
init(
data = teal_data() |> within(iris <- iris),
modules = modules(example_module())
) |>
do.call(what = shiny::shinyApp)
) |
Code Coverage Summary
Diff against main
Results for commit: 8c413a7 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
Unit Tests Summary 1 files 27 suites 2m 22s ⏱️ For more details on these errors, see this check. Results for commit 8c413a7. ♻️ This comment has been updated with latest results. |
Unit Test Performance Difference
Additional test case details
Results for commit 3023fda ♻️ This comment has been updated with latest results. |
I also think about base:
base-wrapper
- base-reporter_add_container
- base-src_container
- base-filter_panel
- base-data_summary
- base-module The list is unlimited. Meanwhile we have:
I think we can limit this to two functions, like:
reason is that |
@vedhav to close this one? |
still 54 fails in R CMD CHECK
|
No description provided.