You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 29, 2021. It is now read-only.
This issue has been automatically marked as stale because it has not had activity in 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.
Overview
Add suites for integration tests to reduce test time and reduce cluster instances on CI.
Each test in suite should reuse nsm / forwarder.
For example:
We have a suite of tests for cluster:
TestNSCDiesSingleNode
TestSimpleMemifConnection
TestNSCDiesMultiNode
TestNSEDiesMultiNode
How it will work:
TestNSCDiesSingleNode
started on CI. It checks namespaceNSM_NAMESPACE
and doesn't find NSM PODs*. The test will deploy NSM PODs.TestSimpleMemifConnection
started on CI. It checks namespaceNSM_NAMESPACE
and finds NSM PODs. The test will reuse NSM PODs.TestNSCDiesMultiNode
started on CI. It checks namespaceNSM_NAMESPACE
and finds NSM PODs. The test will reuse NSM PODs.TestNSEDiesMultiNode
started on CI. It checks namespaceNSM_NAMESPACE
and finds NSM PODs. The test will reuse NSM PODs.NSM_NAMESPACE
for the cluster.Total : suite reduces (max(deploy nsmgr time, deploy forwarder time) + max(cleanup forwarder time, cleanup nsmgr time))
x 3
NSM PODs are forwarder and nsmgr.
Bugs which has been found by testing suites on CI
#2007
#1898
#1895
#1914
...
PRs
First implementation:
After splitting at parts:
The text was updated successfully, but these errors were encountered: