# Testing

## E2E Test

We can run E2E test by adding `run-e2e` label to your PR.

E2E test will deploy `eks-provider` to cluster dev-seed-us-west-2 namespace e2e-pr-{PR_NUM}, so you can find log in [grafana](https://grafana.oauth.dev.shared.aws.tidbcloud.com/explore?orgId=1&left=%7B%22datasource%22:%22loki%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Bcluster%3D%5C%22seed%2Feks%2Fus-west-2%5C%22,container%3D%5C%22eks-provider%5C%22,namespace%3D%5C%22e2e-pr-531%5C%22%7D%22%7D%5D,%22range%22:%7B%22from%22:%22now-24h%22,%22to%22:%22now%22%7D%7D). expr example: `{cluster="seed/eks/us-west-2",container="eks-provider",namespace="e2e-pr-531"}`

Objects created by e2e will have labels `cloud.pingcap.com/reconciler=e2e-pr-{PR_NUM}`, so you can find resources by command:

```bash
kubectl get network -A -l cloud.pingcap.com/reconciler=e2e-pr-531
kubectl describe network -A -l cloud.pingcap.com/reconciler=e2e-pr-531
```

## Joint Test

To do full chain test with core-svc and web console, we need to deploy the eks-provider into a regional controlplane, and then run test in [TiQA](http://tiqa.pingcap.net). Learn more about TiQA in this [doc](https://pingcap.feishu.cn/wiki/wikcnjwGqtYV3PiIg0vSSF7AGCb#0XhxcO)