Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Different coverage percentage from XCode report

Open
#557 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby, swift
Domain
devtools, testing

Research direction

Start by comparing the coverage data Slather reads with the report Xcode generates for the Swift classes described in the issue. The issue gives no file, test, or reproduction details, so first trace the coverage report entry points and look for existing tests covering Swift class coverage. Done means Slather reports percentages consistent with Xcode for the affected classes; the issue has had no comment for 647 days, so confirm the problem is still relevant before investing time.

Written by the indexing model from the issue text.

Description

Hi Team,
The report generated by slather provides coverage percentages that are far different from those provided by XCode. For many swift classes that have 100% coverage with XCode, slather reports zero coverage.
Any suggestions to solve this problem?
Thanks!

Dominant language
Ruby
Stars
1.6k
Forks
239
Avg merge
10h 19m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SlatherOrg/slather

All issues in SlatherOrg/slather

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.