All Projects → ioquatix → Covered

ioquatix / Covered

Programming Languages

ruby
36898 projects - #4 most used programming language

Labels

Projects that are alternatives of or similar to Covered

Coverage.vim
code coverage vim plugin
Stars: ✭ 106 (-32.91%)
Mutual labels:  coverage
Openpojo
POJO Testing & Identity Management Made Trivial
Stars: ✭ 122 (-22.78%)
Mutual labels:  coverage
Osvvm
OSVVM Utility Library: AlertLogPkg, CoveragePkg, RandomPkg, ScoreboardGenericPkg, MemoryPkg, TbUtilPkg, TranscriptPkg, ...
Stars: ✭ 140 (-11.39%)
Mutual labels:  coverage
Teaspoon
Teaspoon: Javascript test runner for Rails. Use Selenium, BrowserStack, or PhantomJS.
Stars: ✭ 1,443 (+813.29%)
Mutual labels:  coverage
Jacoco Plugin
Jenkins JaCoCo Plugin
Stars: ✭ 119 (-24.68%)
Mutual labels:  coverage
Lcov To Cobertura Xml
Converts lcov output to Cobertura-compatible XML for CI
Stars: ✭ 131 (-17.09%)
Mutual labels:  coverage
S2e
S2E: A platform for multi-path program analysis with selective symbolic execution.
Stars: ✭ 102 (-35.44%)
Mutual labels:  coverage
Single cov
Actionable code coverage.
Stars: ✭ 154 (-2.53%)
Mutual labels:  coverage
Example Swift
Codecov: Swift coverage example
Stars: ✭ 121 (-23.42%)
Mutual labels:  coverage
Mutant
Automated code reviews via mutation testing - semantic code coverage.
Stars: ✭ 1,794 (+1035.44%)
Mutual labels:  coverage
Bashcov
Code coverage tool for Bash
Stars: ✭ 113 (-28.48%)
Mutual labels:  coverage
Sbt Jacoco
JaCoCo Code Coverage plug-in for sbt.
Stars: ✭ 115 (-27.22%)
Mutual labels:  coverage
Typescript Coverage Report
Node command tool to generate TypeScript coverage report
Stars: ✭ 138 (-12.66%)
Mutual labels:  coverage
Infection
PHP Mutation Testing library
Stars: ✭ 1,575 (+896.84%)
Mutual labels:  coverage
Gradle Pitest Plugin
Gradle plugin for PIT Mutation Testing
Stars: ✭ 144 (-8.86%)
Mutual labels:  coverage
Awesome Open Hardware Verification
A List of Free and Open Source Hardware Verification Tools and Frameworks
Stars: ✭ 103 (-34.81%)
Mutual labels:  coverage
Example Cpp11 Cmake
Stars: ✭ 129 (-18.35%)
Mutual labels:  coverage
D.s.a Leet
References and summary for leetcode high-frequency algorithm problems
Stars: ✭ 155 (-1.9%)
Mutual labels:  coverage
Moderncppstarter
🚀 Kick-start your C++! A template for modern C++ projects using CMake, CI, code coverage, clang-format, reproducible dependency management and much more.
Stars: ✭ 2,381 (+1406.96%)
Mutual labels:  coverage
Sonar Flutter
SonarQube plugin for Flutter / Dart
Stars: ✭ 138 (-12.66%)
Mutual labels:  coverage

Covered

Actions Status Coverage Status

Covered uses modern Ruby features to generate comprehensive coverage, including support for templates which are compiled into Ruby.

  • Incremental coverage - if you run your full test suite, and the run a subset, it will still report the correct coverage - so you can incrementally work on improving coverage.
  • Integration with RSpec, Minitest, Travis & Coveralls - no need to configure anything - out of the box support for these platforms.
  • Supports coverage of views - templates compiled to Ruby code can be tracked for coverage reporting.

Screenshot

Motivation

Existing Ruby coverage tools are unable to handle evaled code. This is because the coverage module built into Ruby doesn't expose the necessary hooks to capture it. Using the parser gem allows us to do our own source code analysis to compute executable lines, thus making it possible to compute coverage for "templates".

It's still tricky to do it correctly, but it is feasible now to compute coverage of web application "views" by using this technique. This gem is an exploration to see what is possible.

Installation

Add this line to your application's Gemfile:

gem 'covered'

RSpec Integration

In your spec/spec_helper.rb add the following before loading any other code:

require 'covered/rspec'

Ensure that you have a .rspec file with --require spec_helper:

--require spec_helper
--format documentation
--warnings

Minitest Integration

In your test/test_helper.rb add the following before loading any other code:

require 'covered/minitest'
require 'minitest/autorun'

In your test files, e.g. test/dummy_test.rb add the following at the top:

require_relative 'test_helper'

Usage

When running rspec, you can specify the kind of coverage analysis you would like:

COVERAGE=Summary rspec

If no COVERAGE is specified, coverage tracking will be disabled.

Partial Summary

COVERAGE=PartialSummary rspec

This report only shows snippets of source code with incomplete coverage.

Brief Summary

COVERAGE=BriefSummary rspec

This report lists several files in order of least coverage.l

Coveralls/Travis Integration

You can send coverage information to Coveralls by editing your .travis.yml file:

matrix:
  include:
    - rvm: 2.6
      env: COVERAGE=PartialSummary,Coveralls

This will print out a brief report and then upload the coverage data. This integrates transparently with Travis.

See Also

  • coveralls-ruby – the official Coveralls implementation for Ruby.
  • simplecov – one of the original coverage implementations for Ruby, uses the built-in coverage library.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License

Released under the MIT license.

Copyright, 2018, by Samuel G. D. Williams.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

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].