LogoLogo
Contact SupportProduct
  • Knowledge Base
  • What's New
  • Guides
  • Agent Release Notes
  • Welcome!
  • Intro to SeaLights
    • What is SeaLights
      • Glossary
      • Working in Conjunction with Your Quality / Coverage Tools
        • SeaLights vs SonarQube
        • SeaLights vs JaCoCo
        • SeaLights vs CodeSee
    • Technical Overview
      • Test Stage Cycle
    • FAQ
  • Coverage & Quality Insights
    • Quality Insights Overview
    • User Story Coverage
      • 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
      • User Story Coverage Mechanism
    • Coverage Dashboard
    • Coverage Report
    • Test Gaps Report
      • Code Changes Calculation
        • Hidden Changes Detection
    • 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
  • Test Optimization
    • 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
    • Test Optimization Mechanism
      • Associating Code With Tests
        • Statistical modeling
        • One-to-One Mapping
        • Calibration
      • Detecting Modified Code
      • Generating Test Recommendations
  • Test Optimization - Savings Breakdown
    • TIA Configuration
  • Settings
    • Token Access & Management
    • Quality Gates
    • User Management
      • Managing Users
      • Managing Groups
      • Roles & Permissions
      • SSO Authentication
  • Code Labels
  • Code Scope (Ignore/Include)
  • Contact Support
Powered by GitBook
On this page
  • Seamless Access to Detailed User Story Coverage:
  • Absolute Numbers Guide Efficient Testing Resource Allocation

Was this helpful?

  1. Coverage & Quality Insights
  2. User Story Coverage

User Story Quality Overview

PreviousHow to Generate / Edit the ReportNextHow to Generate the User Story View

Last updated 1 year ago

Was this helpful?

Users can delve into the coverage details of individual user stories (and subtasks) and review:

  • The absolute number of modified methods and methods that have been thoroughly tested.

  • The breakdown of the coverage across various test stages.

Primary Users

Ideally suited for developers and QA engineers to track the coverage status of an individual user story and make informed decisions regarding the prioritization and allocation of testing resources.


Seamless Access to Detailed User Story Coverage:

Forget juggling multiple reports! The User Story Quality Overview view is conveniently accessible from anywhere within Jira. With a single click on any user story, you'll gain instant insights into:

  • Comprehensive Coverage: Get a holistic view of coverage percentage, both overall and for non-unit tests specifically.

  • Granular Breakdown: Dive deeper into the specific test types covering each user story, pinpointing areas that require closer attention.

  • Absolute Numbers: Understand the true testing effort involved by seeing the exact number of modified methods and the number of them covered by tests.

  • Deep Dives: For even more granular details, the provided link takes you to a dedicated reports where you can explore sub tasks coverage and individual methods in depth.

Absolute Numbers Guide Efficient Testing Resource Allocation

The absolute numbers presented in the view are crucial, as they provide a clear understanding of the testing effort required for each user story. Testing 25 methods out of 40 modified methods is significantly different from testing 525 out of 840 methods. While completing testing for 15 methods is relatively achievable, testing over 300 methods poses a much larger challenge.

This view empowers teams to make informed decisions regarding the prioritization and allocation of testing resources.