@@ -35,22 +35,28 @@ And use "EnvFile" GoLand plugin to read the env variables from the generated `.e
3535
3636### End-to-End Testing
3737
38- Run the following command to run the end-to-end tests against the Kubernetes cluster pointed to by ` kubectl config current-context ` :
39- You should set up the correct ` REGION ` env variable and create ` non-default `
40- namespace if it doesn't exist.
41-
42- NOTE: You'll need to allow in-bound traffics from lattice prefix list in the security
43- groups of your cluster.
44-
45- ``` bash
46- # create non-default namespace if it hasn't existed yet
38+ To run end-to-end tests against your local controller you need:
39+ - aws account and fetch credentials for "default" profile
40+ - follow deploy.md steps, except a few last steps for controller deployment to EKS
41+ - setup env vars
42+ - create EKS cluster
43+ - allow traffic from Lattice IP to EKS cluster
44+ - create IAM OIDC provider and policy
45+ - install CRD's (see above)
46+ - create non-default namespace
47+ ```
4748kubectl create namespace non-default
48-
49- export REGION=us-west-2
50- make e2etest
49+ ```
50+ - start local controller (in background or new session)
51+ ```
52+ REGION=us-west-2 make run
53+ ```
54+ - run tests against local controller
55+ ```
56+ REGION=us-west-2 make e2etest
5157```
5258
53- Pass ` FOCUS ` environment variable to run some specific test cases based on filter condition.
59+ You can use ` FOCUS ` environment variable to run some specific test cases based on filter condition.
5460You could assign the string in the Describe("xxxxxx") or It("xxxxxx") to the FOCUS environment variable to run the specific test cases.
5561``` go
5662var _ = Describe (" HTTPRoute path matches" , func () {
0 commit comments