We've developed internally a large and fairly complicated shiny app which output fully relies on connections made with our DB. The app is already at a certain state of maturity when it makes sense to include automatic tests before each deployment. However, I just wanted to get your opinion on using shinytest (or testing somehow differently) for an app that outputs (and inputs too) constantly vary with time?
What I mean by that is when user enters the main page one needs to enter a time-range for which certain inputs are rendered and visualized. The problem starts here: when a user performs the same search in 2 weeks from this moment, the outputs won't necessarily be the same, hence, the reference point for testing will constantly change. It might also be the case that in 4 weeks time it wouldn't be possible to input the same input values in the date selection as it's being time-restricted.
Is there a way I can pass static testing inputs to shinytest instead of making DB calls or how to approach this best? Can you please share your experiences?