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
Is your feature request related to a problem? Please describe.
The current draft e2e is written in bash across a series of files, which yield a set of tremendous github workflow yamls
This cannot be run locally easily, and has a high adoption cost to get into the build-test-iteration loop
Migrating to a go-based testing framework for e2e would allow the tests to be run locally easier, and make them much faster to test
Describe alternatives you've considered
Keep the tests in gh actions
You should use this if testing on a private cluster isn't a requirement. Our current e2e tests in Draft use a local cluster which works nicely with the k8s sig e2e framework.
this is a good idea, it looks like the k8s-e2e-framework doesn't support kubectl apply, so we'd test by marshaling the created manifests into k8s objects or using the corresponding clients to bake for helm/kustomize
Is your feature request related to a problem? Please describe.
The current draft e2e is written in bash across a series of files, which yield a set of tremendous github workflow yamls
This cannot be run locally easily, and has a high adoption cost to get into the build-test-iteration loop
Migrating to a go-based testing framework for e2e would allow the tests to be run locally easier, and make them much faster to test
Describe alternatives you've considered
Keep the tests in gh actions
Additional context
something like the testing implemented in https://github.com/Azure/aks-app-routing-operator by @OliverMKing
The text was updated successfully, but these errors were encountered: