[CI] MeshSync E2E test #286
Conversation
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
KiptoonKipkurui
requested review from
leecalcote,
MUzairS15,
theBeginner86 and
MarioArriaga92
KiptoonKipkurui
added
area/ci
|
Once on track, we can discuss the trigger event, currently just at on [push] |
Signed-off-by: Daniel Kiptoon <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #286 +/- ##
======================================
Coverage 9.37% 9.37%
======================================
Files 10 10
Lines 651 651
======================================
Hits 61 61
Misses 583 583
Partials 7 7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
Signed-off-by: Daniel Kiptoon <[email protected]>
…ach time we add a resource to be tracked Signed-off-by: Daniel Kiptoon <[email protected]>
|
@MUzairS15 @MarioArriaga92 I have replaced all sleep statements with appropriate kubectl commands and so far here's the final product. Some things to note, with multiple Kubernetes versions to test for in the matrix, random Kubernetes versions may fail at different times in different tests for example My observation over several runs is that the tests largely fail at the following stages
You may have good pointers here, so let me know if there's anything I can do to make this test consistent |
|
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
bot
added
the
issue/stale
|
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue. |
Description
This PR introduces a new workflow e2etests.yaml that adds end to end test for MeshSync. By design, MeshSync discovers resources within a Kubernetes cluster and watches them for events [ADDED, MODIFIED and DELETED] events, these events are published via a NATS to a topic (
meshery.meshsync.core). The strategy therefore for this test, is to run MeshSync against a Kubernetes cluster, and subscribe to the topic that it publishes its discovered Kubernetes object events' at, then within a 3 minutes(Subject to discussion) it should have discovered some resources otherwise marked as a failure.This PR fixes #285
Notes for Reviewers
Signed commits