Skip to content

[PHASE 1] Baseline Measurement and Coverage Gap Report #933

Open

Description

@ashleyshaw

Summary

Establish the initial coverage baseline and turn the current coverage gap into a documented implementation checklist.

Action

  • Action Type: Create
  • Target File: .github/projects/active/test-coverage-implementation/README.md

Proposed Test Content

This phase covers tasks 1.1 to 1.4 from the source README:

  • run the initial coverage report
  • generate and review the HTML coverage report
  • document baseline metrics and the gap to 80%
  • create the implementation checklist and execution order

Scope & Applicability

  • Type: Baseline audit and reporting
  • Affected Areas: repository-wide coverage reporting, baseline documentation, implementation planning
  • Audience: maintainers, developers, QA

Parent Issue

Acceptance Criteria

  • Coverage report runs successfully.
  • HTML report is reviewed and low-coverage files are identified.
  • Baseline metrics are recorded in the report artefact.
  • A prioritised implementation checklist exists for the remaining phases.
  • Change is documented in the project change log.
  • PR uses correct branch prefix (audit/).

Additional Context

This phase blocks every later phase, so it must be the first live issue in the chain.


Definition of Ready (DoR)

  • Purpose, scope, and audience defined
  • Target file and action type specified
  • Acceptance criteria listed
  • Estimate added (if applicable)

Definition of Done (DoD)

  • All acceptance criteria met and verified
  • Changelog entry prepared for PR
  • Test passes all required scenarios and environments
  • Documentation updated (if needed)
  • PR uses correct branch prefix (audit/)
  • Approved by at least one maintainer

Activity

  1. linear-code commented on Jun 8, 2026

    @linear-code
  2. added this to the milestone on Jun 19, 2026
  3. modified the milestones: , v1.4 on Jul 22, 2026
  4. ashleyshaw commented on Aug 5, 2026

    @ashleyshaw
    MemberAuthor

    Review Assessment - Phase 1: Baseline Measurement and Coverage Gap Report

    ✅ Starting gate for coverage programme - critical priority

    Strengths:

    • Establishes baseline for measurement comparison
    • Gap analysis will highlight areas needing work
    • Foundation for phases 2-6

    Assessment:

    This is the entry point for the entire coverage programme. Must complete before downstream phases can start.

    Key Deliverable:

    • Coverage gap report (to be used for phases 2-5 prioritization)
    • Baseline metrics snapshot

    Ready to Start?

    Yes — This is the first phase. Can start immediately.

    Recommended next: Schedule coverage run and collect baseline data.

  5. github-actions commented on Aug 5, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 57 day(s)
    • SLA state: SLA breached
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-08-05T10:08:20.185Z

    Maintained by project-meta-sync workflow.

  6. ashleyshaw commented on Aug 7, 2026

    @ashleyshaw
    MemberAuthor

    📋 Project Planning Update — test-coverage-implementation

    This issue is related to the test-coverage-implementation active project.

    📁 Project Documentation

    ✅ What's Been Completed

    Phase 1-3: Comprehensive audits, planning standardization, and RFC generation have been completed for this project. Detailed documentation is available in the project directory.

    🎯 Next Steps

    1. Review Project Documentation

      • Check project README for overview
      • Review OpenSpec RFC for implementation roadmap
      • Consult phase-specific documents
    2. For Implementation

      • Follow RFC success criteria and timeline
      • Check related issues for dependencies
      • Refer to project specifications

    🔗 Related Resources


    Co-Authored-By: Claude Haiku 4.5 noreply@anthropic.com

  7. github-actions commented on Sep 8, 2026

    @github-actions
    Contributor

    ⚠️ Bare Labels Detected

    This issue has labels that are not in the canonical taxonomy:

    • migrate:priority:critical
    • migrate:type:audit
    • migrate:area:testing
    • area:quality

    Valid Canonical Labels

    Please use labels with a prefix from the canonical taxonomy:

    • Type: type:bug, type:feature, type:task, type:documentation, etc.
    • Status: status:needs-triage, status:in-progress, status:done, etc.
    • Priority: priority:critical, priority:high, priority:normal, priority:low
    • Area: area:ci, area:docs, area:labels, area:security, etc.
    • Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

    For the complete list, see .github/labels.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Fields

Priority

Medium

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions