slatherorg / slather Goto Github PK

The config right now is pretty annoying -- you have to make .slather.yml, modify .travis.yml, and also potentially add stuff to the Podfile. It'd be nice to use something like highline to walk the user through things by asking them questions and then automatically creating/modifying files.

I know that there is no solution yet that allows to generate gcno for swift yet, but I would like to have this issue tracked separately to be alerted when it will be available in Slather. Thanks!

As far as I can tell, it's only used to add those two build options. It kills me to see it take forever to gem install xcodeproj, activesupport, etc on CI.

Maybe, slather-core that's just what you need on CI and keep xcodeproj in regular slather. Just a thought.

It's possible to set up a project such that there are duplicate gcno files produced. VENTokenField use to have a project org issue where this happened, where 1 copy would have the correct test coverage and the other would have 0% coverage.

Hi,

Considering that I choosed to use relative location of DerivedData to prevent interferences of compilation through different projects, I'm not seeing somewhere where I could tell to use a specific DerivedDara location for Slather to find the gcov files.

Am I missing something or the path to the DerivedData directory is static?

Something I have noticed when running slather in the wild.
If you have an empty source file (or a file with the code commented out) you get a lot of errors like the one below.
I think we do not check defensively enough for nil values on the coverage data when calculating line and branch coverage data:

/Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/coverage_file.rb:68:in `cleaned_gcov_data': undefined method `gsub' for nil:NilClass (NoMethodError)
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/coverage_file.rb:56:in `line_coverage_data'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/coverage_file.rb:91:in `num_lines_testable'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/coverage_file.rb:99:in `percentage_lines_tested'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/project.rb:57:in `each'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/project.rb:57:in `max_by'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/project.rb:57:in `block in dedupe'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/project.rb:57:in `map'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/project.rb:57:in `dedupe'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/project.rb:51:in `coverage_files'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/lib/slather/coverage_service/simple_output.rb:13:in `post'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/bin/slather:58:in `post'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/bin/slather:34:in `execute'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/clamp-0.6.3/lib/clamp/subcommand/execution.rb:11:in `execute'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/clamp-0.6.3/lib/clamp/command.rb:125:in `run'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/clamp-0.6.3/lib/clamp.rb:6:in `Clamp'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/gems/slather-1.5.0/bin/slather:6:in `<top (required)>'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/bin/slather:23:in `load'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/bin/slather:23:in `<main>'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/bin/ruby_executable_hooks:15:in `eval'
    from /Users/xxxxx/.rvm/gems/ruby-2.0.0-p247/bin/ruby_executable_hooks:15:in `<main>'

The description for --simple-output should be different from the description for --coveralls

We have a single repo that has multiple projects under a single workspace because they share dependancies. We handle testing with a shared scheme that builds the test targets for each project.
Is there a way to setup slather to handle this scenario?

How do I install Slather onto my Mac?

I tried sudo gem install slather, but it gets so far and crashes.

Building native extensions. This could take a while...
ERROR: Error installing slather:
ERROR: Failed to build gem native extension.

/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby extconf.rb

