[Complete] Record session/discovery acceptance
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 45/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- documentation, testing
调研方向
Start in docs/operations/acceptance.md, which #125 must create or extend first, and use docs/guides/testing.md as the starting example for the layout. Add a section covering the create, edit, cancel, join and leave study-meeting journeys, recording action, expected result, observed result, pass/fail and a test or screenshot link for each. The work is done when every journey has a row with evidence, and each failure has a linked follow-up issue. The live checks need the approved test environment, so confirm access before you begin.
由索引模型根据 Issue 内容生成。
描述
What to build
Record the create, edit, cancel, join and leave journeys for study meetings. Include discovery and seat-count observations so the handoff shows what was actually checked.
Files
docs/operations/acceptance.md(extend the prerequisite’s file)- Starting example: docs/guides/testing.md
Steps
- Add a section for the journey described above in the listed document. Follow the completed feature issues’ examples and their supplied test inputs.
- Record the action, expected result, observed result, pass/fail and a link to the test or screenshot. Use the approved test environment for live checks.
- Link one focused follow-up issue for each failure. Keep the evidence even when a later check passes.
Example
Supplied create/edit/cancel/join/leave journey with fake clock and test examples; record expected views/action results before freeze.
Check it works
Record the expected and observed result in the named document, with source links and any follow-up issues.
Before starting
- #125 — Record onboarding/profile acceptance
References
Assign yourself before starting, or comment to claim the issue. Project setup.
- 主要语言
- PLpgSQL
- 星标
- 0
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
DevDogsUGA/DogPack 的其他 Issue
-
polish
难度 2/5 1-3 小时 新手友好度 72/100
DevDogsUGA/DogPack#131 ·
-
polish
难度 2/5 1-3 小时 新手友好度 65/100
DevDogsUGA/DogPack#130 ·
-
moderation
难度 2/5 1-3 小时 新手友好度 75/100
DevDogsUGA/DogPack#119 ·
-
moderation
难度 2/5 1-3 小时 新手友好度 85/100
DevDogsUGA/DogPack#113 ·
-
discover
难度 2/5 1-3 小时 新手友好度 74/100
DevDogsUGA/DogPack#106 ·
查看 DevDogsUGA/DogPack 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
area:docs documentation P3
难度 1/5 1 小时以内 新手友好度 88/100
Raaif-Yousuf/Wingman#837 ·
维护者通常 1 天内回复
-
documentation good first issue hacktoberfest
难度 2/5 1-3 小时 新手友好度 70/100
wassim-azi/agy-powerline#47 ·
维护者通常 1 天内回复
-
area/localization language/es triage/accepted
难度 2/5 1-3 小时 新手友好度 70/100
kubernetes/website#58112 ·
维护者通常 2 天内回复
-
agent:working documentation enhancement go:build lane:needs-decision
难度 2/5 1-3 小时 新手友好度 72/100
Sanne/incus-spawn#1435 · 3 条评论 ·
维护者通常 1 天内回复