simonsobs / simonsobs/sotodlib

Setup test coverage reporting

Open
#273 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Python
Stars
19
Forks
23
Avg merge
1d 5h
Merged PRs (30d)
14

Description

Following the discussion on today's call about testing requirements I was wondering if it'd be useful if we setup test coverage reporting for the sotodlib, for example, like what we do on ocs or so3g.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Review the linked coverage-reporting examples for ocs and so3g, then inspect sotodlib's existing test and CI setup. Done means the project has an agreed coverage-reporting configuration comparable to those examples, but the issue does not identify files, tests, or a specific reporting service.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ci-cd, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.