{shinytest2} e2e tests are currently created around AppDriver$set_input that will make the necessary changes via javascript: Shiny.setInput function (within {chromote} session).
Current approach successfully tests the app, but it lacks the real interactions that users have with the app, that is:
Is the input being used visible / existing in the UI
Can the user interact with it
Idea
Add to API functions that find <input> elements and can modify value (triggering observe callbacks in R)
methods for filter panel interaction to modify filters (alternative to set_active_filter_selection)
methods to change encoding panel (alternative to set_module_input)
Code of Conduct
[X] I agree to follow this project's Code of Conduct.
Contribution Guidelines
[X] I agree to follow this project's Contribution Guidelines.
Security Policy
[X] I agree to follow this project's Security Policy.
Feature description
Problem
{shinytest2}e2e tests are currently created aroundAppDriver$set_inputthat will make the necessary changes viajavascript: Shiny.setInputfunction (within{chromote}session).Current approach successfully tests the app, but it lacks the real interactions that users have with the app, that is:
Idea
<input>elements and can modify value (triggeringobservecallbacks inR)set_active_filter_selection)set_module_input)Code of Conduct
Contribution Guidelines
Security Policy