Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chapter on workflow #9

Open
sckott opened this issue Feb 26, 2019 · 8 comments
Open

Chapter on workflow #9

sckott opened this issue Feb 26, 2019 · 8 comments
Assignees

Comments

@sckott
Copy link
Collaborator

sckott commented Feb 26, 2019

including:

  • re-recording cassettes, how often, when to do it, etc.
  • maybe advice on adding make tasks for handling fixtures?
  • others?
@maelle
Copy link
Member

maelle commented Feb 26, 2020

Other thing: your excellent advice on turning wifi off to see what happens (e.g. after you added fixtures).

@sckott
Copy link
Collaborator Author

sckott commented Feb 26, 2020

good idea

@maelle
Copy link
Member

maelle commented Mar 2, 2020

Likewise, if you want to see if your tests can run in the absence of an API key, disable it and run the tests! E.g. open .Renviron, add a character in the API key name, restart R, run the test, fix your key.

@maelle
Copy link
Member

maelle commented Oct 23, 2020

touched upon in the whole games chapters. (except re-recording)

@maelle
Copy link
Member

maelle commented Dec 8, 2020

@sckott
Copy link
Collaborator Author

sckott commented Dec 8, 2020

not yet, haven't done that myself yet. any make tasks would be based on e.g., ropensci/vcr#103

@maelle
Copy link
Member

maelle commented Dec 8, 2020

should we leave this issue opened?

@sckott
Copy link
Collaborator Author

sckott commented Dec 8, 2020

yes i think so

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

No branches or pull requests

2 participants