globalizejs/globalize

Test: Support testing a range of CLDR versions

Open

#427 opened on Mar 24, 2015

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (4,759 stars) (645 forks)batch import
help wanted

Description

Currently, we run our unit and functional tests against the latest CLDR version.

First, we should raise the pros and cons of having tests executed for all supported CLDR versions, e.g., CLDR 25, CLDR 26, CLDR 27. Then, implement it.

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.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
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.
mostly clear
Prerequisites
JavaScripttesting basicsCLDR data structureglobalize library structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the existing test suite to understand how CLDR data is imported and used. Research the pros and cons of testing against multiple CLDR versions (e.g., CLDR 25, 26, 27). Look at the globalize source code for any version specific behavior. Then propose an implementation plan in the issue before coding.