hexojs/hexo

Improve test coverage

Open

#3,984 opened on Dec 18, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)TypeScript (5,017 forks)batch import
discussionhelp wanted

Repository metrics

Stars
 (41,376 stars)
PR merge metrics
 (Avg merge 5d 21h) (1 merged PR in 30d)

Description

Check List

Please check followings before submitting a new feature request.

  • I have already read Docs page
  • I have already searched existing issues

Feature Request

This repo's unit test coverage currently stands at Coverage Status.

For anyone who is interested in improving it, there are a few ways:

  1. Search for "missing-unit-test" to locate functions that haven't been covered.
  2. Click on the coverage badge link and it shows all the relevant lines.
  3. Line coverage report is also shown in the CI job log.

hexo-util Coverage Status also needs help.

Contributor guide

Research direction
Search for 'missing unit test' in the codebase, click on the coverage badge link to see uncovered lines, and examine CI job logs for line coverage reports.
Tech stack
typescriptnodejs
Domain
testing
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
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
GitNode.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70