Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

docs: document how to run the test suite locally

未关闭 适合新手
#430 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

@yuefdev 已经在做这个了。

开始于 2026年10月3日。

  • #435 来自 @yuefdev —— 未关闭

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
活跃
技术栈
python

调研方向

先从贡献者文档或开发文档开始,然后检查仓库的 pytest 配置和 CI 工作流,以确认既定的命令和依赖项设置。记录依赖项安装、完整的 pytest 运行和针对性的 pytest 运行、跳过测试的原因,以及 CI 测试配置所在的位置;当新贡献者能够在本地复现相关检查时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

Problem

When working on a test contribution, I had to inspect the repository's test configuration and CI workflow to determine how to run the same test suite locally.

The project has an established pytest-based test suite, but as a new contributor, I initially had to investigate the repository configuration to understand the expected local testing workflow.

Proposed documentation

Add a short section to the contributor/development documentation explaining:

  • how to install the test dependencies
  • how to run the complete test suite
  • how to run a specific test file
  • how to run a focused test using pytest's -k option
  • why some tests may be skipped
  • where contributors can find the CI test configuration

Who this is for

This is intended for new contributors making their first test-related change who need to verify their changes locally before opening a pull request.

Why I am proposing this

This is based on a real point where I was confused during my test contribution. I had to inspect the project's test configuration and CI workflow to understand how local pytest execution related to the automated checks on a pull request.

主要语言
Python
星标
760
派生
166
平均合并
4 天 3 小时
30 天内合并 PR
7

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

python-humanize/humanize 的其他 Issue

查看 python-humanize/humanize 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。