Thanks for the reply! Good suggestion on the extraction of the functionality into a separate package. I'll take a look into it! I noticed
shinytest has a recording function but it probably won't be much use to me as my app relies on 3rd party data which can change at any point so I'd have failing frontend tests left right and centre.
In terms of Pipelines, I find it a nice lightweight alternative to TravisCI and Jenkins: Pipelines
For example, to build my Dockerised Shiny Server image and push it to Dockerhub on commit I just need a
bitbucket-pipelines.yml file in the base of the repo, all it contains is:
- docker login -u $DOCKER_HUB_USERNAME -p $DOCKER_HUB_PASSWORD
- docker build -t $DOCKER_HUB_REPO:$PROJECT-$BITBUCKET_COMMIT .
- docker push $DOCKER_HUB_REPO
@mishabalyasin thanks for the suggestion, gonna mark this as solved. I'm not sure shinytest will be much use because of the constant changing data returned from 3rd parties. But I'll certainly split out my functionality so it can be tested separately from the main Shiny code.
Going to move the Pipelines section to a separate post.