Name		Name	Last commit message	Last commit date
parent directory ..
controller		controller
extensions		extensions
framework		framework
README.md		README.md
allocator_test.go		allocator_test.go
fleet_test.go		fleet_test.go
fleetautoscaler_test.go		fleetautoscaler_test.go
gameserver_test.go		gameserver_test.go
gameserverallocation_test.go		gameserverallocation_test.go
main_test.go		main_test.go
ping_test.go		ping_test.go

README.md

E2E Testing

End-to-end (e2e) testing is automated testing for real user scenarios.

Prerequisites:

a running k8s cluster (kube config is passed as arguments).
Have kubeconfig file ready.
(optional) set the IMAGE_PULL_SECRET env var to the secret name needed to pull the gameserver and/or Agones SDK images, if needed

e2e tests are written as Go test. All go test techniques apply, e.g. picking what to run, timeout length.

To run e2e tests on your kubectl configured cluster:

make test-e2e

To run on minikube use the special target:

make minikube-test-e2e