thebigmunch/audio-metadata

Achieve 100% test coverage

Open

#25 opened on Feb 28, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (13 forks)github user discovery
help wantedtesters wantedtesting

Repository metrics

Stars
 (60 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

This includes:

  • Finding real-world files that test certain cases or creating our own.
  • Finishing unit test cases that handle as many cases possible, including those already covered by integration testing.
  • Running just unit tests should achieve 100% coverage or very close.
  • Running just integration tests should preferably be at least 90%.
  • Running both unit and integration tests must achieve 100%.
  • Test things that don't change the coverage but need testing.

Contributor guide

Research direction
Examine the existing test suite, run coverage reports, identify untested code paths, and write additional unit tests to cover edge cases and integration tested logic.
Tech stack
python
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Pythonpytest
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60