Re: Unit test code in HARMONY-16

2006-01-16 Thread Mikhail Loenko
.apache.org > > > To > harmony-dev@incubator.apache.org > cc > > Subject > Re: Unit test code in HARMONY-16 > > > > > > > Hi George, > > Thanks for your clarifications > > Could you please try setting 'printAllowed' to false in th

Re: Unit test code in HARMONY-16

2006-01-16 Thread George Harley1
est regards, George George C. Harley Mikhail Loenko <[EMAIL PROTECTED]> 16/01/2006 12:27 Please respond to harmony-dev@incubator.apache.org To harmony-dev@incubator.apache.org cc Subject Re: Unit test code in HARMONY-16 Hi George,

Re: Unit test code in HARMONY-16

2006-01-16 Thread Mikhail Loenko
remember a while back on > >>another project that I knew the timings of things on my machine just > >>from practice, and I could tell when we changed something that impacted > >>performance, because the tests ran longer. This helped catch problems > >>early. > >>

Re: Unit test code in HARMONY-16

2006-01-16 Thread Geir Magnusson Jr
ests ran longer. This helped catch problems early. geir Thanks, Mikhail Loenko Intel Middleware Products Division -Original Message- From: George Harley1 [mailto:[EMAIL PROTECTED] Sent: Friday, January 13, 2006 7:24 PM To: harmony-dev@incubator.apache.org Subject: RE: Unit test c

Re: Unit test code in HARMONY-16

2006-01-16 Thread Mikhail Loenko
__ > George C. Harley > > > > > > "Loenko, Mikhail Y" <[EMAIL PROTECTED]> > 16/01/2006 04:42 > Please respond to > harmony-dev@incubator.apache.org > > > To > > cc > > Subject > RE: Unit test code in HARMONY-16 >

Re: Unit test code in HARMONY-16

2006-01-16 Thread Tim Ellison
g that impacted >>performance, because the tests ran longer. This helped catch problems >>early. >> >>geir >> >> >> >>>Thanks, >>>Mikhail Loenko >>>Intel Middleware Products Division >>> >>> >>>>-

RE: Unit test code in HARMONY-16

2006-01-16 Thread George Harley1
s, George George C. Harley "Loenko, Mikhail Y" <[EMAIL PROTECTED]> 16/01/2006 04:42 Please respond to harmony-dev@incubator.apache.org To cc Subject RE: Unit test code in HARMONY-16 Hi George We will remove all the tests and these QA guys will never disturb us :) E

Re: Unit test code in HARMONY-16

2006-01-16 Thread Mikhail Loenko
, because the tests ran longer. This helped catch problems > early. > > geir > > > > > > Thanks, > > Mikhail Loenko > > Intel Middleware Products Division > > > >> -Original Message- > >> From: George Harley1 [mailto:[EMAIL PROT

Re: Unit test code in HARMONY-16

2006-01-16 Thread Geir Magnusson Jr
:[EMAIL PROTECTED] Sent: Friday, January 13, 2006 7:24 PM To: harmony-dev@incubator.apache.org Subject: RE: Unit test code in HARMONY-16 Hi Mikhail, Thanks for your very complete answer. At some point we had different functionality in the PerformanceTest but it seems to have died now. That is

RE: Unit test code in HARMONY-16

2006-01-15 Thread Loenko, Mikhail Y
George Harley1 [mailto:[EMAIL PROTECTED] >Sent: Friday, January 13, 2006 7:24 PM >To: harmony-dev@incubator.apache.org >Subject: RE: Unit test code in HARMONY-16 > >Hi Mikhail, > >Thanks for your very complete answer. > >> At some point we had different functionality in

RE: Unit test code in HARMONY-16

2006-01-13 Thread George Harley1
"Loenko, Mikhail Y" <[EMAIL PROTECTED]> 13/01/2006 12:12 Please respond to harmony-dev@incubator.apache.org To cc Subject RE: Unit test code in HARMONY-16 As far as we did not have special performance tests, we used unit tests to measure performance, i.e. to compare perform

RE: Unit test code in HARMONY-16

2006-01-13 Thread Loenko, Mikhail Y
As far as we did not have special performance tests, we used unit tests to measure performance, i.e. to compare performance of our classes to performance of "standard" classes. So we ran in cycle a single unit test on both when there are our security classes in bootclasspath and when there are not.