Add v2 node provider for accepting status updates
This allows the use of a built-in provider to do things like mark a node as ready once all the controllers are spun up. The e2e tests now use this instead of waiting on the pod that the vk provider is deployed in to be marked ready (this was waiting on /stats/summary to be serving, which is racey).
This commit is contained in:
@@ -21,7 +21,7 @@ type ShouldSkipTestFunc func(string) bool
|
||||
|
||||
// TestSuite contains methods that defines the lifecycle of a test suite
|
||||
type TestSuite interface {
|
||||
Setup()
|
||||
Setup(t *testing.T)
|
||||
Teardown()
|
||||
}
|
||||
|
||||
@@ -39,7 +39,7 @@ type testCase struct {
|
||||
func Run(t *testing.T, ts TestSuite) {
|
||||
defer failOnPanic(t)
|
||||
|
||||
ts.Setup()
|
||||
ts.Setup(t)
|
||||
defer ts.Teardown()
|
||||
|
||||
// The implementation below is based on https://github.com/stretchr/testify
|
||||
|
||||
@@ -20,7 +20,7 @@ type basicTestSuite struct {
|
||||
testsRan []string
|
||||
}
|
||||
|
||||
func (bts *basicTestSuite) Setup() {
|
||||
func (bts *basicTestSuite) Setup(t *testing.T) {
|
||||
bts.setupCount++
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user