#
lcov
Here are 76 public repositories matching this topic...
-
Updated
Feb 1, 2021 - C++
Dead simple testing framework for Bash with coverage reporting
-
Updated
Aug 11, 2020 - Shell
SonarQube plugin for TypeScript files
-
Updated
Jul 8, 2019 - Java
Creates and updates README testing coverage badges with your json-summary
nyc
readme
coverage
jest
istanbul
husky
lcov
c8
lcov-report
jest-badges-readme
githooks
istanbul-badges-readme
-
Updated
Jun 7, 2021 - TypeScript
Github Action which helps enforce code coverage threshold using lcov created by Very Good Ventures 🦄
-
Updated
May 31, 2021 - JavaScript
A massively parallelized gcov wrapper
-
Updated
Feb 3, 2021 - Python
Danger.js plugin for monitoring code coverage on changed files.
-
Updated
Mar 9, 2021 - TypeScript
phptt a.k.a php test tools
php
test
docker-image
generate
testing-tools
gcov
lcov
php-versions
php-qa
php-test
phpt
phptestfest
phptestfestbrasil
-
Updated
Apr 20, 2019 - Shell
Github action to convert go coverage files to lcov format
-
Updated
Nov 22, 2020
Generates public Apex test coverage reports for your Force.com open-source projects
-
Updated
Aug 8, 2018 - Go
A Github Action which helps enforce code coverage
-
Updated
Oct 28, 2020 - Shell
-
Updated
Mar 17, 2021 - Shell
Parse and format LCOV coverage reports, in JavaScript.
-
Updated
May 22, 2020 - JavaScript
A Yeoman generator for C++ projects.
git
bootstrap
template
cmake
cpp
yeoman
yeoman-generator
googletest
doxygen
scaffolding
lcov
generator-cpp
-
Updated
Dec 5, 2017 - JavaScript
Sample project for setting-up Gitlab CI/CD with CMake, googletest, lcov for C++-based applications
-
Updated
Aug 12, 2019 - C++
Improve this page
Add a description, image, and links to the lcov topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the lcov topic, visit your repo's landing page and select "manage topics."
Reference
ryanluker/vscode-coverage-gutters#239 (comment)
Problem
The old names for the coverage elements (highlights) is quite confusing now that we have gutter coverage elements as well as line and map based ones. We can use the example naming by @DevilXD as a starting point for switching to something more sensical.
Work