Skip to main content Skills Marketplace Descubra e explore skills de IA criadas pela comunidade.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Mostrar detalhes do prompt Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/proffesor-for-testing/sentinel-api-testing --skill test-automation-strategyO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Baixar Zip Baixando... Ocupações relacionadas SOC
Baseado na classificação ocupacional SOC
name test-automation-strategy description Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency. category testing-methodologies priority high tokenEstimate 1000 agents ["qe-test-generator","qe-test-executor","qe-coverage-analyzer","qe-flaky-test-hunter","qe-regression-risk-analyzer"] implementation_status optimized optimization_version 1 last_optimized 2025-12-02T00:00:00.000Z dependencies [] quick_reference_card true tags ["automation","test-pyramid","page-object","first-principles","ci-cd","flaky-tests"]
Test Automation Strategy
<default_to_action>
When designing or improving test automation:
FOLLOW test pyramid: 70% unit, 20% integration, 10% E2E
APPLY F.I.R.S.T. principles: Fast, Isolated, Repeatable, Self-validating, Timely
USE patterns: Page Object Model, Builder pattern, Factory pattern
INTEGRATE in CI/CD: Every commit runs tests, fail fast, clear feedback
MANAGE flaky tests: Quarantine, fix, or delete - never ignore
Quick Anti-Pattern Detection:
Ice cream cone (many E2E, few unit) → Invert to pyramid
Slow tests (> 10 min suite) → Parallelize, mock external deps
Flaky tests → Fix timing, isolate data, or quarantine
Test duplication → Share fixtures, use page objects
Brittle selectors → Use data-testid, semantic locators
Critical Success Factors:
Fast feedback is the goal (< 10 min full suite)
Automation supports testing, doesn't replace judgment
Invest in test infrastructure like production code
</default_to_action>
Quick Reference Card
When to Use
Building new automation framework
Improving existing test efficiency
Reducing flaky test burden
Optimizing CI/CD pipeline speed
Test Pyramid
Layer % Speed Isolation Examples Unit 70% < 1ms Complete Pure functions, logic Integration 20% < 1s Partial API, database E2E 10% < 30s None User journeys
F.I.R.S.T. Principles
Principle Meaning How F astQuick execution Mock external deps I solatedNo shared state Fresh fixtures per test R epeatableSame result every time No random data
S elf-validatingClear pass/fail Assert, don't print
T imelyWritten with code TDD, not after
Anti-Patterns Problem Symptom Fix Ice cream cone 80% E2E, 10% unit Invert pyramid Slow suite 30+ min CI Parallelize, prune Flaky tests Random failures Quarantine, fix timing Coupled tests Order-dependent Isolate data Brittle selectors Break on CSS change Use data-testid
Page Object Model
class LoginPage {
constructor (page ) {
this .page = page;
this .emailInput = '[data-testid="email"]' ;
this .passwordInput = '[data-testid="password"]' ;
this .submitButton = '[data-testid="submit"]' ;
this .errorMessage = '[data-testid="error"]' ;
}
async login (email, password ) {
await this .page .fill (this .emailInput , email);
await this .page .fill (this .passwordInput , password);
await this .page .click (this .submitButton );
}
async getError (return this .page .textContent (this .errorMessage );
}
}
test ('shows error for invalid credentials' , async ({ page }) => {
const loginPage = new LoginPage (page);
await loginPage.login ('bad@email.com' , 'wrong' );
expect (await loginPage.getError ()).toBe ('Invalid credentials' );
});
CI/CD Integration name: Test Pipeline
on: [push , pull_request ]
jobs:
unit-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci
- run: npm run test:unit -- --coverage
timeout-minutes: 5
- uses: codecov/codecov-action@v3
integration-tests:
needs: unit-tests
runs-on: ubuntu-latest
services:
postgres:
image: postgres:15
steps:
- run: npm run test:integration
timeout-minutes: 10
e2e-tests:
needs: integration-tests
runs-on: ubuntu-latest
steps:
- run: npx playwright test
timeout-minutes: 15
Flaky Test Management
describe.skip ('Quarantined - INC-123' , () => {
test ('flaky test awaiting fix' , () => { });
});
await Task ("Fix Flaky Tests" , {
tests : quarantinedTests,
analysis : ['timing-issues' , 'data-isolation' , 'race-conditions' ],
strategies : ['add-waits' , 'isolate-fixtures' , 'mock-externals' ]
}, "qe-flaky-test-hunter" );
Agent-Assisted Automation
await Task ("Generate Test Suite" , {
sourceCode : 'src/' ,
pyramid : { unit : 70 , integration : 20 , e2e : 10 },
patterns : ['page-object' , 'builder' , 'factory' ],
framework : 'jest'
}, "qe-test-generator" );
await Task ("Optimize Suite" , {
algorithm : 'johnson-lindenstrauss' ,
targetReduction : 0.3 ,
maintainCoverage : 0.95
}, "qe-regression-risk-analyzer" );
await Task ("Flaky Analysis" , {
testHistory : 'last-30-days' ,
detectPatterns : ['timing' , 'data' , 'environment' ],
recommend : 'stabilization-strategy'
}, "qe-flaky-test-hunter" );
Agent Coordination Hints
Memory Namespace aqe/automation/
├── test-pyramid/* - Coverage by layer
├── page-objects/* - Shared page objects
├── flaky-registry/* - Quarantined tests
└── execution-metrics/* - Suite performance data
Fleet Coordination const automationFleet = await FleetManager .coordinate ({
strategy : 'test-automation' ,
agents : [
'qe-test-generator' ,
'qe-test-executor' ,
'qe-coverage-analyzer' ,
'qe-flaky-test-hunter' ,
'qe-regression-risk-analyzer'
],
topology : 'hierarchical'
});
Related Skills
Remember Pyramid: 70% unit, 20% integration, 10% E2E. F.I.R.S.T. principles for every test. Page Object Model for E2E. Parallelize for speed. Quarantine flaky tests - never ignore them. Treat test code like production code.
With Agents: Agents generate pyramid-compliant tests, detect flaky patterns, optimize execution time, and maintain test infrastructure. Use agents to scale automation quality.
