Skip to content
This repository has been archived by the owner on May 19, 2021. It is now read-only.

Test project / package after hypothetical package update #62

Open
czeildi opened this issue May 15, 2018 · 2 comments
Open

Test project / package after hypothetical package update #62

czeildi opened this issue May 15, 2018 · 2 comments

Comments

@czeildi
Copy link

czeildi commented May 15, 2018

Related to #31 and also the following comment of @noamross in #35

If you want to do live testing of a package, like seeing what system files/folders it modifies, I'm working on a Dockerized setup for our standard package tests: https://github.com/noamross/launchboat, so one could run tests in an isolated environment before installing.

Before updating a dependency to the newest version see which tests would break.

I can imagine this as a service (or maybe Rhub can already do this??) or a local version with Docker ensuring a separate environment.

@czeildi
Copy link
Author

czeildi commented May 19, 2018

Summary: Before updating a dependency to the newest version see which tests would break.

I can imagine this as a service (or maybe Rhub can already do this??) or a local version with Docker ensuring a separate environment.

@maurolepore
Copy link
Member

I wonder if https://github.com/r-lib/revdepcheck would help. I understand you can get such a report for a package you develop but I don't know if you can for any other package (cc' @jimhester).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants