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

Improve test coverage #39

Open
BomBardyGamer opened this issue Jun 17, 2021 · 1 comment
Open

Improve test coverage #39

BomBardyGamer opened this issue Jun 17, 2021 · 1 comment
Assignees
Labels

Comments

@BomBardyGamer
Copy link
Member

BomBardyGamer commented Jun 17, 2021

Description

We use a plugin called PIT to generate test mutation results, which shows me that the current report for the API has the following stats:

  • Line coverage: 90%
  • Mutation coverage: 73%
  • Test strength: 98%

Which are very good statistics, but I believe we should introduce some testing further than just unit tests, possibly some integration testing, and we also need to do some acceptance and compatibility testing.

Furthermore, the statistics for the server on the other hand, are rather poor:

  • Line coverage: 4%
  • Mutation coverage: 2%
  • Test strength: 79%

This is due to my primary method of testing being manually starting the software, which is required, but I believe we can test much more rigorously than this.

@BomBardyGamer BomBardyGamer added this to the Stable release milestone Jun 17, 2021
@BomBardyGamer BomBardyGamer self-assigned this Jun 17, 2021
@BomBardyGamer
Copy link
Member Author

I also think we should look in to better integration testing, like what Minestom has implemented, to help reduce the amount of manual testing I have to perform when testing this, which is a hell of a lot, and most of the time, I find myself skipping most of the testing, or even all of it sometimes, as I do not want to manually test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

No branches or pull requests

1 participant