LogoLogo
Product
  • Knowledge Base
  • What's New
  • Guides
  • User Story Coverage
    • Getting Started
    • User Story Challenges & Solution
      • Typical Implementation
      • The Challenges
      • The Solution
    • User Story Coverage Report Overview
      • Release Go / No Go Report
        • How to Generate / Edit the Report
      • User Story Quality Overview
        • How to Generate the User Story View
      • User Story Coverage Analysis
        • How to Generate the Analysis View
      • Uncovered Methods View
        • How to Generate the View
      • Customization
      • Integration
    • Use Cases by Persona
      • Managers
        • Informed Go/No Go Decisions Making
        • Effective Resources Prioritization
        • Overall Progress Monitoring
      • Developers
        • Code Quality Ownership
        • Seamless Collaboration with QA
        • Code Review Facilitator
      • QA Engineers
        • Test Execution Progress Monitoring
        • Testing Effort Prioritization
        • Testing Strategy Planing
    • Technical Overview
      • User Story Coverage Mechanism
      • Technical Architecture
      • Deployment Guide
        • US1_getResults.sh
        • US2_createReport.sh
        • US_UpdateConfluence.sh
  • Test Optimization
    • Getting Started
    • Test Execution Challenges & Solution
      • The Challenges
      • Test Optimization Solution
      • Test Optimization Main Advantages
    • Test Optimization Overview
      • Automated Test Optimization
      • Manual Test Optimization
      • Test Optimization for Pull Request
      • Test Selection Policies
        • Full Run Policy
        • No Code Changes Policy
        • Common Code Policy
        • Fastest Path to 100% Coverage Policy
      • Integrations
    • Use Cases by Persona
      • Managers
        • Fast Delivery
        • Resource Optimization
        • Thorough Testing in Tight Schedule
      • Developers
        • Exploring Only Relevant Test Failures
        • Faster Feedback Loop
        • Shift Left Testing
      • QA Engineers & Manual Testers
        • Faster & Focused Manual Testing
        • Optimizing Test Suite
        • Having Stable Product for Testing
    • Technical Overview
      • Test Optimization Mechanism
        • Associating Code With Tests
          • Statistical modeling
          • One-to-One Mapping
          • Calibration
        • Detecting Modified Code
        • Generating Test Recommendations
      • Technical Architecture
      • Deployment Guide
  • Quality Improvement
    • Getting Started
    • Challenges & Approach Comparison
      • The Challenges
      • Quality Improvement Approaches
      • Choosing the Right Approach
    • Quality Improvement Solution Overview
      • Test Gaps Analysis Report
        • How to Generate / Edit the Report
      • Coverage Trend Report
        • How to Generate / Edit the Report
      • Proof of Testing Report
        • How to Generate / Edit the Report
      • Release Quality Improvement Guide
        • STEP 1: Deploy SeaLights
        • STEP 2: Take a Quality Snapshot
        • STEP 3: Prioritize Code Areas
          • Add Code Labels
          • Ignore Irrelevant Code
          • Perform a Deep CSV Analysis
        • STEP 4: Set Baseline & Threshold
        • STEP 5: Analyze Test Gaps
        • STEP 6: Write Tests
        • Step 7: Make a Go / No Go Decision Based on Quality Gate
        • STEP 8: Measure Defect Escape Rate
      • Over Time Quality Improvement Guide
        • STEP 1: Deploy SeaLights
        • STEP 2: Take a Quality Snapshot
        • STEP 3: Prioritize code areas
          • Add Code Labels
          • Ignore Irrelevant Code
          • Perform a Deep CSV Analysis
        • STEP 4: Set Baseline & Goal
        • STEP 5: Set timeline
        • STEP 6: Write tests
        • STEP 7: Monitor progress
        • STEP 8: Measure Defect Escape Rate
    • Use Cases by Persona
      • Managers
        • Effective Prioritization & Budget Allocation
        • Tracking Progress & Measuring Impact
        • Data-Driven Release Decisions
        • Transparency & Communication
      • Developers
        • Mastering Code Coverage
        • Seamless Collaboration with QA
        • Code Quality Ownership
      • QA Engineers
        • Prioritizing Test Efforts
        • Contributing to Release Informed Decisions
        • Seamless Collaboration with Developers
        • Evaluating Testing Strategy
    • Technical Overview
      • Solution Mechanism
      • Technical Architecture
      • Deployment Guide
  • Value Proposition
    • Overview
    • Quality Use Cases
      • Go/No Go Decisions
      • Quality Improvement & Test Gaps
      • Governance & Quality Gates
      • Compliance & Proof of Testing
    • Test Optimization Use Cases
      • Reduce Costs & Infrastructure
      • Shorten Release Cycles
      • Reduce Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. User Story Coverage
  2. Use Cases by Persona
  3. QA Engineers

Testing Strategy Planing

PreviousTesting Effort PrioritizationNextTechnical Overview

Was this helpful?

The User Story Coverage Report is a valuable tool for QA teams to plan a testing strategy. Combine it with your professional judgment, context awareness, and collaboration to create a robust and effective testing strategy.


Step-by-Step Tutorial

1. Define Testing Goals and Resources
  • Clearly define what "good" coverage means for your project. Consider factors like risk, complexity, and regulatory requirements.

  • Estimate the resources available for testing: This includes team size, skill sets, and tools.

  • Align testing goals with resources: Be realistic about what is achievable within your constraints.

  • Set clear expectations: Communicate your testing strategy and coverage goals to the team.

2. Access the Report
  • Navigate to your relevant Jira project and open the Sheets page with the User Story Coverage report.

  • If unavailable, follow the How to Generate / Edit the Report guide to create it.

3. Ensure Scope Accuracy
  • Verify the report covers the intended timeframe using the Scope icon at the bottom right.

  • Adjust the scope as needed, referring to the How to Generate / Edit the Report guide.

4. Analyze Overall Coverage
  • Start by assessing the overall coverage across all user stories. Look for trends in "Modified Coverage" and "Non-Unit Tests Coverage" to identify areas of concern.

  • Drill down into user stories below 100% coverage: Prioritize those with red or orange flags, especially critical stories.

  • Collaborate with developers: Discuss your assessment with developers to gain deeper insights and identify potential risks hidden within seemingly good coverage numbers.

  • Analyze individual test types: See if coverage for specific types (e.g., component, end-to-end) are lacking across multiple stories. This might indicate broader testing gaps.

5. Leverage the Report for Specific Strategies
  • Identify critical scenarios and edge cases: Use the report to pinpoint specific parts of user stories requiring extensive testing.

  • Plan test types based on coverage gaps: Use identified gaps to determine which test types (e.g., performance, component) to prioritize, base on the test strategy.

  • Map resources to specific user stories: Assign testers with relevant skills to stories based on their complexity and testing needs to achieve the testing goals.

6. Use the Report for Continuous Improvement
  • Track progress over time: Monitor trends in coverage to identify areas for improvement.

  • Conduct regular reviews: Discuss gaps and challenges with stakeholders, including developers and product owners.

  • Refine your strategy: Adapt your testing approach based on feedback and real-world data from the report.