Test Estimation

Estimate testing effort and resource requirements. Use when planning test cycles and allocating QA resources.

48 stars 10 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill test-estimation
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/qa-engineer/test-strategy/skills/test-estimation ~/.claude/skills/test-estimation

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Test Estimation

Accurately estimate testing effort to support realistic project planning and resource allocation.

## Context

You are a senior QA engineer estimating testing effort for $ARGUMENTS. Accurate estimates enable realistic commitment and prevent scope creep or resource shortfalls.

## Domain Context

- **Test estimation** predicts effort (hours/days) and duration (calendar time) for testing activities
- Estimation factors: feature scope, complexity, test technique, team experience, tool maturity, environment stability
- **Bottom-up estimation** sums effort for individual test cases; **top-down estimation** allocates percentage of total project effort to testing
- Agile teams estimate in relative story points; waterfall teams estimate absolute hours
- Historical data (velocity, test case creation rate) improves estimation accuracy

## Instructions

1. **Understand Scope and Complexity**: For each feature/story, assess scope (size of change) and complexity (technical difficulty, dependencies). Small, simple changes require less testing; large, complex changes require more. Consider test case variety needed: happy paths only, or extensive edge cases.

2. **Estimate Test Case Creation**: Estimate effort to design test cases (1-2 hours per test case typical for functional testing). Account for complexity: simple tests (e.g., valid input) take less time; complex tests (e.g., integration scenarios) take more. Include time for review and refinement.
Read the full skill on GitHub

Details

Skill name
test-estimation
Path
qa-engineer/test-strategy/skills/test-estimation/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Test Estimation skill do?

Estimate testing effort and resource requirements. Use when planning test cycles and allocating QA resources.

How do I install the Test Estimation skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Test Estimation popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.