My Keploy Contribution: Go Resource Management
While tracking popular repositories on GitHub trending with my awesome-trending-repos project, I came across Keploy, a modern API testing tool written in Go. While exploring the codebase, I found a...

Source: DEV Community
While tracking popular repositories on GitHub trending with my awesome-trending-repos project, I came across Keploy, a modern API testing tool written in Go. While exploring the codebase, I found a couple of resource management bugs that I could fix. Keploy is a modern tool for automated testing and mock generation for APIs, Integration, and E2E tests. What is Keploy? Keploy is an open-source tool for API and integration testing. It provides features like mock creation and test generation, and has over 8k stars on GitHub. It integrates with VSCode through an extension. The VSCode extension allows Keploy to manage tests and mocks directly from the IDE. While examining the codebase, I noticed some common resource management mistakes in Go. I fixed these issues with two separate PRs. PR #3927: The Use-After-Close Bug Discovering the Problem While browsing the project's GitHub issues, I came across #3821, which reported a bug in the isGoBinary function in utils/utils.go. The file was being