Add a principle for choosing the test layer
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 57/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- playwright, react, typescript
- 领域
- testing-qa
调研方向
Read the Verification group in the go-mode principle index, the tdd skill, and the Feature playbook to find how principles are organized and referenced. Check the current Playwright Test Agents command against Playwright documentation. Done when the new principle is indexed, linked from both skills, documented in go-help and the README, and passes the named authoring validation and build.
由索引模型根据 Issue 内容生成。
描述
Parent
#15
What to build
An agent that has to test a change knows which layer to test it at. A new principle says to test at the lowest layer where the bug can actually occur: unit tests for pure logic, component tests for component behavior, and one real end-to-end test for anything that crosses the browser-server line. The principle names auth, sessions, routing, and redirects as browser-server concerns, so a login flow gets one end-to-end test of the main path instead of only mocked form tests. It also says when each layer runs: sub-second checks continuously, targeted checks on every meaningful edit, slow suites before declaring done, and CI-only suites left to CI.
To generate a new end-to-end suite, the principle points to Playwright Test Agents instead of having the agent write the suite by hand.
Acceptance criteria
- The new principle skill exists and is listed in the Verification group of the go-mode principle index.
- The
tddskill and the Feature playbook point to it. - Asked how to test a React login flow, an agent following gstack proposes one real end-to-end test of the main path.
- The Playwright Test Agents command matches current Playwright docs.
- The principle has a go-help row and a README line.
- The skill passes the authoring-a-skill validation and the build.
The principle's name is left to the build.
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 0
- 平均合并
- 3 小时 33 分钟
- 30 天内合并 PR
- 13
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
gregogun/gstack 的其他 Issue
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
ready-for-agent
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
ready-for-human
难度 4/5 3-5 天 新手友好度 43/100
维护者通常 1 天内回复
-
ready-for-agent
难度 3/5 1-2 天 新手友好度 56/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
lyswhut/lx-music-desktop#3026 ·
-
area: ci type: test
难度 2/5 1-3 小时 新手友好度 65/100
schlessera/brain-kit#2769 ·
维护者通常 1 天内回复
-
Read a vector index's quantization back on Neo4j 2026.10, which reports vector.quantization.type未关闭
难度 2/5 1-3 小时 新手友好度 78/100
liberation-data/drivine#231 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
alveusgg/alveusgg#2502 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复