shinyloadtest is designed to work with a wide variety of application types and deployments, but there are certain types of application and deployment configurations that it is known not to support.
shinyloadtest does not.
shinycannon against an application deployed using that same type of server. So, for example, a recording made of an application running on Connect will not work correctly if it’s run with
shinycannon on the same target application deployed using a different server like Shiny Server Pro.
record_session contains messages from the server in the order they were received. If messages are received in a different order by
shinycannon when it’s playing the recording back, that session will be considered a failure. If the same change in inputs does not always lead to outputs being updated in the same order, shinyloadtest will not work.
shinycannon to fail. The telltale sign of such a problem is a message like
WS_RECV line 66: Haven't received message after 30 seconds in
shinycannon is replaying them.
selectize() input, particularly when
server = TRUE. More information can be found at https://github.com/rstudio/shinyloadtest/issues/121
runtime: shiny unsupported: R Markdown documents that embed Shiny applications are currently unsupported.