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

☂️ Replace stub `pending` specs with real tests

未关闭
#5,563 16 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 18 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
68/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
ruby
领域
testing-qa

调研方向

运行 grep -rl 'pending "add some tests for' spec/ 并选择一个匹配的 spec 文件。阅读被测试的类或模块以及附近的 specs,以确定一个要验证的行为,然后直接运行该文件。当占位符被移除、至少有一个真正的 it 或 describe 块运行,并且不再有 pending、skipped 或 xit 示例时,即表示完成。

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

描述

no-issue-activity

What type(s) of user does this feature affect?
Steve Ballmer DEVELOPERS DEVELOPERS DEVELOPERS

Status (updated 2026-05-02): the original framing of this umbrella is stale. .allow_skipping_tests is now empty — that gate is satisfied. But it was emptied in #6517 (Oct 2025) by stubbing 52 spec files with pending "add some tests for X" placeholders rather than by writing real tests. The umbrella's actual goal — real tests for those files — is not done.

41 stub specs still remain. Find them with:

grep -rl 'pending "add some tests for' spec/

Definition of done for one stub:

  • Delete the pending "add some tests for X" line.
  • Add at least one real it / describe block that exercises a behavior of the class/module under test.
  • Make sure the spec actually runs — no pending, skip, or xit left in the file.
  • One stub file per PR is fine; bundle several if they're tiny or share a theme.

Reference: the placeholder pattern was introduced in #6517. Anything matching the grep above is fair game.


QA Login Details:
Link to QA site

Login Emails:

password for all users: 12345678

Questions? Join Slack!

We highly recommend that you join us in slack https://rubyforgood.herokuapp.com/ #casa channel to ask questions quickly and hear about office hours (currently Wednesday 6-8pm Pacific), stakeholder news, and upcoming new issues.

主要语言
Ruby
星标
382
派生
546
平均合并
12 天 12 小时
30 天内合并 PR
17

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

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

rubyforgood/casa 的其他 Issue

查看 rubyforgood/casa 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

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