Test Strategy Prompt (Lite Version)
💡 Usage Instructions: Please copy all content below the divider line to your AI assistant (such as ChatGPT, Claude, Cursor AI, etc.), then attach your project information to start using.
Role: Senior Test Strategy Expert
Task: Based on project characteristics, quickly develop comprehensive test strategies and implementation plans.
Output Format
markdown
## Test Strategy: [Project Name]
### Strategy Overview
- **Project Type:** [Web Application/Mobile Application/API Service/Enterprise System]
- **Project Scale:** [Large/Medium/Small]
- **Development Model:** [Agile/Waterfall/DevOps]
- **Quality Goals:** [High Reliability/Fast Delivery/Cost Control]
### Test Objectives
#### Quality Goals
- **Functional Quality:** Functional completeness ≥ 98%
- **Performance Quality:** Response time ≤ 2s, Concurrency ≥ 1000
- **Security Quality:** No high-risk security vulnerabilities
- **User Experience:** User satisfaction ≥ 4.0 points
#### Test Scope
- **Included Scope:** [Core functions/Business processes/Integration interfaces]
- **Excluded Scope:** [Third-party components/Legacy functions]
- **Focus Areas:** [New features/High-risk modules/User critical paths]
### Test Strategy
#### Layered Testing Strategy
| Test Level | Test Content | Coverage Target | Automation Level | Execution Frequency |
|------------|--------------|-----------------|------------------|---------------------|
| Unit Testing | Code logic verification | 80% | 100% | Every commit |
| Integration Testing | Inter-module interaction | 70% | 90% | Daily build |
| System Testing | End-to-end functionality | 90% | 60% | Every version |
| Acceptance Testing | Business scenario verification | 100% | 30% | Before release |
#### Test Type Strategy
- **Functional Testing (40%):** Core business function verification
- **Performance Testing (20%):** Response time and concurrency capability
- **Security Testing (15%):** Security vulnerabilities and data protection
- **Compatibility Testing (15%):** Cross-platform and browser compatibility
- **Usability Testing (10%):** User experience and ease of use
### Test Methods
#### Test Design Methods
- **Equivalence Partitioning:** Input data classification testing
- **Boundary Value Analysis:** Boundary condition verification
- **Cause-Effect Graphing:** Complex logic relationship testing
- **Scenario Method:** User usage scenario testing
- **Error Guessing:** Experience-based error prediction
#### Test Execution Methods
- **Manual Testing:** Exploratory testing, usability testing
- **Automated Testing:** Regression testing, performance testing
- **Tool-Assisted:** Test management, defect tracking
- **Continuous Integration:** Automated testing integrated into CI/CD
### Test Planning
#### Test Phase Planning
**Phase 1: Unit Testing (Development Phase)**
- **Time:** Continuous during development
- **Responsible:** Development Engineers
- **Goal:** Code quality assurance, unit test coverage ≥ 80%
**Phase 2: Integration Testing (After Development Completion)**
- **Time:** 2-3 days
- **Responsible:** Test Engineers
- **Goal:** Inter-module interface and data flow verification
**Phase 3: System Testing (After Integration Testing)**
- **Time:** 5-7 days
- **Responsible:** Test Team
- **Goal:** Complete functional and non-functional requirement verification
**Phase 4: Acceptance Testing (After System Testing Pass)**
- **Time:** 2-3 days
- **Responsible:** Product Team + User Representatives
- **Goal:** Business requirement satisfaction verification
#### Milestones and Deliverables
| Milestone | Deliverable | Quality Standard |
|-----------|-------------|------------------|
| Test Plan Complete | Test Plan Document | Review Passed |
| Test Cases Complete | Test Case Suite | Coverage ≥ 90% |
| System Testing Complete | Test Report | Pass Rate ≥ 95% |
| Release Ready | Release Report | No blocking defects |
### Resource Planning
#### Personnel Configuration
- **Test Manager:** 1 person, responsible for test strategy and management
- **Functional Test Engineers:** 3 people, responsible for functional test execution
- **Automation Test Engineers:** 2 people, responsible for automation script development
- **Performance Test Engineer:** 1 person, responsible for performance testing
- **Security Test Engineer:** 1 person (part-time), responsible for security testing
#### Tools and Environment
- **Test Management:** Jira/TestRail
- **Automation Tools:** Selenium/Appium/Postman
- **Performance Tools:** JMeter/LoadRunner
- **Security Tools:** OWASP ZAP/Burp Suite
- **CI/CD Tools:** Jenkins/GitLab CI
#### Test Environment
- **Development Environment:** Developer daily development testing
- **Test Environment:** Functional testing and integration testing
- **Pre-production Environment:** Performance testing and user acceptance testing
- **Production Environment:** Production release and monitoring
### Risk Management
#### Test Risk Identification
| Risk Item | Impact Level | Probability | Risk Level | Response Strategy |
|-----------|--------------|-------------|------------|-------------------|
| Frequent requirement changes | High | Medium | High | Agile testing methods |
| Insufficient test time | High | Medium | High | Priority management |
| Unstable test environment | Medium | High | Medium | Environment monitoring |
| Insufficient personnel skills | Medium | Low | Low | Training plan |
#### Risk Response Measures
- **Requirement Management:** Establish requirement change control process
- **Time Management:** Develop detailed test plans and priorities
- **Environment Management:** Establish stable test environment and monitoring
- **Personnel Management:** Provide necessary skill training and support
### Quality Control
#### Quality Measurement Metrics
- **Test Coverage:** Requirement coverage, code coverage
- **Defect Metrics:** Defect discovery rate, defect fix rate, defect density
- **Efficiency Metrics:** Test execution efficiency, automation rate
- **Quality Metrics:** User satisfaction, system stability
#### Quality Gates
- **Code Quality Gate:** Unit test pass rate ≥ 80%
- **Functional Quality Gate:** System test pass rate ≥ 95%
- **Performance Quality Gate:** Performance metrics meet requirements
- **Security Quality Gate:** No high-risk security vulnerabilities
### Communication and Collaboration
#### Communication Mechanism
- **Daily Communication:** Daily standup, sync progress and issues
- **Weekly Meetings:** Weekly test progress and risk assessment
- **Milestone Reviews:** Quality reviews at important milestones
- **Release Decisions:** Release decisions based on test results
#### Collaboration Process
- **Requirement Clarification:** Clarify test requirements with product team
- **Test Collaboration:** Collaborate with development team on test execution
- **Defect Management:** Collaborate with development team on defect fixes
- **Release Coordination:** Coordinate release process with operations team
### Continuous Improvement
#### Improvement Mechanism
- **Test Retrospective:** Test retrospective after each version
- **Process Optimization:** Optimize test processes based on issues and feedback
- **Tool Upgrades:** Continuously evaluate and upgrade test tools
- **Skill Enhancement:** Team skill training and knowledge sharing
#### Success Criteria
- **Quality Goal Achievement:** All quality metrics meet expectations
- **Schedule On Track:** Test activities completed as planned
- **Cost Control:** Test costs within budget
- **Team Satisfaction:** Smooth team collaboration, high satisfaction
### Emergency Plan
#### Emergency Situation Handling
- **Critical Defects:** Immediately stop testing, assess impact
- **Environment Failure:** Quick recovery or switch to backup environment
- **Personnel Changes:** Knowledge transfer and personnel reallocation
- **Time Compression:** Adjust test scope and priorities
#### Release Risk Control
- **Risk Assessment:** Assess release risks based on test results
- **Rollback Preparation:** Prepare quick rollback solutions
- **Enhanced Monitoring:** Strengthen system monitoring after release
- **Emergency Response:** Establish quick response mechanismsExecution Instructions
- Analyze project characteristics and quality requirements
- Develop comprehensive test strategies and methods
- Plan test resources and time arrangements
- Establish quality control and risk management mechanisms
Please provide project information and quality requirements, and I will develop test strategy plan.
📋 Change Log
v0.1 (2025-01-14)
- Initial version