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. User Story Coverage Report Overview

Uncovered Methods View

PreviousHow to Generate the Analysis ViewNextHow to Generate the View

Was this helpful?

This alternative view skips the subtask grouping and presents a tailored list of only the uncovered modified methods per user story.

  • Indicates which methods have not been adequately tested, lacking coverage across all test types.

  • Identifies methods missing coverage within each specific test type, providing valuable insights for dedicated teams or individuals responsible for specific test stages, such as integration tests or end-to-end tests.

Primary Users

Ideally suited for developers and QA engineers to focus on uncovered methods of an individual user story, collaborate, make informed decisions regarding the prioritization and allocation of testing resources and track progress.


Focus Your Testing Efforts with the Uncovered Methods View

The Uncovered Methods View streamlines your testing prioritization by showcasing two key areas:

  1. Methods completely untested (across all types): These high-priority methods demand immediate attention and are listed first.

  2. Methods missing specific test types (functional, performance, etc.): Each test type has its own section, allowing you to easily identify untested areas and assign them to dedicated teams or individuals.

For clarity, methods lacking any non-unit test coverage are highlighted in orange, while completely untested methods (appearing in both sections) are flagged red.

Testing Recommendations:

  1. Address methods with no coverage across all tests first.

  2. Focus on methods missing non-unit test coverage next.

  3. Finally, consider covering methods in additional test types based on your organization's needs.

By following this guided approach, you can efficiently allocate resources and ensure comprehensive testing coverage.

How the Uncovered Methods View Differs from User Story Coverage Analysis?

While both views provide user story coverage information, the Uncovered Methods View offers a crucial advantage: centralized visibility and prioritization.

  • User Story Coverage Analysis:

    • Requires drilling down into individual subtasks.

    • Demands manually sifting through each method list to identify gaps.

    • Doesn't prioritize untested methods, leaving you to determine focus areas.

  • Uncovered Methods View:

    • Presents all untested methods across the user story in one comprehensive list.

    • Instantly reveals the bigger picture of coverage gaps, saving you time and effort.

    • Prioritizes methods based on severity:

      • Red flags methods completely untested (urgent attention).

      • Orange flags methods missing non-unit test coverage (important).

    • This clear prioritization empowers you to make quick decisions about testing allocation and assignment.

In essence, the Uncovered Methods View acts as a one-stop shop for identifying and prioritizing critical testing needs within a user story, saving you valuable time and ensuring efficient resource allocation.