-
Notifications
You must be signed in to change notification settings - Fork 13
Add test suite for the git vcs provider #58
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
base: master
Are you sure you want to change the base?
Add test suite for the git vcs provider #58
Conversation
5d447c6 to
ce9c90c
Compare
ce9c90c to
0dda984
Compare
|
The commit tests are working locally, they are probably failing in CI due to missing author info |
071d805 to
4fc6c6b
Compare
| } | ||
|
|
||
| [Fact] | ||
| public void DetectingGitOnMachineWorks() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: can we make a negative test for this as well?
I am not sure how to go about it, but currently the implementation could just be return true and the test would pass :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess we could but I'm not sure how easily that is done - I do agree with your comment though.
running it on a machine without git in CI will not work, as it won't be able to get the source code - but perhaps altering the path for the process info we use to launch the tool will work.
| } | ||
|
|
||
| [Fact] | ||
| public void IsRepositoryCleanWorks() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue: add test with dirty state as well
4fc6c6b to
6264b57
Compare
This PR will
IVcsprovider to allow passing in a working directoryGitVcsto use passed working directoryCloses #57