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

Add a small reusable valid assessment factory

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

在当前 main 上阅读 tests/conftest.py 和 pyproject.toml,然后检查 scripts/check.sh 和 .github/workflows/checks.yml 以了解测试和 lint 的要求。添加 tests/roadmap/tooling/test_assessment_factory.py,覆盖完整且有效的合成响应、显式覆盖、响应验证,以及不依赖 provider 内部实现。使用聚焦的 pytest 命令、pylint 和 bash scripts/check.sh 进行验证。

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

描述

area:testing contributor-roadmap difficulty:intermediate help wanted status:ready

TST-02 · Test infrastructure

Difficulty: intermediate · Status: ready

This is a focused contribution against current main. No unmerged feature PR is required.

Why this is useful

Tests duplicate response dictionaries with inconsistent values

Start here

Source audit: 9d8ac3e01df1. Read these files on current main too, because paths may change after the audit:

Scope and intended output

Add the focused test file tests/roadmap/tooling/test_assessment_factory.py. Change runtime code only if the acceptance criteria explicitly request a behavior fix; otherwise report newly discovered behavior separately.

Acceptance criteria
  • Return complete valid synthetic responses with explicit overrides
  • Avoid a MagicMock that bypasses response validation
  • Keep it independent of provider internals
Verification
uv run pytest tests/roadmap/tooling/test_assessment_factory.py -q
uv run pylint app tests

Create the named focused test file before running its command. Tests must be deterministic, mock external services, and avoid paid calls. Run bash scripts/check.sh before submitting a Python change.

Dependencies

None. Keep the PR based on current upstream main.

Out of scope
  • Unrelated refactors, broad formatting, endpoint renames, or extra dependencies without agreement.
  • Live cloud provisioning, paid model calls, real private messages, or credentials in fixtures/logs.
  • Implementing neighboring roadmap issues in the same PR.
Getting help and submitting

Comment with your intended approach and ask when expected behavior is unclear. Check for an existing PR before starting; there is no deadline for a volunteer contribution. A useful reproduction or partial finding is welcome.

Use the issue's criteria as the review checklist. Include the commands actually run and any limitations. Link the issue; use Fixes only when its entire agreed scope is complete. If CONTRIBUTING.md is not yet on main, the contributor-roadmap PR provides the onboarding guide.

主要语言
Python
星标
3
派生
10
平均合并
8 小时 11 分钟
30 天内合并 PR
18

环境准备

我们还没有检查这个项目的环境配置文件。先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

ashrafee-dev/scamshield-api 的其他 Issue

查看 ashrafee-dev/scamshield-api 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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