All Projects → naver → Cover Checker

naver / Cover Checker

Licence: apache-2.0
Check your pull request code coverage

Programming Languages

java
68154 projects - #9 most used programming language

Projects that are alternatives of or similar to Cover Checker

behat-code-coverage
Generate Code Coverage reports for Behat tests
Stars: ✭ 48 (+0%)
Mutual labels:  code-coverage
frankencover.it
Code coverage for iOS and OSX.
Stars: ✭ 102 (+112.5%)
Mutual labels:  code-coverage
Nyc
the Istanbul command line interface
Stars: ✭ 4,858 (+10020.83%)
Mutual labels:  code-coverage
cpp14-project-template
A simple, cross-platform, and continuously integrated C++14 project template
Stars: ✭ 64 (+33.33%)
Mutual labels:  code-coverage
instrumentation
Assorted pintools
Stars: ✭ 24 (-50%)
Mutual labels:  code-coverage
Cpp Project
Boiler plate template for C++ projects, with CMake, Doctest, Travis CI, Appveyor, Github Actions and coverage reports.
Stars: ✭ 328 (+583.33%)
Mutual labels:  code-coverage
tarpaulin
📈 GitHub Action for code coverage reporting with tarpaulin
Stars: ✭ 69 (+43.75%)
Mutual labels:  code-coverage
Modern Cpp Template
A template for modern C++ projects using CMake, Clang-Format, CI, unit testing and more, with support for downstream inclusion.
Stars: ✭ 690 (+1337.5%)
Mutual labels:  code-coverage
next-and-cypress-example
Next.js example instrumented for code coverage from Cypress tests
Stars: ✭ 111 (+131.25%)
Mutual labels:  code-coverage
Utplsql
Testing Framework for PL/SQL
Stars: ✭ 402 (+737.5%)
Mutual labels:  code-coverage
node example
ROS node examples with parameter server, dynamic reconfigure, timers, and custom messages for C++ and Python.
Stars: ✭ 90 (+87.5%)
Mutual labels:  code-coverage
mutant-swarm
Mutation testing framework and code coverage for Hive SQL
Stars: ✭ 20 (-58.33%)
Mutual labels:  code-coverage
Afl Cov
Produce code coverage results with gcov from afl-fuzz test cases
Stars: ✭ 342 (+612.5%)
Mutual labels:  code-coverage
jacoco-report
Github action that publishes the JaCoCo report as a comment in the Pull Request
Stars: ✭ 31 (-35.42%)
Mutual labels:  code-coverage
Codecov Action
GitHub Action that uploads coverage to Codecov ☂️
Stars: ✭ 625 (+1202.08%)
Mutual labels:  code-coverage
instrument-cra
Little module for CRA applications to instrument code without ejecting react-scripts
Stars: ✭ 61 (+27.08%)
Mutual labels:  code-coverage
Tester
Tester: enjoyable unit testing in PHP with code coverage reporter. 🍏🍏🍎🍏
Stars: ✭ 281 (+485.42%)
Mutual labels:  code-coverage
Simplifyify
A simplified Browserify and Watchify CLI
Stars: ✭ 37 (-22.92%)
Mutual labels:  code-coverage
Istanbuljs
monorepo containing the various nuts and bolts that facilitate istanbul.js test instrumentation
Stars: ✭ 656 (+1266.67%)
Mutual labels:  code-coverage
Altcover
Cross-platform coverage gathering and processing tool set for .net/.net core and Mono
Stars: ✭ 344 (+616.67%)
Mutual labels:  code-coverage

Coverage Checker Build Status

CoverChecker provides a test coverage for new added lines of code. If you create new pull request, CoverChecker would give feedback regarding how much of the new lines your test code has covered.

Good Test code makes people find bug more efficiently before service release and prevents service from being disabled. To check the test code quality, most of developers refer the code coverage status as an important index. This is why most of them spend their resources to update their test code to achieve more code coverage whenever they add new lines of code. However, it has been hard to check and improve the code coverage as there are lots of old legacy codes which is not within the scope of the current test code.

Spring REST doc is one of spring component. it makes api document from test code.

CoverChecker provides a feature to check the code coverage for new added code, not a whole code. It will reduce the pressure to cover the whole and help you to achieve more coverage steadly and efficiently. Makes your code more durable!

CoverChecker do...

example

  • Find new code line from pull request
  • Get test coverage each file from coverage report
  • Combine information and check test code cover new code line
  • Write report on pull request
  • CoverChecker will fail when coverage doesn't satisfy your goal

Run with jenkins

  1. Install jdk 8 on your ci
  2. Build CoverChecker
  3. Fix your project to generate test coverage report(CoverChecker only Jacoco or Cobertura)
  4. Execute CoverChecker in you build job

How to build

Use maven wrapper

./gradlew clean build jar

then maven would make jar cover-checker-console/build/libs/cover-checker-${version}-all.jar

Create access token

Create a access token

Execute with parameter

java -jar cover-checker-console/build/libs/cover-checker-${version}-all.jar \
    --cover ${coverageReportPath} \
    [--cover ${otherCoverageReportPath}] \
    --github-token ${githubAccessToken} \
    --repo ${githubRepositoryPath} \
    --threshold ${coverageThreshold} \
    --github-url ${githubHost} \
    --pr ${pullrequestNo} \
    -type (jacoco | cobertura)

Parameter

usage: coverchecker.jar -c <arg> [-d <arg>] [-dt <arg>] [-ft <arg>] [-g <arg>]
       [-p <arg>] [-r <arg>] -t <arg> [-type <arg>] [-u <arg>]
-c,--cover <arg>          coverage report paths(absolute recommend), coverage
                          report path can take multiple paths for multi-module
                          project
-d,--diff <arg>           diff file path(absolute recommend)
-dt,--diff-type <arg>     diff type (github | file)
-ft,--file-threshold <arg>coverage report type (jacoco | cobertura) default is
                          jacoco
-g,--github-token <arg>   github oauth token
-p,--pr <arg>             github pr number
-r,--repo <arg>           github repo
-t,--threshold <arg>      coverage pass threshold
-type <arg>               coverage report type (jacoco | cobertura) default is
                          jacoco
-u,--github-url <arg>     The url when you working on github enterprise url.
                          default is api.github.com

License

Copyright 2018 NAVER Corp.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].