Re: [jira] Created: (HARMONY-424) NullPointerException in java.text.DecimalFormat.getCurrency()

2006-04-28 Thread Richard Liang
Boris Kuznetsov (JIRA) wrote: NullPointerException in java.text.DecimalFormat.getCurrency() - Key: HARMONY-424 URL: http://issues.apache.org/jira/browse/HARMONY-424 Project: Harmony Type: Bug Environment

Re: [Fwd: Re: [classlib] Tests for serialization – which package, name?]

2006-04-28 Thread Mikhail Loenko
I suggest that we first decide how we will test serialization, otherwise we may make a low-level decision that will make some high-level designs impossible Thanks, Mikhail 2006/4/28, Paulex Yang <[EMAIL PROTECTED]>: > Stepan Mishura wrote: > > On 4/28/06, Paulex Yang wrote: > > > >> Paulex Yang

Re: [classlib] Tests for serialization – which package, name?

2006-04-28 Thread Mikhail Loenko
I meant that environment could be created, stored, and later reused by other test methods. Thanks, Mikhail 2006/4/28, Anton Avtamonov <[EMAIL PROTECTED]>: > On 4/28/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote: > > 2006/4/28, Anton Avtamonov <[EMAIL PROTECTED]>: > > > On 4/28/06, Mikhail Loenko <

Re: [Fwd: Re: [classlib] Te sts for serialization – which package, name?]

2006-04-28 Thread Paulex Yang
Stepan Mishura wrote: On 4/28/06, Paulex Yang wrote: Paulex Yang wrote: I think two serialization test is necessary in general: 1. test for Harmony itself, which ensure that the object can be serialized/deserialized smoothly within Harmony VM/classlib 2. test for compatibility with RI

Re: [classlib] Tests for serialization – which package, name?

2006-04-28 Thread Stepan Mishura
On 4/28/06, Anton Avtamonov wrote: > Stepan, > > I see everyone agree that we have to use the same approach accross the > modules, but have no agreement on the particular test layout approach. > May be you should initiate voting to choose the layout approach? > Just to decide either to have tests

Re: [classlib] charset decoding

2006-04-28 Thread Paulex Yang
Richard Liang wrote: Paulex Yang wrote: I see, the OutputStreamWriterTest does fail, seems there's some problem for CharsetDecoder to handling UTF-8 byte stream, but the InputStreamReader itself should work because it pass all tests for other decoding. I'll go on to study it. And I also real

Re: [classlib] charset decoding

2006-04-28 Thread Richard Liang
Paulex Yang wrote: Vladimir Strigun wrote: On 4/26/06, Paulex Yang <[EMAIL PROTECTED]> wrote: Andrew Zhang wrote: Mikhail Loenko wrote: 2006/4/26, Andrew Zhang <[EMAIL PROTECTED]>: Vladimir Strigun wrote: On 4/26/06, Andrew Zhang <[EMAIL PROTECTED]> wrote: I tr

Re: [Fwd: Re: [classlib] Tests for serialization – which package, name?]

2006-04-28 Thread Stepan Mishura
On 4/28/06, Paulex Yang wrote: > > Paulex Yang wrote: > > > I think two serialization test is necessary in general: > > > > 1. test for Harmony itself, which ensure that the object can be > > serialized/deserialized smoothly within Harmony VM/classlib > > 2. test for compatibility with RI, which e

Re: [classlib] Testing

2006-04-28 Thread Paulex Yang
Mikhail Loenko wrote: 2006/4/28, Paulex Yang <[EMAIL PROTECTED]>: Mikhail Loenko wrote: I suggest physically separate high-level suites: src/test/ | +- impl/ | +- compliant/[names might be changed] | +- stress/ | \- etc/ The

Re: [classlib] Testing

2006-04-28 Thread Mikhail Loenko
2006/4/28, Paulex Yang <[EMAIL PROTECTED]>: > Mikhail Loenko wrote: > > I suggest physically separate high-level suites: > > > > src/test/ > >| > >+- impl/ > >| > >+- compliant/[names might be changed] > >| > >+- stress/ > >| > >\

Re: [classlib] Tests for serialization – which package, name?

2006-04-28 Thread Anton Avtamonov
Stepan, I see everyone agree that we have to use the same approach accross the modules, but have no agreement on the particular test layout approach. May be you should initiate voting to choose the layout approach? Just to decide either to have tests in separate packages, separate TestCases or tog

Re: [classlib] Tests for serialization – wh ich package, name?

2006-04-28 Thread Richard Liang
Stepan Mishura wrote: On 4/28/06, Anton Avtamonov wrote: On 4/28/06, Stepan Mishura wrote: On 4/28/06, Anton Avtamonov wrote: On 4/28/06, Stepan Mishura wrote: On 4/27/06, Anton Avtamonov wrote: Which approach is better is very personal :-). I would ay t

Re: [Fwd: Re: [classlib] Te sts for serialization – which package, name?]

2006-04-28 Thread Paulex Yang
Paulex Yang wrote: Mikhail Loenko wrote: 2006/4/28, Paulex Yang <[EMAIL PROTECTED]>: Anton Avtamonov wrote: On 4/27/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote: As far as most of serialization tests extend SerializationTest then having serialization test cases included into a r

Re: [classlib] Tests for serialization – wh ich package, name?

2006-04-28 Thread Richard Liang
Anton Avtamonov wrote: On 4/28/06, Stepan Mishura <[EMAIL PROTECTED]> wrote: On 4/27/06, Anton Avtamonov wrote: On 4/27/06, Tim Ellison wrote: I say leave them mixed. We are no more likely to want to run serialization tests separately than we are locking tests etc. and trying

Re: [classlib] Testing

2006-04-28 Thread Paulex Yang
Mikhail Loenko wrote: I suggest physically separate high-level suites: src/test/ | +- impl/ | +- compliant/[names might be changed] | +- stress/ | \- etc/ Then on package-level separate classpath from bootclasspath stuff 1) We will r

Re: [classlib] Tests for serialization – which package, name?

2006-04-28 Thread Anton Avtamonov
On 4/28/06, Stepan Mishura <[EMAIL PROTECTED]> wrote: > On 4/28/06, Anton Avtamonov wrote: > > > > On 4/28/06, Stepan Mishura wrote: > > > On 4/28/06, Anton Avtamonov wrote: > > > > > > > > On 4/28/06, Stepan Mishura wrote: > > > > > On 4/27/06, Anton Avtamonov wrote: > > > > > > > > > > > > Whic

Re: [Fwd: Re: [classlib] Te sts for serialization – which package, name?]

2006-04-28 Thread Paulex Yang
Mikhail Loenko wrote: 2006/4/28, Paulex Yang <[EMAIL PROTECTED]>: Anton Avtamonov wrote: On 4/27/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote: As far as most of serialization tests extend SerializationTest then having serialization test cases included into a regular unit tests