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

Write tests #6

Open
ekho opened this issue Jan 12, 2017 · 1 comment
Open

Write tests #6

ekho opened this issue Jan 12, 2017 · 1 comment

Comments

@ekho
Copy link
Owner

ekho commented Jan 12, 2017

there is no unit tests =(

@ScottA38
Copy link
Contributor

ScottA38 commented Mar 19, 2022

I was trying to consider this in my PR, however the main obstacle seems to be mocking, or at least providing a stable, unchanging example remote mock repo that doesn't change. In actual fact I have Googled for something and all that returns are API mocking libraries.

Edit: Looks like you don't need to mock a git repo, you can do it all locally

So, is it known:

  • Whether git uses some kind of REST API
  • Can there be a VPS set up to allow a git repository that never changes? One candidate is AWS codecommit, but this is likely paid. This is likely a more robust solution
    Secondary questions:
    - How would the rakefile test read the remote? Would there be a git init on the test/ directory with submodule config for the VPS added? Then we would be committing refs and hashes I believe 😬 Could instead add reference to setting up a separate dir as the test remote repo and symlink?

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

No branches or pull requests

2 participants