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 Effort Prioritization

PreviousTest Execution Progress MonitoringNextTesting Strategy Planing

Was this helpful?

The User Story Coverage Report empowers QA engineers to prioritize testing efforts effectively and collaborate seamlessly with developers. By combining strategic prioritization with proactive collaboration, you can achieve comprehensive testing coverage and deliver high-quality software with confidence.

Tips for fostering collaboration:

  • Bridge the Gap: Utilize the report to proactively engage developers in discussions. Identifying untested methods is just the beginning.

  • Seek Clarification: Schedule regular meetings to discuss complex methods and seek their expertise.

  • Joint Ownership: Foster a collaborative spirit to overcome challenges and ensure comprehensive testing.


Step-by-Step Tutorial

1. Access the Report
  • Navigate to your relevant Jira project and locate the User Story Coverage report within the Sheets page.

  • If unavailable, follow the How to Generate / Edit the Report guide for creation.

2. 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.

3. Visualize and Analyze
  • Simplify View: Collapse subtasks under user stories (or your hierarchy) for better visualization.

  • Review Metrics: Analyze both Modified Coverage and Non-Unit Tests Coverage for each user story.

4. Identify and Categorize Gaps

Focus your efforts on areas most likely to lack comprehensive testing. Expand these user stories to pinpoint specific subtasks lacking tests.

Critical Non-Unit Test Gaps:

  • Begin by prioritizing user stories where Non-Unit Tests Coverage is marked red (low coverage) or orange (requires improvement).

  • These stories have the highest potential for missing crucial non-functional aspects like integration, usability, or performance.

  • Verify Satisfactory Coverage: Ensure subtasks with sufficient coverage align with your testing strategy (e.g., API testing for relevant changes).

Address Moderate Non-Unit Test Gaps:

  • After addressing critical gaps, move to stories with green Non-Unit Tests Coverage, but not 100%.

  • Analyze these stories closely, as moderate gaps could still indicate vulnerabilities.

  • Address Specific Test Types: Assess individual test type coverage against your standards and identify responsible subtasks.

5. Craft a Testing Plan
  • Categorize Gaps: Create separate lists for:

    • Uncovered subtasks.

    • Subtasks with low coverage.

    • Subtasks lacking crucial test types (based on your strategy).

  • Assign Ownership: Match each list item with its parent user story for context.

6. Prioritize Resources

Strategic Allocation: Follow this sequence:

  • Address uncovered subtasks first (complete testing absence).

  • Move to subtasks with low coverage, prioritizing based on severity and impact.

  • Assign relevant individuals to cover subtasks within critical test types, focusing on sensitive code sections and critical functionality.

Remember: This framework serves as a foundation. Adapt it to your specific organizational needs, testing strategies, and resource availability.