AI Skill Report Card
Testing PlannerVersi E2E QA
PlannerVersi E2E QA Testing
Quick Start15 / 15
Bash# Test a page with default settings teste a página Associativo # Test with specific scope and credentials teste a tela Curva de Vendas apenas frontend, usuário admin@empresa.com senha 123456 # Test specific functionality valide o CRUD da página Taxa de Administração, funcionalidades: adicionar, editar, deletar
Recommendation▾
Remove over-explanation of basic concepts like 'Don't trust success messages alone' - Claude knows to validate persistence
Workflow14 / 15
Input Parsing
Extract these parameters from user request:
- Page (required): "Associativo", "Curva de Vendas", etc.
- Scope: FRONTEND | BACKEND | AMBOS (default: AMBOS)
- Credentials: email/password (default: teste@vp6.com.br/teste2026)
- Organization: for multi-tenant portals
- Functions: which operations to test (default: load, CRUD, version/module switching)
Test Configuration Display
╔══════════════════════════════════════════════╗
║ Test Configuration ║
╠══════════════════════════════════════════════╣
║ Page...........: <page-name> ║
║ Scope..........: <FRONTEND|BACKEND|AMBOS> ║
║ Credentials....: <email> ║
║ Organization...: <org-name or —> ║
║ Functions......: <function-list> ║
║ Notes..........: <additional-notes or —> ║
╚══════════════════════════════════════════════╝
Execution Order
- Authentication
- Route mapping
- Component mapping
- Endpoint extraction
- Page navigation (frontend scopes)
- Enterprise/version/module selection
- Initial load validation
- Network + Redux + DOM validation
- Functional testing (CRUD)
- Fresh refetch persistence validation
- Version/module switching regression test
- Final report generation
- Bug fix instructions (if issues found)
Recommendation▾
Condense the verbose pitfalls section - many points are redundant variations of 'validate persistence'
Examples18 / 20
Example 1: Frontend-only test
Input: teste a página Associativo apenas frontend
Output: UI navigation, form validation, Redux state checks, visual regression testing
Example 2: Backend API validation
Input: valide o backend da Taxa de Administração
Output: Direct HTTP API testing, CRUD operations, status codes, response validation
Example 3: Full E2E test
Input: execute teste completo da Curva de Vendas
Output: Complete frontend + backend flow with persistence validation
Recommendation▾
Simplify the workflow checklist - 12 steps is excessive for a clear process
Best Practices
Test Environment Defaults
- Frontend: http://localhost:3000
- Backend: http://localhost:8000
- Stack: UmiJS + React + DVA + Ant Design
- Redux access:
window.g_app._store.getState()
Critical Validation Rules
- Never consider test passed without fresh refetch validation
- Always cross-validate: Network + Redux + DOM
- Confirm persistence after save operations
- Test version/module switching for data staleness
- Use React input helpers for masked fields
Masked Input Helper
JavaScriptwindow.__setMaskedCurrency = (selector, value) => { const el = document.querySelector(selector); const setter = Object.getOwnPropertyDescriptor(HTMLInputElement.prototype, 'value').set; setter.call(el, Math.round(Number(value) * 100).toString()); el.dispatchEvent(new Event('input', { bubbles: true })); el.dispatchEvent(new Event('change', { bubbles: true })); };
Performance Guidelines
- Avoid excessive screenshots (max 8 per test)
- Use DOM polling instead of fixed waits
- Capture table data programmatically
- Minimize browser actions
Common Pitfalls
False Positives
- Don't trust success messages alone - validate actual persistence
- Don't trust visual updates only - confirm backend persistence
- Don't trust Redux updates only - verify database persistence
- Don't skip fresh refetch - memory vs. database can differ
Test Data Management
- Create test data when possible - don't rely on existing data
- Clean up after tests - delete created records
- Use descriptive test data - easy to identify and remove
- Avoid production data modification when alternatives exist
Bug Classification
- High: Data loss, save failures, broken CRUD, authentication blocks
- Medium: Stale Redux, visual inconsistencies, incomplete forms
- Low: Layout issues, minor UX problems, cosmetic concerns
Report Structure
Always generate structured reports with:
- Test configuration and scope
- Endpoint mapping table
- Step-by-step checklist with ✓/✗/— status
- Bug details with severity, evidence, and suggested fixes
- Clear pass/fail determination with technical reasoning