> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/others/why-sealights-uses-method-coverage.md). # Why SeaLights Uses Method Coverage? Unlike unit test coverage where you are testing only the specific methods and therefore need that higher granularity, SeaLights captures coverage from the entire business flow through all the methods and other services. This means that even though there will be situations where methods are considered covered when not all their branches were covered, all the methods those uncovered lines call will not be covered and will be reflected through them in the modified coverage (and they will appear in the testing gap analysis that SeaLights provides). We have found from our experience that the gain in accuracy is small whereas the increase in difficulty of investigation is major and therefore recommend to concentrate on the method level. This is because SeaLights concentrates on the modified coverage which is the highest risk area. Looking at line coverage will increase the number of untested modified code to a number that will be hard to work on and that discourages teams from closing their testing gaps and raising their quality. Our customers that only used method coverage successfully increased their quality and reduced production issues by over 90% without the need to work with line coverage. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sealights.io/knowledgebase/setup-and-configuration/troubleshooting-faq/others/why-sealights-uses-method-coverage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.