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

Add better test coverage for #6647 #6821

Open
vburenin opened this issue Nov 21, 2017 · 1 comment
Open

Add better test coverage for #6647 #6821

vburenin opened this issue Nov 21, 2017 · 1 comment
Labels
component/test Tests not covered by a more specific component label priority/p2 team/foundation team/lifecycle

Comments

@vburenin
Copy link
Contributor

vburenin commented Nov 21, 2017

User Statement:
#6647 is not covered by direct test, however, that logic runs every time VCH boots or gets new IP address via DHCP. The test coverage is not that trivial. As functional test requirement two things needs to be tested, the trace path as well as the content of bridge.out routing table on VCH.

Acceptance Criteria:
bridge.out contains a network route to the network where default VCH gateway is.
default gateway doesn't appear in trace path when container traces path to the IP address that in the same network where default VCH gateway is. (use different IP from default gateway).

@mhagen-vmware mhagen-vmware added component/test Tests not covered by a more specific component label priority/p0 team/lifecycle labels Nov 22, 2017
@zjs
Copy link
Member

zjs commented Dec 1, 2017

Sending back for estimation by the team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/test Tests not covered by a more specific component label priority/p2 team/foundation team/lifecycle
Projects
None yet
Development

No branches or pull requests

5 participants