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

slather dont generate all the coverage

Open
#535 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
testing-qa

Research direction

The issue only says that Slather does not generate all coverage and points to screenshots; it names no files or failing tests. Start by inspecting the screenshots and checking the project’s coverage generation entry points. Done means identifying the missing coverage and documenting a reproducible expected result, but the issue provides too little detail to define that result.

Written by the indexing model from the issue text.

Description

I have this files

Screenshot 2023-03-14 at 2 24 35 PM Screenshot 2023-03-14 at 2 23 31 PM
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.