test-estimation
Estimate testing effort, duration, and resourcing for a Katalon True Platform/TestOps cycle. Use when the question is how long testing will take, how many testers it needs, whether the scope fits the sprint window, or what a scope change costs in person-hours. Sizes design, manual execution, automated execution and triage, and rework separately, counts the countable part from platform data (case counts, automation split, historical pass and stability rates, configuration matrix), calibrates the rest against a rate the team supplies, and returns a three-point range with a confidence label instead of a single number. Splits resourcing across the manual and automated lanes and names the assumptions that would move the number most. For what to test and in what order, use test-plan; for a verdict on a cycle that has already run, use release-analyze. Written for the test lead sizing a cycle before it starts and the test manager who has to fund it.
Pinned to revision 36b8bbd52863, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/test-estimation/SKILL.md
- skills/test-estimation/references/estimation-model.md
- skills/test-estimation/references/mcp-evidence-map.md
Every link opens the file at its source, pinned to the revision this page describes.