ComplyCube
Coveralls
CodeClimate
Codacy
SensioLabs Insight
ESLint
Codecov
Phabricator
Source-Navigator NG
SonarQube
Codacy
CodeClimate
Checkmarx
Coverity Scan
Snyk
ReSharper
PyCharm
SonarQube, a core component of the Sonar solution, is an open source, self-managed tool that systematically helps developers and organizations deliver Clean Code. SonarQube integrates into the developers' CI/CD pipeline and DevOps platform to detect and help fix issues in the code while performing continuous inspection of projects.
Supported by the Sonar Clean as You Code methodology, only code that meets the defined quality standard can be released to production. SonarQube analyzes the most popular programming languages, frameworks, and infrastructure technologies and supports over 5,000 Clean Code rules.
Trusted by 7 million developers and 400,000 organizations globally to clean more than half a trillion lines of code, Sonar has become integral to delivering better software.
Explore our pricing and request an evaluation: https://www.sonarsource.com/plans-and-pricing/
Coveralls SonarQubeBased on our record, Coveralls seems to be a lot more popular than SonarQube. While we know about 13 links to Coveralls, we've tracked only 1 mention of SonarQube. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Cpan_coverage: This calculates the coverage of your test suite and reports the results. It also uploads the results to coveralls.io. - Source: dev.to / 3 months ago
I will normally use GitHub Actions to automatically run my test suite on each push, on every major version of Perl I support. One of the test runs will load Devel::Cover and use it to upload test coverage data to Codecov and Coveralls. - Source: dev.to / about 1 year ago
Coveralls.io — Display test coverage reports, free for Open Source. - Source: dev.to / over 1 year ago
Several years ago I got into Travis CI and set up lots of my GitHub repos so they automatically ran the tests each time I committed to the repo. Later on, I also worked out how to tie those test runs into Coveralls.io so I got pretty graphs of how my test coverage was looking. I gave a talk about what I had done. - Source: dev.to / over 1 year ago
This approach will create two json coverage files, which will be merged together by NYC. Therefore the results will be purely local. If You don't mind using online tools like Codecov or Coveralls for merging data from different tests, then go ahead and use them. They will probably also be more accurate. But if You still want to learn how to get coverage from E2E, then please read through. - Source: dev.to / almost 2 years ago
Even for Java, C# and JS we do enforce such kind of rules, e.g. https://sonarqube.org. - Source: Hacker News / over 1 year ago
CodeClimate - Code Climate provides automated code review for your apps, letting you fix quality and security issues before they hit production. We check every commit, branch and pull request for changes in quality and potential vulnerabilities.
Codacy - Automatically reviews code style, security, duplication, complexity, and coverage on every change while tracking code quality throughout your sprints.
SensioLabs Insight - PHP Project Quality Done Right.
Checkmarx - The industry’s most comprehensive AppSec platform, Checkmarx One is fast, accurate, and accelerates your business.
ESLint - The fully pluggable JavaScript code quality tool
Coverity Scan - Find and fix defects in your Java, C/C++ or C# open source project for free