End 2 End Tests

Integration tests are e2e tests that invoke Handler methods directly and ignore networking completely.
True e2e tests are Black-box tests that invoke network endpoint.

Start Cluster

start minimal e2e test cluster locally

# start
kubectl apply -f build/kubernetes.local.yaml
# stop
kubectl delete -f build/kubernetes.local.yaml

(Or) start production like e2e test cluster locally

# start
kubectl apply -f build/kubernetes.production.yaml
# stop
kubectl delete -f  build/kubernetes.production.yaml

E2E Test via REST Gateway

Use REST Client tests for manual testing

E2E Test via gRPC Gateway

• set envelopment variables for CI e2e tests via micro proxy.
• You can also run this test against local standalone service(go run ./service/greeter), without any extra settings

# e2e tests in CI envelopment with micro gRPC Gateway
MICRO_PROXY_ADDRESS="localhost:8081" \
make test-e2e
# e2e tests against local standalone services
make test-e2e
go test -v ./e2e/...
MICRO_PROXY_ADDRESS="localhost:8081" micro publish gkit.service.emailer '{"to": "sumo@demo.com"}'

Benchmark

assume Account service running at localhost:8080

make run-account ARGS="--server_address=localhost:8080"

# set `host` and full path for `import-paths` in config.json
~/Developer/Apps/ghz/ghz --config ./e2e/ghz-account-config.json

Reference

• Simple gRPC benchmarking and load testing tool https://ghz.sh