You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should move_shinytest2_tests() always move the contents of the testing directory to <project_path>/tests instead of relying on the original name of the directory?
(I suspect there's a bug waiting to happen here, where the user has a name for that directory that is not "tests").
From my understanding, move_shinytest2_tests() relies on the parameter for the shinytests2 test directory to be exactly tests to work properly. If the directory is called tests_shinytests then it fails.
I've setup a branch with this example on the test app:
Should
move_shinytest2_tests()
always move the contents of the testing directory to<project_path>/tests
instead of relying on the original name of the directory?(I suspect there's a bug waiting to happen here, where the user has a name for that directory that is not "tests").
From my understanding,
move_shinytest2_tests()
relies on the parameter for the shinytests2 test directory to be exactlytests
to work properly. If the directory is calledtests_shinytests
then it fails.I've setup a branch with this example on the test app:
https://github.com/Appsilon/shiny.benchmark/tree/example_non_standard_name/tests/end2end/app
The text was updated successfully, but these errors were encountered: