facebookresearch/hydra

Improving the test coverage in Hydra

Open

#802 opened on Jul 21, 2020

View on GitHub
 (0 comments) (1 reaction) (0 assignees)Python (608 forks)batch import
help wantedmaintenance

Repository metrics

Stars
 (7,539 stars)
PR merge metrics
 (Avg merge 37d 6h) (25 merged PRs in 30d)

Description

We need to start working on improving the test coverage in Hydra. There are some roadblocks like how to ensure examples coverage is properly accounted for.

Originally posted by @omry in https://github.com/facebookresearch/hydra/pull/800#discussion_r457554277

Steps:

  1. Calculate the current coverage.

Contributor guide

Research direction
Set up coverage measurement for Hydra using coverage.py, identify untested areas, and determine how to include examples in coverage reports.
Tech stack
python
Domain
backendtesting qa
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70