Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved Unit Test Coverage from 51.6% to 58.1% with Keploy AI #1505

Open
wants to merge 14 commits into
base: master
Choose a base branch
from

Conversation

shivamsouravjha
Copy link

@shivamsouravjha shivamsouravjha commented Feb 7, 2025

Hey,
I’ve added new unit tests to the Go codebase while testing the capabilities of my Keploy AI testing agent. The tests ensure reliable coverage by validating code builds, eliminating flaky tests, and improving overall test stability. Here’s what the AI checks for:

  • Ensures new tests build without errors.
  • Confirms no flaky tests are introduced.
  • Enhances coverage for previously untested areas.
    Coverage Breakdown:
  • Total Coverage Increased: 51.6% to 54.8%

Command to run

go test ./... -cover -coverprofile=coverage.out && go tool cover -func=coverage.out | tail -n 1

let me know if there is anything else I can add.

Unverified

This commit is not signed, but one or more authors requires that any commit attributed to them is signed.
Signed-off-by: shivamsouravjha <[email protected]>

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
@shivamsouravjha shivamsouravjha changed the title chore: add unit tests Improved Unit Test Coverage from 51.6% to 53.8% with Keploy AI Feb 7, 2025
@shivamsouravjha shivamsouravjha changed the title Improved Unit Test Coverage from 51.6% to 53.8% with Keploy AI Improved Unit Test Coverage from 51.6% to 54.8% with Keploy AI Feb 7, 2025
@shivamsouravjha shivamsouravjha changed the title Improved Unit Test Coverage from 51.6% to 54.8% with Keploy AI Improved Unit Test Coverage from 51.6% to 58.1% with Keploy AI Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant