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.

Sign up for GitHub

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

Jump to bottom

Integration tests #31

Closed
ysbaddaden opened this issue Sep 9, 2015 · 2 comments
Closed

Integration tests #31

ysbaddaden opened this issue Sep 9, 2015 · 2 comments
Labels
kind:feature
Milestone
v0.4.0

Comments

@ysbaddaden
Copy link
Contributor

In order to properly test the lock file behavior , integration tests are required. They would use the compiled shards binary and generate/manipulate different shard.yml in different project folders and test the outcome (what dependencies are installed, failures, if it correctly uses the lock file, updates the dependencies and lock file, ...)

refs #12 and #27
@ysbaddaden ysbaddaden added this to the v0.4.0 milestone Sep 9, 2015
@jhass
Copy link
Member

jhass commented Sep 9, 2015

An interesting tool for this could be aruba.

@ysbaddaden
Copy link
Contributor Author

Implemented in d02a1db

I didn't need aruba, after all, since I already had almost everything at hand (forging Git repositories, running shell commands, ...)

@ysbaddaden ysbaddaden mentioned this issue Sep 10, 2015
Merged
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind:feature
Projects
None yet
Milestone
v0.4.0
Development

No branches or pull requests
3 participants
@ysbaddaden @jhass @straight-shoota