Skip to main content

testing-strategy

Guidelines for writing effective tests in this project

来源信息

仓库
block/agent-skills
最近来源活动
2026年1月27日 20:31
检测到的 SKILL.md 语言
英语
星标
26
Forks
50

安装方式

默认使用会先检查来源的 Prompt;你也可以切换为直接命令,或下载本地副本。

检查来源文件

决定是否安装前,请先阅读 SKILL.md,以及 SkillsMP 当前展示的配套文件。

正在显示 SKILL.md

SKILL.md
来源说明 · 只读预览
name
testing-strategy
description
Guidelines for writing effective tests in this project
author
goose
version
1.0
tags
["testing","development","quality"]
# Testing Guidelines ## Unit Tests - Test one thing per test - Use descriptive test names: `test_user_creation_fails_with_invalid_email` - Mock external dependencies - Keep tests fast and isolated ## Integration Tests - Test API endpoints with realistic data - Verify database state changes - Clean up test data after each test - Use test fixtures for common scenarios ## Running Tests ```bash # Run all tests npm test # Run unit tests only npm test:unit # Run integration tests (requires database) npm test:integration # Run tests with coverage npm test:coverage ``` ## Test Structure ``` tests/ ├── unit/ # Fast, isolated unit tests ├── integration/ # Tests requiring external services ├── fixtures/ # Shared test data └── helpers/ # Test utilities ``` ## Best Practices 1. **Arrange-Act-Assert**: Structure tests clearly 2. **One assertion per test**: When possible, test one behavior 3. **Descriptive names**: Test names should describe the scenario 4. **No test interdependence**: Tests should run in any order 5. **Clean state**: Each test starts with a known state ## Coverage Goals - Aim for 80%+ line coverage - Focus on critical paths first - Don't sacrifice test quality for coverage numbers
在 GitHub 查看