checking if the C compiler accepts ... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers. Check the mkmf.log file for more details. You may
need configuration options.

Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
--help
--clean
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/mkmf.rb:434:in try_do': The compiler failed to generate an executable file. (RuntimeError) You have to install development tools first. from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/mkmf.rb:549:inblock in try_compile'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/mkmf.rb:500:in with_werror' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/mkmf.rb:549:intry_compile'
from extconf.rb:80:in nokogiri_try_compile' from extconf.rb:87:inblock in add_cflags'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/mkmf.rb:599:in with_cflags' from extconf.rb:86:inadd_cflags'
from extconf.rb:337:in `

Gem files will remain installed in /Library/Ruby/Gems/2.0.0/gems/nokogiri-1.6.6.4 for inspection.
Results logged to /Library/Ruby/Gems/2.0.0/gems/nokogiri-1.6.6.4/ext/nokogiri/gem_make.out

Hey friends,

I'm the founder of Codecov and would like to accept uploads from Slather. I simply need an example output file I can parse into our format on Codecov.

Thank you for your time!

Are you trying to see these visually locally? Would be interesting to be able to open straight in Coverstory

https://code.google.com/p/coverstory/

Related: https://github.com/socialize/socialize-project-helpers-ios/blob/master/export-coverstory.sh

I don't think installing slather should automatically screw with all pod installs without there being any way to turn it off save for deleting the plugin from the Gem. I don't think it is a safe assumption that everyone who uses slather and CocoaPods wants it in all projects.

I'm getting this crash when running slather:

Slathering...
/Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/2.1.0/fileutils.rb:1454:in `unlink': No such file or directory @ unlink_internal - AccountsViewController.m.gcov (Errno::ENOENT)
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/2.1.0/fileutils.rb:1454:in `block in remove_file'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/2.1.0/fileutils.rb:1459:in `platform_support'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/2.1.0/fileutils.rb:1453:in `remove_file'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/2.1.0/fileutils.rb:791:in `remove_file'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/2.1.0/fileutils.rb:569:in `block in rm'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/2.1.0/fileutils.rb:568:in `each'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/2.1.0/fileutils.rb:568:in `rm'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:50:in `block in gcov_data'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:50:in `each'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:50:in `gcov_data'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:57:in `coverage_data'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:83:in `num_lines_tested'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:91:in `percentage_lines_tested'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/project.rb:57:in `each'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/project.rb:57:in `max_by'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/project.rb:57:in `block in dedupe'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/project.rb:57:in `map'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/project.rb:57:in `dedupe'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/project.rb:51:in `coverage_files'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/lib/slather/coverage_service/simple_output.rb:13:in `post'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/bin/slather:57:in `post'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/bin/slather:33:in `execute'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/clamp-0.6.3/lib/clamp/subcommand/execution.rb:11:in `execute'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/clamp-0.6.3/lib/clamp/command.rb:125:in `run'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/clamp-0.6.3/lib/clamp.rb:6:in `Clamp'
        from /Users/ksmiley/.rbenv/versions/2.1.3/lib/ruby/gems/2.1.0/gems/slather-1.3.0/bin/slather:6:in `<top (required)>'
        from /Users/ksmiley/.rbenv/versions/2.1.3/bin/slather:23:in `load'
        from /Users/ksmiley/.rbenv/versions/2.1.3/bin/slather:23:in `<main>'
        from /Users/ksmiley/.rbenv/versions/2.1.3/bin/ruby_executable_hooks:15:in `eval'
        from /Users/ksmiley/.rbenv/versions/2.1.3/bin/ruby_executable_hooks:15:in `<main>'

I'm seeing this with ruby 2.1.3 and 1.9.3

context

Suggestion from @marklarr:

