globalizejs/globalize

Test Coverage: How to improve?

Open

#319 opened on Sep 29, 2014

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

Repository metrics

Stars
 (4,759 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Review the linked test suites from ECMA 402, Google CLDR, Twitter CLDR, and others to understand their structure and how they could be ported or integrated into Globalize. Check the existing test coverage reports and consider using grunt qunit istanbul for improved reporting.
Tech stack
javascript
Domain
testinginternationalization
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.
Needs investigation
Prerequisites
JavaScriptCLDRQUnit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40