[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search
 
Modify

CLDR Ticket #6414(accepted unittest)

Opened 4 years ago

Last modified 2 years ago

Add unit tests

Reported by: mark Owned by: yoshito
Component: other Data Locale:
Phase: rc Review:
Weeks: Data Xpath:
Xref:

Description

This has been split off from ##6371, with the tests divided up as per the spreadsheet below.


For each test (method starting with Test/test...), make sure that it runs, eg convert println's into error checks where possible, otherwise generally loglns. If the test exposes a real problem, file a bug, and add logKnownBug() to make sure it still passes.

Change names of methods from Test/test... that can't reasonably be converted into tests. If nothing remains suitable as a test, change the inheritance to not be from TestFmwk.

https://docs.google.com/spreadsheet/ccc?key=0AqRLrRqNEKv-dDRDY3I4enBlSHFTa19ieUltNWkydkE#gid=0

Attachments

Change History

comment:1 Changed 4 years ago by yoshito

  • Milestone changed from 24rc to 25dsub

comment:2 Changed 4 years ago by srl

there's a new utility, find-unrun-tests.sh (about to be checked in). It gives the following report.

---- Unit Test Report ----
Lines ending in '<' are tests that exist but are not run.
Lines ending in '>' are tests that are run but don't exist (!)
GenerateTransformTest					      <
LanguageInfoTest					      <
LanguageTest						      <
LikelySubtagsTest					      <
TestAttributes						      <
TestBCP47						      <
TestBcp47Numbers					      <
TestBcp47Transforms					      <
TestCldrResolver					      <
TestDateOrder						      <
TestDtdCompatibility					      <
TestFallbackIterator					      <
TestFmwkPlus						      <
TestIdentifierInfo					      <
TestKeyboardModifierSet					      <
TestPathsModule						      <
TestTransforms						      <
TestUExtension						      <
TestXMLSource						      <

And the following are just wrong- should be under unittest.
org/unicode/cldr/test/TestCLDRTests.java:public class TestCLDRTests extends TestFmwk {
org/unicode/cldr/test/CLDRTest.java:public class CLDRTest extends TestFmwk {
org/unicode/cldr/test/TestTransformsSimple.java:public class TestTransformsSimple extends TestFmwk {
org/unicode/cldr/icu/TestCldr.java:public class TestCldr extends TestFmwk {
org/unicode/cldr/draft/TransformTest.java:public class TransformTest extends TestFmwk {
org/unicode/cldr/draft/GapStringTest.java:public class GapStringTest extends TestFmwk {
com/ibm/icu/dev/test/ListFormatTest.java:public class ListFormatTest extends TestFmwk {
com/ibm/icu/dev/test/GenderInfoTest.java:public class GenderInfoTest extends TestFmwk {

comment:3 Changed 4 years ago by emmons

  • Milestone changed from 25dsub to 25M1

Moving all 25dsub to 25M1. Please adjust the milestone if you are not planning to complete the item in the 25M1 time frame.

comment:4 Changed 4 years ago by yoshito

  • Milestone changed from 25M1 to 25rc

comment:5 Changed 4 years ago by yoshito

  • Milestone changed from 25rc to 26dsub

Hmm.. I actually do not know what I should do with this ticket. Revisit after 25.

comment:6 Changed 4 years ago by emmons

  • Milestone changed from 26dsub to 26dvet

Moving all 26dsub to 26dvet. Please assess the need to complete tickets by 26dvet, which is 2014-06-19

comment:7 Changed 3 years ago by yoshito

  • Milestone changed from 26dvet to 27rc

comment:8 Changed 3 years ago by markus

  • Phase set to rc
  • Milestone changed from 27rc to 27

comment:9 Changed 3 years ago by emmons

  • Milestone changed from 27 to 28

comment:10 Changed 3 years ago by markus

  • Type changed from defect to unittest
  • Component changed from test to unknown

comment:11 Changed 3 years ago by srl

  • Status changed from new to accepted

comment:12 Changed 2 years ago by emmons

  • Component changed from unknown to other

comment:13 Changed 2 years ago by emmons

  • Milestone changed from 28 to 28roll

Moving all outstanding 28 tickets to 28roll. We will discuss disposition of these at the next CLDR TC.

View

Add a comment

Modify Ticket

Action
as accepted
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.