Order of e2e tests execution spread across multiple *.go files

[przemolb]

What do you want to see?

Hello everyone,
(this is not
I would like to split all e2e tests across different *_test.go files for maintenance purposes.
How do I enforce specific order of all Test* functions from different *_test.go files ? Is there any way I can do that ?

Extra Labels

No response

[vladimirvivien]

@przemolb I don't know of a way to force execution order of test functions spread across multiple files.

• You can try to name your test functions with numerical suffix (i.e. TestMyFunc01(..), TestMyFunc02(..), etc).
• You can write a test driver function that calls your own tests in order

func TestDriver(t *testing.T){
    myTestA(t)
    myTestB(t)
 ...
}
func myTestA(t *testing.T)
func myTestB(t *testing.T)

Hope that helps.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale