> 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/intro-to-sealights/what-is-sealights/working-in-conjunction-with-your-quality-coverage-tools/sealights-vs-sonarqube.md).

# SeaLights vs SonarQube

While both SeaLights and SonarQube are valuable tools for software development, they cater to different aspects of the quality assurance process. Here's a comparison table highlighting their key differences:

| Feature                               | SeaLights                                                                | SonarQube                                       |
| ------------------------------------- | ------------------------------------------------------------------------ | ----------------------------------------------- |
| **Target Audience**                   | Developers, QA owners, testers, product owners, executives               | Developers working locally on unit tests        |
| **Focus**                             | **Quality improvement and test optimization across the entire pipeline** | **Static code analysis and code quality**       |
| **Code Coverage**                     | All test types (unit, integration, API, manual, etc.)                    | Primarily unit tests (limited setup for others) |
| **Modified Code Coverage**            | Analyzes coverage specifically for changed code                          | Not applicable                                  |
| **Test Gap Analysis**                 | Shows gaps across all testing stages and types                           | Shows gaps only for unit tests                  |
| **Code Coverage Analysis**            | Tracks coverage trends across builds, teams, etc.                        | Shows coverage data for the current build only  |
| **Quality Gates**                     | Policy-based across the entire pipeline                                  | Primarily for pull requests and unit tests      |
| **Coverage Trend Analytics**          | Out-of-the-box reports with insights                                     | Requires additional configuration               |
| **Test Prioritization**               | Recommends tests to skip based on code changes                           | No test prioritization                          |
| **Test Optimization**                 | Automatically skips unimpacted tests                                     | No test optimization                            |
| **Out-of-the-Box Risk Notifications** | Policy-based notifications via email or Slack                            | No out-of-the-box notifications                 |
| **SOC 2 Type II Compliance**          | Yes                                                                      | Please check with the vendor                    |
| **Source Code Access**                | Not required                                                             | Requires full access to the code base           |

### **Key Takeaways**

* SeaLights focuses on **optimizing testing efforts** across the entire development lifecycle, providing insights into **all test types** and **modified code coverage**.
* SonarQube focuses on **code quality**, helping developers write better code through **static code analysis**.
* While they don't directly integrate, SeaLights and SonarQube can **work together** to provide a **comprehensive view of software quality**.
* Choosing the right tool depends on your specific needs and the stage of the development process.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sealights.io/knowledgebase/intro-to-sealights/what-is-sealights/working-in-conjunction-with-your-quality-coverage-tools/sealights-vs-sonarqube.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.