test_app() and it says, “Server did not update any output values within 3 seconds”?The full message is this:
Server did not update any output values within 3 seconds. If this is expected, use `wait_ = FALSE` or increase the value of `timeout_`.This happens when setting an input value does not result in an output changing.
{shinytest2} normally assumes that when you call app$set_inputs(), the setting of an input will also result in a changed output, so the test driver process will wait for an output to change before moving on to the next step in a test script. If no outputs change within the timeout period (which defaults to 3 seconds), it prints that message.
If, in your application, you expect that setting a particular input does not immediately result in any output changes, then you should call app$set_inputs() with wait_=FALSE.
On the other hand, if you expect that setting the input should result in an output change, but the time exceeds the timeout, then you can call app$set_inputs() with, for example, timeout_ = 10 * 1000.
app$set_inputs(). How do I wait for them?In most situations, when an input value is set, {shinytest2} will wait for the next value to be sent to the server. (See question above and this section in Testing in depth. However, when dealing with dynamic UI inputs, htmlwidgets, or even selectize inputs, input values are not set on the first output change. Use app$wait_for_value(input = NAME, ignore = list(VALUE_1, ...., VALUE_N)) to wait until a particular input (or output) value is available (or has a non-invalid value).
{shinytest2}?Sometimes it can be useful to alter the behavior of your application when it’s being tested. To detect when it’s being tested, you can use isTRUE(getOption("shiny.testmode")), as in:
Loading the support environment for a Shiny application requires a call to shinytest2::load_app_env() in ./tests/testthat/setup.R. This method will load the global.R and all R files into the testing environment, similar to testing package R code.
This is not automatically performed as it may be costly to load the support environment.
input and output values that are recorded in snapshots?For some kinds of outputs, it is problematic to record the raw value directly in a JSON snapshot. The output might be very large (e.g., image data or a large table), or it may contain randomly-generated values for which the specific value is unimportant for testing (such as randomly-generated DOM element IDs).
In these situations, you can use an output preprocessor function. This is most commonly done by the author of component used in an application, although it can also be done by an application author. An output preprocessor function is passed an object representing the output value, and it should return a value. If the problem is that the value is large, the preprocessor function can modify the value by hashing it and returning the hash. If the problem is that the value contains some random values, the preprocessor function can replace the random values with fixed ones.
To add an output preprocessor, use shiny::snapshotPreprocessOutput() to modify an output renderer. For example, see this section of the renderDataTable() function. It takes the object that would be returned by renderDataTable(), and modifies it by adding an output preprocessor which removes strings that contain random values.
For some outputs (notably htmlwidgets), the output value is text string containing JSON, and if you want to modify the JSON, you will have to either (1) do text processing on the JSON, or (2) convert the JSON to an R object, modify the R object, and convert the R object back to JSON. The plotly R package uses this method in renderPlotly().
The examples above modify the output renderer from inside the output renderer function, and this would have to be done by the author of the component. It is also possible for an application author to modify a renderer with something like the following:
shinyApp(
ui = fluidPage(
verbatimTextOutput("random")
),
server = function(input, output, session) {
output$random <- snapshotPreprocessOutput(
renderText({
paste("This is a random number:", rnorm(1))
}),
function(value) {
sub("[0-9.]+$", "<a random number>", value)
}
)
}
)The output in the JSON snapshot will be:
(This example is just for illustration purposes. Note that for this example, the screenshots will still change each time the test is run, so there are better solutions, like setting the random seed.)
Input values can face the same issues, and they can also be modified with shiny::snapshotPreprocessInput().
AppDriver?For code completeness, you should call app$stop() at the end of your tests to shut down the background Shiny process and current Chromote Session.
However, {shinytest2} does not do this for code brevity and relies on AppDriver$private$finalizer() (which is called when the value is garbage collected or the R session is stopped) to call AppDriver$stop().
If your R session is starting to feel more sluggish, you may want to call app$stop() manually. Or if you are programmatically creating many instances of AppDriver, you may want to call app$stop() when the specific test is complete.