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

Fix tests #8

Merged
merged 1 commit into from Dec 23, 2014
Merged

Fix tests #8

merged 1 commit into from Dec 23, 2014

Conversation

dmcgowan
Copy link
Owner

Fixes the unit tests, assuming the behavior change is accurate. Changing to use the REGISTRY endpoint to v2 breaks the integration tests since the latest version of the registry is not deployed.

Signed-off-by: Derek McGowan <derek@mcgstyle.net>
@stevvooe
Copy link
Collaborator

LGTM!

@stevvooe
Copy link
Collaborator

Should there be a test that ensures once the APIVersion is changed, the string is updated?

@dmcgowan
Copy link
Owner Author

Probably, doesn't seem to be wide coverage on the endpoint code. However I would wait until after the factor is merged before spending time increasing coverage.

@jlhawn
Copy link

jlhawn commented Dec 23, 2014

Should there be a test that ensures once the APIVersion is changed, the string is updated?

This would require a much larger integration test which actually pings the endpoint.

since it does fix the currently borked test cases, LGTM.

@dmcgowan dmcgowan merged commit 47c5b1e into v2-registry Dec 23, 2014
@dmcgowan dmcgowan deleted the v2-registry-testfix1 branch June 15, 2016 17:11
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

Successfully merging this pull request may close these issues.

None yet

3 participants