The main goal I have in mind is to use this for profiling. Currently the dashboard can be profiled via profvis::profvis(shiny::runApp("<app dir>")) but requires a human to provide the interaction. This makes it difficult to redo and to compare behavior of exactly the same actions.
My understanding of Shiny testing is that we want to use Selenium to click buttons on the dashboard and time how long it takes a particular html element (by id) to show up. The shinytest package may also be useful.
Perhaps we should make a more generalized tool in case we want to apply it to other automated dashboard tasks.
The main goal I have in mind is to use this for profiling. Currently the dashboard can be profiled via
profvis::profvis(shiny::runApp("<app dir>"))but requires a human to provide the interaction. This makes it difficult to redo and to compare behavior of exactly the same actions.My understanding of Shiny testing is that we want to use Selenium to click buttons on the dashboard and time how long it takes a particular html element (by id) to show up. The
shinytestpackage may also be useful.Perhaps we should make a more generalized tool in case we want to apply it to other automated dashboard tasks.