globalizejs/globalize

Test Coverage: How to improve?

Open

#319 opened on Sep 29, 2014

View on GitHub
 (8 comments) (0 reactions) (0 assignees)JavaScript (4,759 stars) (645 forks)batch import
help wantednew featurequestion

Description

How can we improve our test coverage? What test suites can we import (e.g., ECMA-402, google cldr implementation)?

How to improve test coverage reports?

  • grunt-qunit-instanbul

Contributor guide

Tech stack
javascript
Domain
testinginternationalizationlocalization
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
JavaScriptQUnitInternationalization basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
First, review the current test suite structure in the repository (likely under a 'test' directory). Then, examine the external test suites linked in the issue, such as those from ECMA 402 and CLDR implementations (e.g., twitter cldr rb). Assess which tests can be adapted and how to integrate them with the existing QUnit based setup. Finally, explore improving coverage reports using tools like Istanbul (grunt qunit instanbul).