Thank you for the amazing tool! It's quickly become a core part of my workflow.
I understand the reasoning behind the relative path for the reference images and jsons, but for apps with a long-running lifecycle, frequent changes, or repositories with several apps, we're a little nervous about the pngs accumulating in the git history and bloating the repository size. We'd like to be able to host the reference images outside of the repository, without cloning the app around those files every time.
I can see that the shinytest internals already distinguish between the "path" (to the App) and the "testDir", but the testDir is hidden from the user. It would be really valuable for us to be able to set the testDir location as an argument (or perhaps a configuration to be stored in the app code repository?). Thanks!
Thank you for the amazing tool! It's quickly become a core part of my workflow.
I understand the reasoning behind the relative path for the reference images and jsons, but for apps with a long-running lifecycle, frequent changes, or repositories with several apps, we're a little nervous about the pngs accumulating in the git history and bloating the repository size. We'd like to be able to host the reference images outside of the repository, without cloning the app around those files every time.
I can see that the shinytest internals already distinguish between the "path" (to the App) and the "testDir", but the testDir is hidden from the user. It would be really valuable for us to be able to set the testDir location as an argument (or perhaps a configuration to be stored in the app code repository?). Thanks!