• Log when we've successfully configured pods for slather
• Log each GCNO file that is ignored (ones for files that aren't your source files, and also duplicate ones.)
• Log each GCNO file that is processed, along with its
• created_at timestamp
• modified_at timestamp
• Contents? Seems too noisy... but it'd be nice to at least see a couple.
• Add some sort of #inspect method to Slather::CoverageFile class, and print out this as well.
• Add coverage_service specific logging to each of the services. For example, for coveralls, print out the JSON blob that it'll send to coveralls, and the response from coveralls after it has been posted.

Hello slather developers,

I have noticed that development activity on this project has slowed down over the last four months. Could anyone of you give me an update on how the project is currently maintained? There are open issues related to Xcode 7 and the changes that have been introduced with it, coverage formats in particular.

Since many of us are using slather not only on their pet projects but also on the job we need development in the flow especially when working actively on iOS 9 / watchOS / tvOS projects.

I would love to hear from you.

Regards
tarbrain

I'm currently trying to add functionality to slather to output coverage files as static htmls. I've already added the basic functionality in my branch and currently trying to add tests to cover those up.

Although, I had a problem when running the tests in my local machine. I'm currently running Mac OS X 10.10.3, ruby 2.0.0p481 and Xcode 6.3.1. What I did was:

• Clone repo
• bundle install
• bundle exec rspec

Firstly, I have a warning from iPhone simulator saying that the service could not established. Here is the warning message:
xcodebuild[3176:118116] [MT] iPhoneSimulator: SimVerifier returned: Error Domain=NSPOSIXErrorDomain Code=53 "Simulator verification failed." UserInfo=0x7f91a1d6e280 {NSLocalizedFailureReason=A connection to the simulator verification service could not be established., NSLocalizedRecoverySuggestion=Ensure that Xcode.app is installed on a volume with ownership enabled., NSLocalizedDescription=Simulator verification failed.}

Secondly, I have 3 tests failing, which all related to the fixture Branches.m on line 13. It seems that somehow the generated outputs differ from the fixture files. Below are my rspec failures:

  1) Slather::CoverageService::CoberturaXmlOutput#post should create an XML report spanning all coverage files
     Failure/Error: EquivalentXml.equivalent?(current_xml_doc, fixture_xml_doc).should be_truthy
       expected: truthy value
            got: false
     # ./spec/slather/coverage_service/cobertura_xml_spec.rb:38:in `block (3 levels) in <top (required)>'

  2) Slather::CoverageService::GutterJsonOutput#post should print out the coverage for each file, and then total coverage
     Failure/Error: expect(current_json).to be_json_eql(fixture_json)
       Expected equivalent JSON
       Diff:

       @@ -185,10 +185,9 @@
                "short_text": "-"
              },
              {
       -        "background_color": "0x35CC4B",
                "line": 13,
                "long_text": "",
       -        "short_text": "2"
       +        "short_text": "-"
              },
              {
                "line": 14,

       @@ -432,10 +431,9 @@
                "short_text": "-"
              },
              {
       -        "background_color": "0xFC635E",
                "line": 13,
                "long_text": "",
       -        "short_text": "#####"
       +        "short_text": "-"
              },
              {
                "line": 14,
     # ./spec/slather/coverage_service/gutter_json_spec.rb:26:in `block (3 levels) in <top (required)>'

  3) Slather::CoverageService::SimpleOutput#post should print out the coverage for each file, and then total coverage
     Failure/Error: fixtures_project.post
       #<Slather::Project> path:`/Users/ikhsan/Open Source/slather/spec/fixtures/fixtures.xcodeproj` UUID:`8C9A2025195965F00013B6B3` received :puts with unexpected arguments
         expected: ("spec/fixtures/fixtures/fixtures.m: 2 of 4 lines (50.00%)")
              got: ("spec/fixtures/fixtures/more_files/Branches.m: 9 of 19 lines (47.37%)")
     # ./lib/slather/coverage_service/simple_output.rb:23:in `block in post'
     # ./lib/slather/coverage_service/simple_output.rb:13:in `each'
     # ./lib/slather/coverage_service/simple_output.rb:13:in `post'
     # ./spec/slather/coverage_service/simple_output_spec.rb:32:in `block (3 levels) in <top (required)>'

In contradiction, I pushed the same commit to run it on travis. It works fine. I'd really appreciate it if you guys could shed some light on how to run the tests properly.

Many thanks for this wonderful library! 👍

Hello Slather team,
I am new to Slather and am trying to set it up for coverage report.
I am using the following branch:
gem 'slather', :git => "https://github.com/mattdelves/slather.git", :branch => "feature-profdata"

I am trying to generate an Html report for my iOS project and used the following command:
"slather coverage --html --show"

and get the following error:

//.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/lib/slather/coverage_file.rb:50:in gcov_data': undefined methodbasename' for nil:NilClass (NoMethodError)
from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/lib/slather/coverage_file.rb:72:in cleaned_gcov_data' from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/lib/slather/coverage_file.rb:81:inline_coverage_data'
from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/lib/slather/coverage_info.rb:5:in num_lines_tested' from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/lib/slather/coverage_service/html_output.rb:62:inblock in create_index_html'
from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/lib/slather/coverage_service/html_output.rb:61:in each' from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/lib/slather/coverage_service/html_output.rb:61:increate_index_html'
from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/lib/slather/coverage_service/html_output.rb:41:in create_html_reports' from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/lib/slather/coverage_service/html_output.rb:19:inpost'
from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/bin/slather:80:in post' from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/bin/slather:46:inexecute'
from //.rvm/gems/ruby-2.1.0/gems/clamp-0.6.5/lib/clamp/command.rb:67:in run' from //.rvm/gems/ruby-2.1.0/gems/clamp-0.6.5/lib/clamp/subcommand/execution.rb:11:inexecute'
from //.rvm/gems/ruby-2.1.0/gems/clamp-0.6.5/lib/clamp/command.rb:67:in run' from //.rvm/gems/ruby-2.1.0/gems/clamp-0.6.5/lib/clamp/command.rb:132:inrun'
from //.rvm/gems/ruby-2.1.0/gems/clamp-0.6.5/lib/clamp.rb:6:in Clamp' from //.rvm/gems/ruby-2.1.0/bundler/gems/slather-d09ce4f5d592/bin/slather:6:in<top (required)>'
from //.rvm/gems/ruby-2.1.0/bin/slather:23:in load' from //.rvm/gems/ruby-2.1.0/bin/slather:23:in

Can some one please advice on what i am doing wrong?

Thank you

via @kylef's https://github.com/kylef/CGFloatType

Hi guys!

I was trying to use slather for the first time and noticed that it couldn't find the gcda coverage files for my test target, specifying the exact location of the test target with the -b flag fixed it.

Is this working the way it is intended to work or is there something about my project configuration that makes it fail?

I'm using Xcode 6.1.1 and my tests are strictly unit tests built into a separate target (I'm not hooking the tests on the actual application).

Thank you!

I'm currently looking into slather as our tool of choice to measure code coverage in connection with coveralls.io

When I initially tried to setup slather as mentioned in the README.txt through
slather setup Project.xcodeproj
my whole .pbxproj file got rewritten (as what the diff showed me) due to different ways of formatting the file.

My next step, was using
slather coverage -s Project.xcodeproj
to measure my code coverage. Unfortunately, this is where everything breaks and slather starts to throw the stack trace at me.

The error message looks like this:

Slathering...
/Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/lib/slather/project.rb:49:in `coverage_files': No coverage files found. Are you sure your project is setup for generating coverage files? Try `slather setup your/project.pbxproj` (StandardError)
    from /Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/lib/slather/coverage_service/simple_output.rb:13:in `post'
    from /Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/bin/slather:64:in `post'
    from /Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/bin/slather:36:in `execute'
    from /Users/florian/.rvm/gems/ruby-2.2.0/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
    from /Users/florian/.rvm/gems/ruby-2.2.0/gems/clamp-0.6.3/lib/clamp/subcommand/execution.rb:11:in `execute'
    from /Users/florian/.rvm/gems/ruby-2.2.0/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
    from /Users/florian/.rvm/gems/ruby-2.2.0/gems/clamp-0.6.3/lib/clamp/command.rb:125:in `run'
    from /Users/florian/.rvm/gems/ruby-2.2.0/gems/clamp-0.6.3/lib/clamp.rb:6:in `Clamp'
    from /Users/florian/.rvm/gems/ruby-2.2.0/gems/slather-1.5.4/bin/slather:6:in `<top (required)>'
    from /Users/florian/.rvm/gems/ruby-2.2.0/bin/slather:23:in `load'
    from /Users/florian/.rvm/gems/ruby-2.2.0/bin/slather:23:in `<main>'
    from /Users/florian/.rvm/gems/ruby-2.2.0/bin/ruby_executable_hooks:15:in `eval'
    from /Users/florian/.rvm/gems/ruby-2.2.0/bin/ruby_executable_hooks:15:in `<main>'

After investigating into this for several hours, I found another "example" project which is using Slather + Coveralls.io and their slather support is broken as well.
The project I was looking into is the XNGAPIClient, which had their last successful measurement in mid December (see this build Travis CI Coveralls.io).

As it's definitely not the difference between XCode 6.1 and XCode 6.1.1 (tried that), I tried to add these flags manually and slather started to work.

So afaik, the setup function of slather is not working right now and should be fixed ASAP as slather is more or less not useable in comparison with Travis CI (only with a customised setup).

So this is the first time I've used Slather + Coveralls, and I'm running into an issue as described here: intuit/LocationManager#37 (comment)

Running Slather locally on the Xcode project works fine:

$ slather coverage -s LocationManagerExample/LocationManagerExample.xcodeproj/
Slathering...
Source/INTULocationManager.m: 180 of 240 lines (75.00%)
Source/INTULocationRequest.m: 60 of 73 lines (82.19%)
Test Coverage: 76.68%
Slathered

However, something is failing when this runs on Travis, and as a result Coveralls shows 0% coverage (although Coveralls does show the correct source files). Here's the output from a Travis build: https://travis-ci.org/intuit/LocationManager/builds/59321046

Any idea if this a Slather or Coveralls issue and what I need to do to get this working?

Hi,

It seems that after updating Cocoapods to the latest version breaks slather, because it is depends on an older version of xcodeproj.

If there a way to fix this without downgrading Cocoapods ?

Error loading the plugin with path `/Users/nghimbovschi/.rbenv/versions/2.2.3/lib/ruby/gems/2.2.0/gems/slather-1.8.1/lib/cocoapods_plugin.rb`.

Gem::ConflictError - Unable to activate slather-1.8.1, because xcodeproj-0.28.2 conflicts with xcodeproj (~> 0.26.2)
/Users/nghimbovschi/.rbenv/versions/2.2.3/lib/ruby/2.2.0/rubygems/specification.rb:2112:in `raise_if_conflicts'
...

Given slather is installed, when you run pod install, then the targets in Pods.xcodeproj all have
Instrument Program Flow and Generate Test Coverage Files set to Yes, which makes the build fail for a project that doesn't have those flags set to Yes with the following:

Undefined symbols for architecture x86_64:
  "_llvm_gcda_emit_arcs", referenced from:
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSDictionary+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSMutableArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSNumber+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSSet+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSString+ObjectiveSugar.o)
  "_llvm_gcda_emit_function", referenced from:
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSDictionary+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSMutableArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSNumber+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSSet+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSString+ObjectiveSugar.o)
  "_llvm_gcda_end_file", referenced from:
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(Pods-SlatherTest-ObjectiveSugar-dummy.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSDictionary+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSMutableArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSNumber+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSSet+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSString+ObjectiveSugar.o)
      ...
  "_llvm_gcda_start_file", referenced from:
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(Pods-SlatherTest-ObjectiveSugar-dummy.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSDictionary+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSMutableArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSNumber+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSSet+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSString+ObjectiveSugar.o)
      ...
  "_llvm_gcda_summary_info", referenced from:
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(Pods-SlatherTest-ObjectiveSugar-dummy.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSDictionary+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSMutableArray+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSNumber+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSSet+ObjectiveSugar.o)
      ___llvm_gcov_writeout in libPods-SlatherTest-ObjectiveSugar.a(NSString+ObjectiveSugar.o)
      ...
  "_llvm_gcov_init", referenced from:
      ___llvm_gcov_init in libPods-SlatherTest-ObjectiveSugar.a(Pods-SlatherTest-ObjectiveSugar-dummy.o)
      ___llvm_gcov_init in libPods-SlatherTest-ObjectiveSugar.a(NSArray+ObjectiveSugar.o)
      ___llvm_gcov_init in libPods-SlatherTest-ObjectiveSugar.a(NSDictionary+ObjectiveSugar.o)
      ___llvm_gcov_init in libPods-SlatherTest-ObjectiveSugar.a(NSMutableArray+ObjectiveSugar.o)
      ___llvm_gcov_init in libPods-SlatherTest-ObjectiveSugar.a(NSNumber+ObjectiveSugar.o)
      ___llvm_gcov_init in libPods-SlatherTest-ObjectiveSugar.a(NSSet+ObjectiveSugar.o)
      ___llvm_gcov_init in libPods-SlatherTest-ObjectiveSugar.a(NSString+ObjectiveSugar.o)
      ...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I think that rather than forcing those flags to be Yes by default on any project, they should only be set once you run slather setup against your project.

It would be great if I could export multiple output with 1 line of command.

slather coverage -x --html --output-directory MyTests

Just thought I would post this here and see if there is a good solution. The build settings required by Slather break Bitcode. Related: soffes/RateLimit#18.

We need to figure out why we are getting this error:

[Coveralls] API internal error occured, we're on it!

🐙

i've executed slather setup xx.projct when i'm running test with cmd+u it failed:
Code Coverage Data Generation Failed
Unable to retrieve the profile data files from 'iPhone 5s

and the log show
2015-12-14 13:59:28.582 xctest[6447:734168] The bundle “MyTests.xctest” couldn’t be loaded. Try reinstalling the bundle.
2015-12-14 13:59:28.583 xctest[6447:734168

(dlopen(/Users/wx/Library/Developer/Xcode/DerivedData/My-akiykixzlljhyegfebcgflamfzgb/Build/Intermediates/CodeCoverage/My/Products/Debug-iphonesimulator/MyTests.xctest/MyTests, 265): Symbol not found: OBJC_CLASS$_AgreementViewController
Referenced from: /Users/wx/Library/Developer/Xcode/DerivedData/My-akiykixzlljhyegfebcgflamfzgb/Build/Intermediates/CodeCoverage/My/Products/Debug-iphonesimulator/MyTests.xctest/MyTests
Expected in: /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Xcode/Agents/xctest
in /Users/wx/Library/Developer/Xcode/DerivedData/My-akiykixzlljhyegfebcgflamfzgb/Build/Intermediates/CodeCoverage/My/Products/Debug-iphonesimulator/MyTests.xctest/MyTests)

Program ended with exit code: 83

I am using your feature-profdata branch for generating code coverage within my apps. I wanted to know when this will become part of a new release?

Also how can I exclude paths from the cobertura reports.

Even with ignore paths from my pods in the .yml file and bundle exec slather command I still get Pods in my results.

Any ideas where I might be going wrong.

Running the recommended

$ slather setup path/to/project.xcodeproj

ends up executing this code:

    def slather_setup_for_coverage
      build_configurations.each do |build_configuration|
        build_configuration.build_settings["GCC_INSTRUMENT_PROGRAM_FLOW_ARCS"] = "YES"
        build_configuration.build_settings["GCC_GENERATE_TEST_COVERAGE_FILES"] = "YES"
      end
    end

As currently written, I think that the effects of this (or manually modifying the project file in the same way) is problematic, because we end up turning these 2 flags on even for non-Debug/Test/Coverage builds. From my understanding of these flags, changing them from their default NO value ends up changing the compiled binary (as additional code is injected to perform the measurements). At the very least, this is bad because it's likely inefficient and causes unnecessary overhead. But it's also risky for production code, and a quick search on Google turns up some reports of app crashes and other nastiness in some situations when these flags are enabled.

Now, I don't think this will affect users who integrate the library with CocoaPods, since CocoaPods is generating its own Xcode project (right?), but if you use Carthage or a similar mechanism to build a framework or static library directly from the Xcode project in the repo itself, having these flags on for all build configurations will affect the generated artifacts.

I think these flags should only be set for Debug/Test/Coverage build configurations. The reason I am opening this issue instead of a PR is because I'm not sure the best way to do this...we could test against the build configuration name (looking for "Debug" or similar), or check for a preprocessor define of "DEBUG", or potentially something else.

FWIW, Apple recommends using a separate, new build configuration just for Coverage builds.

Thoughts?

I've tried to set up two different projects with Slather today (https://github.com/lazerwalker/MTLParseAdapter and https://github.com/intentkit/IntentKit – the former is much smaller/simpler, if you're looking for a test case). Both are failing for the same reason:

/Library/Ruby/Gems/2.0.0/gems/slather-1.7.0/lib/slather/project.rb:49:in `coverage_files': No coverage files found. 
Are you sure your project is setup for generating coverage files? 
Try `slather setup your/project.pbxproj` 
(StandardError)

Both of these are failing both locally and on Travis (e.g. https://travis-ci.org/lazerwalker/MTLParseAdapter/builds/59264653).

Poking around existing issues, it seems that's common if you've manually changed where the gcda files get placed. However, I haven't changed that for either of these projects. It also doesn't appear to be a local system-wide Xcode config issue, as I have other projects with similar setups that will let themselves be Slathered just fine.

Any thoughts?

Slather is not picking up the .gcno files in my project's build directory. To prove this, I ran tree on the folder where my project was built and grepped for the files on travis. They're there.

My slather config:

coverage_service: coveralls
xcodeproj: paq.xcodeproj
ignore:
  - catch.hpp

Looking at slather's source, it looks like it either thinks the file has no source file, or that it is in my ignore list. Neither seems to be true.

Is there any way to disable the "no source file" check? I can explicitly give slather the correct build directory to look in using the -b flag, so it can just blindly take all the .gcno files in there.

The error handling could be changed so this doesn't output a Ruby backtrace to the user.

$ slather coverage -s CGFloatTypeTests/CGFloatType.xcodeproj
/Users/kylef/gems/gems/slather-1.0.1/lib/slather/project.rb:34:in `coverage_files': No coverage files found. Are you sure your project is setup for generating coverage files? Try `slather setup your/project.pbxproj` (StandardError)
    from /Users/kylef/gems/gems/slather-1.0.1/lib/slather/coverage_service/simple_output.rb:13:in `post'
    from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:50:in `post'
    from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:30:in `execute'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/subcommand/execution.rb:11:in `execute'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:125:in `run'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp.rb:6:in `Clamp'
    from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:6:in `<top (required)>'
    from /Users/kylef/gems/bin/slather:23:in `load'
    from /Users/kylef/gems/bin/slather:23:in `<main>'

$ slather
Slathering...
/Users/kylef/gems/gems/slather-1.0.1/lib/slather/coverage_service/coveralls.rb:24:in `coveralls_coverage_data': Environment variable `TRAVIS_JOB_ID` not set. Is this running on a travis build? (StandardError)
    from /Users/kylef/gems/gems/slather-1.0.1/lib/slather/coverage_service/coveralls.rb:35:in `post'
    from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:50:in `post'
    from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:30:in `execute'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/subcommand/execution.rb:11:in `execute'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:67:in `run'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp/command.rb:125:in `run'
    from /Users/kylef/gems/gems/clamp-0.6.3/lib/clamp.rb:6:in `Clamp'
    from /Users/kylef/gems/gems/slather-1.0.1/bin/slather:6:in `<top (required)>'
    from /Users/kylef/gems/bin/slather:23:in `load'
    from /Users/kylef/gems/bin/slather:23:in `<main>'

I am trying to run slather on my Xcode 7 project slather, but I get the error "Failed to load coverage: No object file for requested architecture".
Here is the command I am running (as per the instructions in http://mgrebenets.github.io/mobile%20ci/2015/09/21/code-coverage-for-ios-xcode-7/)

bundle exec slather coverage --input-format profdata -s --ignore "../**/*/Xcode*" --output-directory slather-report --scheme MyApp MyApp.xcodeproj

Note 1: The DerivedData folder contains these two files - Coverage.profdata and ProfileData/MyApp-39997.profdata
Note 2: my project uses Pods and hence has a corresponding xcworkspace. Does this affect the use of slather?

Could someone please gem push slather.gem? It seems it is not available on rubygems.org: https://rubygems.org/gems/slather

Thanks!

Want to start getting unit tests into our app. My initial thought is to have a github blocker that if new or modified code gets checked and there needs to be a certain % of code coverage for that PR.

Is this possible with slather?

Once CocoaPods/CocoaPods#1755 is merged, we can use the post-install hook to enable the settings and user's wont need to add the following the their Podfile's:

begin
  require 'slather'
  Slather.prepare_pods(self)
rescue LoadError
  puts 'Slather has been disabled (not installed).'
end

Under slather 1.8, iOS projects built on CircleCI with a coverage_service of coveralls fail to post coverage results to Coveralls. See this build, which seems to slather properly (Slathering... Slathered) but never posts to Coveralls.

CircleCI => Coveralls worked properly in previous releases of slather, as seen in this build from today which is pinned to slather 1.7.1.

Posting this issue mostly as a reminder to myself to look into this :)

We should look into supporting the LLVM’s code coverage mapping format.

http://llvm.org/docs/CoverageMappingFormat.html
http://llvm.org/docs/CommandGuide/llvm-profdata.html
http://llvm.org/docs/CommandGuide/llvm-cov.html

Xcode uses LLVM, one day it might encourage developers to use this coverage format too.

Xcode 7 compiles this data together into a binary plist with the extension .xccoverage, reading that should be much easier.

Thanks a lot for adding Cobertura support recently! 👍

It would be useful to me if I cam specify a place where cobertura report should be saved. I.e. build/reports/coverage.xml instead of cobertura.xml. Or can be even more useful if slather can return the data into output stream instead of collection it into one variable and then putting it into file. So it will allow to do something like slather coverage -x > build/reports/covearage.xml. Or, if needed, slather coverage -x | tee build/reports/covearage.xml so its output will be returned into console as well.

Hi there,

I've tried to use cobertura_xml coverage service but I've got the following error:
coverage_service=:'' is not a valid coverage service. Try 'terminal' or 'coveralls' (ArgumentError)

I get this same message even if install 1.8.2 specifically. That message was in 1.4.0 last time. So it seems that wrong code downloaded when it's installed via RubyGems.

Another symptom: gemspec of 1.8.2 says that it depends on xcodeproj 0.28.0 but on RubyGems.org it is xcodeproj 0.17. (which was the dependency in slather 1.4.0)

Could you look after it? Thanks.

Looks like slather setup project is working but now when I try to run slather coverage I'm being told

No coverage files found. Are you sure your project is setup for generating coverage files

ISO8601 at aeb5da75332954c9cd2f156edd8d8f83bbdef97e shows 100% coverage locally (via rake coverage), but it only shows 86% on Coveralls.

I'm running slather on CircleCI objective-c project. Slather runs without error and without any output other than:
Slathering...
Slathered.

However, nothing gets sent to Coveralls. I can run slather with coverage --html and that does produce a coverage report on CircleCI

I have set my github repo token in CircleCI Environment Variable: COVERALLS_REPO_TOKEN

.slather.yml:
ci_service: circleci
coverage_service: coveralls
xcodeproj: ObjectiveCBootstrap.xcodeproj
source_directory: ./

circle.yml:
machine:
xcode:
version: "7.0"
test:
override:
- xcodebuild test -project ObjectiveCBootstrap.xcodeproj -scheme ObjectiveCBootstrap -destination 'platform=iOS Simulator,name=iPhone 6,OS=9.0' ONLY_ACTIVE_ARCH=NO TEST_AFTER_BUILD=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=YES GCC_GENERATE_TEST_COVERAGE_FILES=YES
post:
- bundle exec slather

Give a description of RubyGems, Bundler, and RVM (or ruby version managers in general).

File this under question or feature request:

In their repo setup instructions, Coveralls warns against making your repo token public. There are ways to do this for projects running PR builds on a public repo—though they aren't exactly bullet-proof. It would be nice if slather supported passing the repo token using command-line args and/or environment variables. The fallback logic could look like:

• Env var?
• YAML?
• CL arg?
• Fail, no repo token provided

Thoughts?

Slathering...
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1439:in unlink': No such file or directory - AgreementViewController.m.gcov (Errno::ENOENT) from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1439:inblock in remove_file'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1444:in platform_support' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:1438:inremove_file'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:785:in remove_file' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:563:inblock in rm'
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:562:in each' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/fileutils.rb:562:inrm'
from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:50:in block in gcov_data' from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:50:ineach'
from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:50:in gcov_data' from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:57:incoverage_data'
from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:83:in num_lines_tested' from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/coverage_file.rb:91:inpercentage_lines_tested'
from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/project.rb:57:in each' from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/project.rb:57:inmax_by'
from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/project.rb:57:in block in dedupe' from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/project.rb:57:inmap'
from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/project.rb:57:in dedupe' from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/project.rb:51:incoverage_files'
from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/lib/slather/coverage_service/simple_output.rb:13:in post' from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/bin/slather:57:inpost'
from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/bin/slather:33:in execute' from /Library/Ruby/Gems/2.0.0/gems/clamp-0.6.5/lib/clamp/command.rb:67:inrun'
from /Library/Ruby/Gems/2.0.0/gems/clamp-0.6.5/lib/clamp/subcommand/execution.rb:11:in execute' from /Library/Ruby/Gems/2.0.0/gems/clamp-0.6.5/lib/clamp/command.rb:67:inrun'
from /Library/Ruby/Gems/2.0.0/gems/clamp-0.6.5/lib/clamp/command.rb:132:in run' from /Library/Ruby/Gems/2.0.0/gems/clamp-0.6.5/lib/clamp.rb:6:inClamp'
from /Library/Ruby/Gems/2.0.0/gems/slather-1.3.0/bin/slather:6:in <top (required)>' from /usr/local/bin/slather:23:inload'
from /usr/local/bin/slather:23:in `

Should slather have HTML export?

gcovr can produce an ugly static html report, would be great if we could generate a pretty modern html report with some javascript to support filtering, reorder, etc within the page. Only restriction would be it needs to be able to run as a file:/// url (no cross-origin)

Hello folks,

I am currently looking for coverage reports which can be integrated in a classical Jenkins Continuous Integration environment.

Cobertura is very popular there so I thought I'd write a coverage service to generate coverage reports in Cobertura XML format. Since xctool is able to generate JUnit reports a Cobertura XML coverage service for slather would be a good complement.

It is still missing branch coverage calculation and specs but if you like you can take a look at it here:

https://github.com/tarbrain/slather/tree/feature/cobertura_reporter

Cheers
Julian