PyO3/pyo3

Improving test coverage

Open

#2,453 opened on Jun 14, 2022

View on GitHub
 (8 comments) (2 reactions) (0 assignees)Rust (668 forks)batch import
Good First Issueeasyhelp-wantedneeds-implementer

Repository metrics

Stars
 (10,152 stars)
PR merge metrics
 (Avg merge 9d 18h) (51 merged PRs in 30d)

Description

This issue gathers some areas where we need to improve our test coverage.

You can view pyo3's test coverage online here or locally by following the steps here (do this when writing tests, so you can check them).

In particular (but not limited to) these areas need improvement:

Please keep in mind to write meaningful tests - do not just write tests that take the happy path, but also tests that take error paths or corner cases.

Contributor guide

Research direction
Look at the coverage reports for the specified files (pycell.rs and once cell.rs) and write meaningful unit tests covering edge cases and error paths. Refer to existing tests in the same module for patterns.
Tech stack
rust
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75