Add 309: Test flexdashboard tab and page management with {bslib}#155
Add 309: Test flexdashboard tab and page management with {bslib}#155
Conversation
| } | ||
|
|
||
| expect_test_element_hidden <- function(app, test_id) { | ||
| expect_false(app$get_js(is_test_element_visible(!!test_id))) |
There was a problem hiding this comment.
Since these tests are essentially purely client-side, it'd probably faster/better to use {shinyjster} instead of {shinytest2}, for example:
shinycoreci/inst/apps/187-navbar-collapse/app.R
Lines 10 to 45 in fb236b8
There was a problem hiding this comment.
@schloerke Is shinyjster designed to facilitate running and testing R Markdown Shiny apps using runtime: shiny? (I couldn't find anything in the docs.)
It seems like the biggest advantage of using shinyjster would be to test in Chrome, Edge, and Firefox. From looking at the logs of previous runs, though, and unless I'm misunderstanding them, I would expect switching to shinyjster to increase the test time for these tests. Right now, they take ~7 seconds locally on my M1 for all three Bootstrap variants. With shinyjster we'd be adding two more browsers into the matrix.
There was a problem hiding this comment.
{shinyjster} can run inside Rmd docs. Ex:
shinycoreci/inst/apps/185-report-theme/index.Rmd
Lines 135 to 174 in fb236b8
Yes, it's reasonable that the time would be increased, but it is not by a large factor. I'd be comfortable using shinyjster.
Co-authored-by: Carson Sievert <cpsievert1@gmail.com>
Does this really matter though since |
Yeah I think this is all set to merge and fine to merge ahead of rstudio/bslib#501. |
Adds an app for testing tab and page management that rely on Bootstraps Tab plugin, as managed by bslib, over Bootstrap version 3, 4 and 5.
data-bs-toggleis present in the BS3 tabset compatibility shims bslib#501Fixes #154