Skip to content
This repository has been archived by the owner on Mar 16, 2024. It is now read-only.

Increase Test Coverage to 80% #54

Open
emrgnt-cmplxty opened this issue Jun 23, 2023 · 0 comments
Open

Increase Test Coverage to 80% #54

emrgnt-cmplxty opened this issue Jun 23, 2023 · 0 comments
Labels

Comments

@emrgnt-cmplxty
Copy link
Owner

emrgnt-cmplxty commented Jun 23, 2023

Test coverage is a crucial aspect of maintaining a healthy, robust codebase. It allows us to ensure that our code is appropriately validated and can help in the early detection of bugs and issues. Currently, our test coverage stands at 64.52%, as per our latest Codecov report. Our aim is to raise this to a minimum of 80% to increase the reliability of our codebase and ensure that critical functionalities are adequately tested. Achieving this goal will require concerted effort and detailed understanding of our codebase and its various components.

Here are the steps you can follow to increase the test coverage:

  1. Identify Uncovered Areas: Utilize Codecov or a similar tool to find out the test coverage line by line and file by file. Identify the areas of code that are not currently covered by our tests. This will give us a clear idea of where we need to focus our efforts.

  2. Prioritize Critical Code: Prioritize the uncovered code sections based on their importance and potential impact. Critical functionalities that affect the overall performance of the system should be prioritized.

  3. Write Comprehensive Tests: Write unit tests that cover the previously uncovered areas. Ensure the tests cover a range of scenarios and edge cases to make them as thorough as possible.

  4. Review and Refactor Existing Tests: Review the existing tests and look for potential improvements. There might be overlapping tests that can be refactored or removed to increase efficiency.

  5. Continuous Monitoring: Keep monitoring the test coverage reports after adding or updating the tests. Continuous monitoring will help us maintain or increase the coverage percentage.

Please note that while increasing test coverage is important, it's crucial to focus on the quality of tests rather than just the quantity. Higher test coverage with poorly written tests can give a false sense of security. The goal should be to write effective and efficient tests that truly validate the functionality of our code.

In addition, make sure to document your process and learnings, which will serve as a valuable resource for the team in the future. Don't hesitate to ask questions or seek help if needed. Your contributions to this project are greatly appreciated!

See the last test result here -

Codecov Report

❗ No coverage uploaded for pull request base (main@3a54c5c). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #51   +/-   ##
=======================================
  Coverage        ?   64.52%           
=======================================
  Files           ?       54           
  Lines           ?     3614           
  Branches        ?        0           
=======================================
  Hits            ?     2332           
  Misses          ?     1282           
  Partials        ?        0           
Flag Coverage Δ
unittests 64.52% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Huntemall pushed a commit to Huntemall/automata-dev that referenced this issue Oct 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant