firefox-devtools/profiler

Test coverage for src/components/header

Open

#734 opened on Jan 24, 2018

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)TypeScript (486 forks)auto 404
code maintenancehelp wantedtests

Repository metrics

Stars
 (1,515 stars)
PR merge metrics
 (PR metrics pending)

Description

In attempting to uncover our worst offenders for code coverage, the header component stands out.

  • TimeSelectionScrubber (53 lines uncovered)
  • IntervalMarkerOverview (47 lines uncovered)
  • ProfileThreadHeaderContextMenu (26 lines uncovered)
  • SelectionScrubberOverlay (26 lines uncovered)
  • ProfileThreadHeaderBar (25 lines uncovered)
  • ThreadStackGraph (14 lines uncovered)
  • OverflowEdgeIndicator (8 lines uncovered)
  • ProfileThreadJankOverview (6 lines uncovered)
  • ProfileViewerHeader (3 lines uncovered)
  • TimeRuler (2 lines uncovered)
  • EmptyThreadIndicator (0 lines uncovered)
  • ProfileThreadTracingMarkerOverview (0 lines uncovered)

┆Issue is synchronized with this Jira Task

Contributor guide

Research direction
Examine the existing test patterns in the repository, locate the test files for the header components, and write tests covering the uncovered lines using the project's testing framework.
Tech stack
typescriptreact
Domain
frontend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJest
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75