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

Add coverage #784

Merged
merged 1 commit into from
Jun 17, 2024
Merged

Add coverage #784

merged 1 commit into from
Jun 17, 2024

Conversation

AlexProgrammerDE
Copy link
Contributor

No description provided.

@AlexProgrammerDE AlexProgrammerDE changed the base branch from master to dev January 8, 2024 18:51
@AlexProgrammerDE AlexProgrammerDE changed the base branch from dev to master May 14, 2024 05:26
@Kas-tle
Copy link
Member

Kas-tle commented Jun 17, 2024

Is this still needed, and if so for what purpose?

@AlexProgrammerDE
Copy link
Contributor Author

It's not "needed". It's a nice-to-have. Coverage checks how much of the library code you're actually testing inside of your tests. So like a coverage of 25% means you test 25% of your library code inside unit tests.

@Kas-tle Kas-tle merged commit 5624d77 into GeyserMC:master Jun 17, 2024
1 check passed
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.

2 participants