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

Increase Unit Test Coverage (Currently at 16%) #374

Open
Sonichigo opened this issue Feb 13, 2025 · 0 comments
Open

Increase Unit Test Coverage (Currently at 16%) #374

Sonichigo opened this issue Feb 13, 2025 · 0 comments

Comments

@Sonichigo
Copy link

Due diligence

My actions before raising this issue

Before you ask for help or support, make sure that you've consulted the manual for faasd. We can't answer questions that are already covered by the manual.

Why do you need this?

Currently, the test coverage for the project is only 16%, which may lead to untested edge cases, regressions, and potential stability issues. Improving test coverage will enhance reliability, maintainability, and confidence in future updates.

Who is this for?

What company is this for? Are you listed in the ADOPTERS.md file?

Not an Adopter

Expected Behaviour

  1. The project should have a higher unit test coverage (goal: 80%).
  2. New features and modules should have corresponding tests.

Current Behaviour

  1. The current unit test coverage is only 16%.
  2. Many critical components lack adequate tests.
  3. Potential regressions may go unnoticed.

List All Possible Solutions and Workarounds

Which Solution Do You Recommend?

  1. Identify untested modules and write new unit tests.
  2. Improve existing tests to cover edge cases.

Steps to Reproduce (for bugs)

  1. Run the below command
go test ./... -cover -coverprofile=coverage.out && go tool cover -func=coverage.out | tail -n 1
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

No branches or pull requests

1 participant