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

Refine patterns used for vic-machine service end-to-end tests #6508

Closed
zjs opened this issue Oct 4, 2017 · 2 comments
Closed

Refine patterns used for vic-machine service end-to-end tests #6508

zjs opened this issue Oct 4, 2017 · 2 comments
Labels
area/api The Vritual Container Host management API component/install component/test Tests not covered by a more specific component label kind/architecture team/lifecycle
Milestone
Sprint 20 Lifecycle

Comments

@zjs
Copy link
Member

zjs commented Oct 4, 2017

The vic-machine service product is establishing new patterns for organization of end-to-end test code. Towards the end of the project, we should revisit the results and make sure it's what we want to merge to master.

See #6475 (review) for more context.
@zjs zjs added area/api The Vritual Container Host management API component/test Tests not covered by a more specific component label component/install kind/architecture team/lifecycle labels Oct 4, 2017
@zjs zjs mentioned this issue Oct 4, 2017
Closed
@anchal-agrawal
Copy link
Contributor

@zjs Please add an estimate and priority, thanks.

@zjs zjs added this to the Sprint 20 Lifecycle milestone Nov 2, 2017
@zjs
Copy link
Member Author

zjs commented Nov 2, 2017

Fixed by #6666

@zjs zjs closed this as completed Nov 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/api The Vritual Container Host management API component/install component/test Tests not covered by a more specific component label kind/architecture team/lifecycle
Projects
None yet
Milestone
Sprint 20 Lifecycle
Development

No branches or pull requests
2 participants
@zjs @anchal-agrawal