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

[CI] E2E tests MeshSync #285

Open
KiptoonKipkurui opened this issue Dec 17, 2023 · 3 comments
Open

[CI] E2E tests MeshSync #285

KiptoonKipkurui opened this issue Dec 17, 2023 · 3 comments
Assignees
Labels
area/ci Continuous integration | Build and release issue/willfix This issue will be worked on

Comments

@KiptoonKipkurui
Copy link
Member

Current Behavior

MeshSync does not have integration tests that test the functionality of MeshSync against an actual Kubernetes Cluster.

Desired Behavior

Implement Integration test that ensures MeshSync functions as expected when deployed against a Kubernetes cluster.

Implementation

Acceptance Tests


Contributor Guides and Resources

@KiptoonKipkurui KiptoonKipkurui added the area/ci Continuous integration | Build and release label Dec 17, 2023
@KiptoonKipkurui KiptoonKipkurui self-assigned this Dec 17, 2023
@leecalcote
Copy link
Member

Good!

Copy link

stale bot commented Feb 3, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Feb 3, 2024
@saurabh100ni saurabh100ni added issue/willfix This issue will be worked on and removed issue/stale Issue has not had any activity for an extended period of time labels Feb 8, 2024
@ayushrakesh
Copy link

@leecalcote @saurabh100ni This issue is still open? @KiptoonKipkurui has closed one linked PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci Continuous integration | Build and release issue/willfix This issue will be worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants