39b6916cbc
These wrapper functions set labels in addition to injecting the annotation into
the test text. It then becomes possible to select tests in different ways:
ginkgo -v --focus="should respect internalTrafficPolicy.*\[FeatureGate:ServiceInternalTrafficPolicy\]"
ginkgo -v --label-filter="FeatureGate:ServiceInternalTrafficPolicy"
ginkgo -v --label-filter="Beta"
When a test runs, ginkgo shows it as:
[It] should respect internalTrafficPolicy=Local Pod to Pod [FeatureGate:ServiceInternalTrafficPolicy] [Beta] [FeatureGate:ServiceInternalTrafficPolicy, Beta]
The test name and the labels at the end are in different colors. Embedding the
annotations inside the text is redundant and only done because users of the e2e
suite might expect it. Also, our tooling that consumes test results currently
doesn't know about ginkgo labels.
Environments, features and node features as described by
https://github.com/kubernetes/enhancements/tree/master/keps/sig-testing/3041-node-conformance-and-features
are also supported.
The framework and thus (at the moment) test/e2e do not have any pre-defined
environments and features. Adding those and modifying tests will follow in
a separate commit.
62 lines
1.7 KiB
Go
62 lines
1.7 KiB
Go
/*
|
|
Copyright 2023 The Kubernetes Authors.
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License");
|
|
you may not use this file except in compliance with the License.
|
|
You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|
|
*/
|
|
|
|
package unittests
|
|
|
|
import (
|
|
"bytes"
|
|
"flag"
|
|
"testing"
|
|
|
|
"github.com/stretchr/testify/require"
|
|
"k8s.io/kubernetes/test/e2e/framework"
|
|
)
|
|
|
|
// GetFrameworkOutput captures writes to framework.Output during a test suite setup
|
|
// and returns it together with any explicit Exit call code, -1 if none.
|
|
// May only be called once per test binary.
|
|
func GetFrameworkOutput(t *testing.T, flags map[string]string) (output string, finalExitCode int) {
|
|
// This simulates how test/e2e uses the framework and how users
|
|
// invoke test/e2e.
|
|
framework.RegisterCommonFlags(flag.CommandLine)
|
|
framework.RegisterClusterFlags(flag.CommandLine)
|
|
for flagname, value := range flags {
|
|
require.NoError(t, flag.Set(flagname, value), "set %s", flagname)
|
|
}
|
|
var buffer bytes.Buffer
|
|
framework.Output = &buffer
|
|
framework.Exit = func(code int) {
|
|
panic(exitCode(code))
|
|
}
|
|
finalExitCode = -1
|
|
defer func() {
|
|
if r := recover(); r != nil {
|
|
if code, ok := r.(exitCode); ok {
|
|
finalExitCode = int(code)
|
|
} else {
|
|
panic(r)
|
|
}
|
|
}
|
|
output = buffer.String()
|
|
}()
|
|
framework.AfterReadingAllFlags(&framework.TestContext)
|
|
|
|
// Results set by defer.
|
|
return
|
|
}
|
|
|
|
type exitCode int
|