From vfm-agent-company
Comprehensive QA and testing methodology from Google (Chrome/Android scale, 2B+ users). Use when writing unit tests (Jest, Vitest), integration tests, E2E tests (Playwright, Cypress), performance tests (k6), security tests (OWASP), setting up test coverage, creating test plans, or coordinating UAT sign-off. Triggers on testing, test cases, test coverage, QA, E2E tests, unit tests, integration tests, or quality assurance.
npx claudepluginhub duylinhdang1998/claude-template-agent --plugin vfm-agent-companyThis skill uses the workspace's default tool permissions.
**Purpose**: Complete testing methodology from Google's testing infrastructure team
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Purpose: Complete testing methodology from Google's testing infrastructure team
Agent: Google QA Engineer Use When: Phase 4 (Testing) - need comprehensive quality assurance
This skill module provides comprehensive testing procedures used at Google to ensure quality at massive scale (2B+ users for Chrome, Android OS).
Core Philosophy:
File: references/test-planning.md
Covers:
When to Use: Beginning of Phase 4 (Testing)
File: references/test-automation.md
Covers:
When to Use: Week 2-3 of Testing phase
Example Topics:
File: references/performance-testing.md
Covers:
When to Use: Before deployment to production
Example Scenarios:
File: references/security-testing.md
Covers:
When to Use: Before UAT and production deployment
Tools Covered:
File: references/uat-coordination.md
Covers:
When to Use: Week 5 of Testing phase
Templates Included:
# Week 1: Test Planning
Read: references/test-planning.md
Create: Test plan for project
Setup: Test frameworks
# Week 2-3: Test Implementation
Read: references/test-automation.md
Write: Unit, integration, E2E tests
# Week 4: Performance & Security
Read: references/performance-testing.md
Read: references/security-testing.md
Execute: Load tests, security scans
# Week 5: UAT
Read: references/uat-coordination.md
Coordinate: Client testing
Verify: All acceptance criteria met
PM: Review test plans, track testing progress Developers: Write unit tests (refer to test-automation.md) BA: Coordinate UAT (refer to uat-coordination.md) DevOps: Integrate tests in CI/CD pipeline
/\
/ \ E2E Tests (10%)
/____\ - Critical user journeys
/ \ - Slow but high confidence
/________\
/ \ Integration Tests (30%)
/____________\ - API tests, DB tests
/ \ - Medium speed
\______________/
\ / Unit Tests (60%)
\____________/ - Fast, isolated
\ / - High coverage
\________/
Why this ratio?
Before deployment approval:
## Code Quality ✅
- [ ] Unit test coverage ≥ 80%
- [ ] All unit tests passing
- [ ] No code smells (SonarQube)
## Integration Testing ✅
- [ ] All API endpoints tested
- [ ] Database tests passing
- [ ] Third-party integration tests passing
## E2E Testing ✅
- [ ] Top 10 user flows tested
- [ ] No flaky tests
- [ ] Cross-browser testing done
## Performance ✅
- [ ] API p95 latency < 500ms
- [ ] Page load time < 2s
- [ ] Core Web Vitals: Good
- [ ] Load test passed (target concurrency)
## Security ✅
- [ ] OWASP Top 10 tested
- [ ] No critical vulnerabilities
- [ ] Dependency scan passed
- [ ] Security headers configured
## UAT ✅
- [ ] Client testing completed
- [ ] All critical scenarios passed
- [ ] Feedback incorporated
- [ ] UAT sign-off received
**QA Sign-Off**: _______________
**Date**: _______________
Coverage: 80%+ for production code Speed: Full test suite < 5 minutes Flakiness: 0% - all tests must be reliable Documentation: Every test has clear description
Test Naming Convention:
describe('TodoService', () => {
describe('createTodo', () => {
it('should create todo with valid data', () => {
// Test implementation
});
it('should throw error when title is empty', () => {
// Test implementation
});
});
});
**Testing Progress**: Day 3 of Week 2
- Unit tests: 87% coverage (✅ target: 80%)
- Integration tests: 12/15 passing (⚠️ 3 fixing)
- E2E tests: Setup complete, writing scenarios
**Blockers**:
- Need staging environment for integration tests (ETA: tomorrow)
**Next 24h**:
- Complete integration test fixes
- Begin E2E test writing
## Week 2 Quality Report
**Test Execution**:
- Total tests: 450
- Passing: 445 (98.9%)
- Failing: 5 (under investigation)
**Coverage**: 87% (target: 80%) ✅
**Bugs Found**: 8
- P0: 0
- P1: 2 (both fixed)
- P2: 6 (4 fixed, 2 in progress)
**On Track**: Yes, UAT scheduled for Week 5
🛡️ Quality is not negotiable
⚡ Fast feedback wins
🔄 Zero tolerance for flaky tests
For detailed procedures, read the reference guides in references/ folder
Created: 2026-02-04 Maintained By: Google QA Engineer Review Cycle: After each major project