PyO3/pyo3

Improving test coverage

Open

#2,453 建立於 2022年6月14日

在 GitHub 查看
 (8 留言) (2 反應) (0 負責人)Rust (10,152 star) (668 fork)batch import
Good First Issueeasyhelp-wantedneeds-implementer

描述

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.

貢獻者指南

技術棧
rust
領域
testing
議題類型
test
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Basic Rust knowledgeUnderstanding of PyO3's testing frameworkFamiliarity with code coverage tools
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
Focus on the files marked as untested: src/pycell.rs and src/once cell.rs. Check current coverage gaps via the provided Codecov link and write meaningful tests covering error paths and corner cases, not just happy paths. Review existing merged PRs like #2462 for examples of acceptable test contributions.