When Mauricio started working on Kubernetes one of his first tasks was to run the Kubernetes storage e2e tests with a CSI Driver, e2e tests run by compiling the e2e test codebase onto a binary called e2e.test, while running tests Mauricio wanted to stop at some specific part of the test to check the status of the cluster which previously required adding sleep statements in the test and recompiling the e2e.test binary, as Mauricio was learning go tooling he found Delve which enables setting breakpoints on go programs but saw that it wasn't integrated with the way Kubernetes run e2e tests. Mauricio added a way to debug the e2e tests with Delve, in this talk Mauricio will talk about how Delve works and how it's used with the e2e.test binary to debug tests. This talk is for people that want to contribute to Kubernetes but don't know where to start, in Mauricio's opinion you can start from the e2e tests and by setting breakpoints and analyzing the cluster state based on what the test does you'll understand how Kubernetes works.