From: danieldasilvaferreira@... Date: 2018-01-15T22:07:32+00:00 Subject: [ruby-core:84884] [Ruby trunk Bug#9572] Restarting Coverage does not produce correct coverage result Issue #9572 has been updated by dsferreira (Daniel Ferreira). Well, well, well Aaron. What have you been doing? Gmail has an eye on you! Your messages are being considered spam. :-) Is it just me again? ---------------------------------------- Bug #9572: Restarting Coverage does not produce correct coverage result https://bugs.ruby-lang.org/issues/9572#change-69591 * Author: sean_ferguson (Sean Ferguson) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.0dev (2018-01-13 trunk 61811) [x86_64-darwin15] * Backport: ---------------------------------------- Feature 4796(https://www.ruby-forum.com/topic/1811306#1001864) appears to have a bug in it. While the test listed there does pass the following test does not:

require "test/unit"
require "coverage"
require 'tmpdir'
class TestCoverage < Test::Unit::TestCase
  def test_restarting_coverage
    Dir.mktmpdir {|tmp|
      Dir.chdir(tmp) {
        File.open("test.rb", "w") do |f|
          f.puts <<-EOS
            def coverage_test_method
              puts :ok
            end
          EOS
        end
        Coverage.start
        require tmp + '/test.rb'
        Coverage.result
        Coverage.start
        coverage_test_method
        result = Coverage.result
        assert_equal 1, result.size
        assert_equal [0, 1, nil], result.first[1] # coverage stats show an empty array here
      }
    }
  end
end

It appears that while the coverage is finding the correct files it is not giving any coverage stats for those files. Knowing this information would be very helpful in determining test coverage data for individual test files. I'm not very familiar with how the coverage library works, but if you can point me at where to look I can give fixing it a try. Thanks, Sean Ferguson -- https://bugs.ruby-lang.org/ Unsubscribe: