Find a usecase for/improve the fake github API testing

未关闭
#567 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
python
领域
testing

调研方向

Start by reviewing the fake GitHub API code from #563 and identify a concrete code path where response headers or query strings would enable useful test coverage. Agree on that use case before expanding the fake API; done means the use case is documented and the added capability supports tests for it.

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

描述

devops needs-plan testing

In the code from #563
Not modelled yet: response headers (pagination, rate limits, redirects) and query strings

Filing an issue so we remember to expand the capabilities of the github API testing later.

That said: like some of my comments on that PR - i want to make sure we have a usecase for these expanded features first - i.e. a concrete part of the code we can add test coverage to with this feature that wouldnt be possible without (or would have a less clean solution if done another way).

Marking as needs-plan to ensure we identify the usecase before we implement so we dont just add code that never gets used

主要语言
Python
星标
17
派生
30
平均合并
6 小时 16 分钟
30 天内合并 PR
9

环境准备

从这里开始

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

chaoss/CollectOSS 的其他 Issue

查看 chaoss/CollectOSS 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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