Code Coverage

[kevinthedang]

Issue

• We don't exactly know how much of our codebase is covered to ensure there is no regression in functionality. We have a command that can be found in the package.json called "test:coverage": "vitest run --coverage"

Solution

• Implement some kind of visual in the readme on how much the code is covered.
• It would also be nice to investigate how to put the code coverage in the PR (with some quick research it might be tough).
  • This would be useful as if code coverage goes down, we want to implement tests to mitigate or even improve coverage.

References

• 14

• 60

[JT2M0L3Y]

Something like CodeCov may be worth checking out for this. However, this looks to be the most promising if this repository's ownership migrates to an organization.

Using a GitHub gist, this example could also be implemented: Gist-Based Coverage.

This is a way to do it with a gh-pages branch: Pages. This would brush up alongside ideas about #17.

These are available at a free-tier basis for open-source projects, but will require administration by the owner of this repository alone.

[kevinthedang]

In all honesty, are we really going to implement #17? It was an interesting idea, but it seems against the idea of a "Discord Chat Bot" when you just move to a webpage.

Considering a close on #17 because it will become extraneous to this project. What do you think?

@JT2M0L3Y

[JT2M0L3Y]

I was thinking the same thing. Plus, it's what everyone else seems to be interested in doing with Ollama. I will close #17 now.