You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Sean Qiu <se...@gmail.com> on 2007/10/17 04:58:40 UTC

[Test] Shall we maintain a individual archive for our classlib unit test?

Like some other famous open source project , i.e. derby,eclipse, they will
release the project as well as a individual jar of their test.
Gnu Classpath even has sub-project called Mauve which consists of many unit
test.

Harmony has so many unit tests that our user can make use of.
Most user will download our binary release rather than checking out the
souce, building and testing.
I guess we can archive a testing.jar for user, so they can test their binary
jre directly without any building.

Within a testing.jar and a build.xml, we can run test through one command:

$> ant -Dtest.jre.dir=${path}/jre

What's more, there are two kinds of test, some are harmony implementation
dependent tests.
And the rest are public api tests.
We can publish the public API tests for other independent implementation.
(Though the candidates are hard to find right now.)

Even RI can use our test if they want.

Any comments? Suggestions?

-- 
Sean Qiu
China Software Development Lab, IBM

Re: [Test] Shall we maintain a individual archive for our classlib unit test?

Posted by Sian January <si...@googlemail.com>.
This would be a really useful feature.  I think HARMONY-950 and HARMONY-984
are the relevant JIRAs.

Regards,

Sian


On 17/10/2007, Alexey Varlamov <al...@gmail.com> wrote:
> The idea is floating around for a while, there are related JIRA
> entries with 3-digit ids ;). Surely it worths to be done, all
> components (including not only classlib but drlvm and jdktools as
> well) have a lot of tests suitable for that.
> We just need a framework (either standalone or a part of build system)
> - so patches are always welcome :)
>
> 2007/10/17, Sean Qiu <se...@gmail.com>:
> > Of couse we can.
> > We have our classlib modularized, so does their test.
> >
> > 2007/10/17, Xiao-Feng Li <xi...@gmail.com>:
> > >
> > > On 10/17/07, Sean Qiu <se...@gmail.com> wrote:
> > > > Like some other famous open source project , i.e. derby,eclipse,
they
> > > will
> > > > release the project as well as a individual jar of their test.
> > > > Gnu Classpath even has sub-project called Mauve which consists of
many
> > > unit
> > > > test.
> > > >
> > > > Harmony has so many unit tests that our user can make use of.
> > > > Most user will download our binary release rather than checking out
the
> > > > souce, building and testing.
> > > > I guess we can archive a testing.jar for user, so they can test
their
> > > binary
> > > > jre directly without any building.
> > > >
> > > > Within a testing.jar and a build.xml, we can run test through one
> > > command:
> > > >
> > > > $> ant -Dtest.jre.dir=${path}/jre
> > > >
> > > > What's more, there are two kinds of test, some are harmony
> > > implementation
> > > > dependent tests.
> > > > And the rest are public api tests.
> > > > We can publish the public API tests for other independent
> > > implementation.
> > > > (Though the candidates are hard to find right now.)
> > > >
> > > > Even RI can use our test if they want.
> > > >
> > > > Any comments? Suggestions?
> > > >
> > >
> > > Probably a good idea. It should also consider the case that people
> > > developing a module may only care about the tests of that module.
> > >
> > > Thanks,
> > > xiaofeng
> > >
> > > > --
> > > > Sean Qiu
> > > > China Software Development Lab, IBM
> > > >
> > >
> > >
> > > --
> > > http://xiao-feng.blogspot.com
> > >
> >
> >
> >
> > --
> > Sean Qiu
> > China Software Development Lab, IBM
> >
>



-- 
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

Re: [Test] Shall we maintain a individual archive for our classlib unit test?

Posted by Sean Qiu <se...@gmail.com>.
Great.

2007/10/17, Alexey Varlamov <al...@gmail.com>:
>
> The idea is floating around for a while, there are related JIRA
> entries with 3-digit ids ;). Surely it worths to be done, all
> components (including not only classlib but drlvm and jdktools as
> well) have a lot of tests suitable for that.
> We just need a framework (either standalone or a part of build system)
> - so patches are always welcome :)
>
> 2007/10/17, Sean Qiu <se...@gmail.com>:
> > Of couse we can.
> > We have our classlib modularized, so does their test.
> >
> > 2007/10/17, Xiao-Feng Li <xi...@gmail.com>:
> > >
> > > On 10/17/07, Sean Qiu <se...@gmail.com> wrote:
> > > > Like some other famous open source project , i.e. derby,eclipse,
> they
> > > will
> > > > release the project as well as a individual jar of their test.
> > > > Gnu Classpath even has sub-project called Mauve which consists of
> many
> > > unit
> > > > test.
> > > >
> > > > Harmony has so many unit tests that our user can make use of.
> > > > Most user will download our binary release rather than checking out
> the
> > > > souce, building and testing.
> > > > I guess we can archive a testing.jar for user, so they can test
> their
> > > binary
> > > > jre directly without any building.
> > > >
> > > > Within a testing.jar and a build.xml, we can run test through one
> > > command:
> > > >
> > > > $> ant -Dtest.jre.dir=${path}/jre
> > > >
> > > > What's more, there are two kinds of test, some are harmony
> > > implementation
> > > > dependent tests.
> > > > And the rest are public api tests.
> > > > We can publish the public API tests for other independent
> > > implementation.
> > > > (Though the candidates are hard to find right now.)
> > > >
> > > > Even RI can use our test if they want.
> > > >
> > > > Any comments? Suggestions?
> > > >
> > >
> > > Probably a good idea. It should also consider the case that people
> > > developing a module may only care about the tests of that module.
> > >
> > > Thanks,
> > > xiaofeng
> > >
> > > > --
> > > > Sean Qiu
> > > > China Software Development Lab, IBM
> > > >
> > >
> > >
> > > --
> > > http://xiao-feng.blogspot.com
> > >
> >
> >
> >
> > --
> > Sean Qiu
> > China Software Development Lab, IBM
> >
>



-- 
Sean Qiu
China Software Development Lab, IBM

Re: [Test] Shall we maintain a individual archive for our classlib unit test?

Posted by Mark Hindess <ma...@googlemail.com>.
Another vital step that is still outstanding is modifying all tests to
load resources from the classpath so that both tests and resources can
be bundled in a jar.  Some tests already do this but I think many still
reference files directly.

-Mark.

On 17 October 2007 at 12:50, "Alexey Varlamov" <al...@gmail.com> wrote:
> The idea is floating around for a while, there are related JIRA
> entries with 3-digit ids ;). Surely it worths to be done, all
> components (including not only classlib but drlvm and jdktools as
> well) have a lot of tests suitable for that.
> We just need a framework (either standalone or a part of build system)
> - so patches are always welcome :)
> 
> 2007/10/17, Sean Qiu <se...@gmail.com>:
> > Of couse we can.
> > We have our classlib modularized, so does their test.
> >
> > 2007/10/17, Xiao-Feng Li <xi...@gmail.com>:
> > >
> > > On 10/17/07, Sean Qiu <se...@gmail.com> wrote:
> > > > Like some other famous open source project , i.e. derby,eclipse, they
> > > will
> > > > release the project as well as a individual jar of their test.
> > > > Gnu Classpath even has sub-project called Mauve which consists of many
> > > unit
> > > > test.
> > > >
> > > > Harmony has so many unit tests that our user can make use of.
> > > > Most user will download our binary release rather than checking out the
> > > > souce, building and testing.
> > > > I guess we can archive a testing.jar for user, so they can test their
> > > binary
> > > > jre directly without any building.
> > > >
> > > > Within a testing.jar and a build.xml, we can run test through one
> > > command:
> > > >
> > > > $> ant -Dtest.jre.dir=${path}/jre
> > > >
> > > > What's more, there are two kinds of test, some are harmony
> > > implementation
> > > > dependent tests.
> > > > And the rest are public api tests.
> > > > We can publish the public API tests for other independent
> > > implementation.
> > > > (Though the candidates are hard to find right now.)
> > > >
> > > > Even RI can use our test if they want.
> > > >
> > > > Any comments? Suggestions?
> > > >
> > >
> > > Probably a good idea. It should also consider the case that people
> > > developing a module may only care about the tests of that module.
> > >
> > > Thanks,
> > > xiaofeng
> > >
> > > > --
> > > > Sean Qiu
> > > > China Software Development Lab, IBM
> > > >
> > >
> > >
> > > --
> > > http://xiao-feng.blogspot.com
> > >
> >
> >
> >
> > --
> > Sean Qiu
> > China Software Development Lab, IBM
> >
> 



Re: [Test] Shall we maintain a individual archive for our classlib unit test?

Posted by Alexey Varlamov <al...@gmail.com>.
The idea is floating around for a while, there are related JIRA
entries with 3-digit ids ;). Surely it worths to be done, all
components (including not only classlib but drlvm and jdktools as
well) have a lot of tests suitable for that.
We just need a framework (either standalone or a part of build system)
- so patches are always welcome :)

2007/10/17, Sean Qiu <se...@gmail.com>:
> Of couse we can.
> We have our classlib modularized, so does their test.
>
> 2007/10/17, Xiao-Feng Li <xi...@gmail.com>:
> >
> > On 10/17/07, Sean Qiu <se...@gmail.com> wrote:
> > > Like some other famous open source project , i.e. derby,eclipse, they
> > will
> > > release the project as well as a individual jar of their test.
> > > Gnu Classpath even has sub-project called Mauve which consists of many
> > unit
> > > test.
> > >
> > > Harmony has so many unit tests that our user can make use of.
> > > Most user will download our binary release rather than checking out the
> > > souce, building and testing.
> > > I guess we can archive a testing.jar for user, so they can test their
> > binary
> > > jre directly without any building.
> > >
> > > Within a testing.jar and a build.xml, we can run test through one
> > command:
> > >
> > > $> ant -Dtest.jre.dir=${path}/jre
> > >
> > > What's more, there are two kinds of test, some are harmony
> > implementation
> > > dependent tests.
> > > And the rest are public api tests.
> > > We can publish the public API tests for other independent
> > implementation.
> > > (Though the candidates are hard to find right now.)
> > >
> > > Even RI can use our test if they want.
> > >
> > > Any comments? Suggestions?
> > >
> >
> > Probably a good idea. It should also consider the case that people
> > developing a module may only care about the tests of that module.
> >
> > Thanks,
> > xiaofeng
> >
> > > --
> > > Sean Qiu
> > > China Software Development Lab, IBM
> > >
> >
> >
> > --
> > http://xiao-feng.blogspot.com
> >
>
>
>
> --
> Sean Qiu
> China Software Development Lab, IBM
>

Re: [Test] Shall we maintain a individual archive for our classlib unit test?

Posted by Sean Qiu <se...@gmail.com>.
Of couse we can.
We have our classlib modularized, so does their test.

2007/10/17, Xiao-Feng Li <xi...@gmail.com>:
>
> On 10/17/07, Sean Qiu <se...@gmail.com> wrote:
> > Like some other famous open source project , i.e. derby,eclipse, they
> will
> > release the project as well as a individual jar of their test.
> > Gnu Classpath even has sub-project called Mauve which consists of many
> unit
> > test.
> >
> > Harmony has so many unit tests that our user can make use of.
> > Most user will download our binary release rather than checking out the
> > souce, building and testing.
> > I guess we can archive a testing.jar for user, so they can test their
> binary
> > jre directly without any building.
> >
> > Within a testing.jar and a build.xml, we can run test through one
> command:
> >
> > $> ant -Dtest.jre.dir=${path}/jre
> >
> > What's more, there are two kinds of test, some are harmony
> implementation
> > dependent tests.
> > And the rest are public api tests.
> > We can publish the public API tests for other independent
> implementation.
> > (Though the candidates are hard to find right now.)
> >
> > Even RI can use our test if they want.
> >
> > Any comments? Suggestions?
> >
>
> Probably a good idea. It should also consider the case that people
> developing a module may only care about the tests of that module.
>
> Thanks,
> xiaofeng
>
> > --
> > Sean Qiu
> > China Software Development Lab, IBM
> >
>
>
> --
> http://xiao-feng.blogspot.com
>



-- 
Sean Qiu
China Software Development Lab, IBM

Re: [Test] Shall we maintain a individual archive for our classlib unit test?

Posted by Xiao-Feng Li <xi...@gmail.com>.
On 10/17/07, Sean Qiu <se...@gmail.com> wrote:
> Like some other famous open source project , i.e. derby,eclipse, they will
> release the project as well as a individual jar of their test.
> Gnu Classpath even has sub-project called Mauve which consists of many unit
> test.
>
> Harmony has so many unit tests that our user can make use of.
> Most user will download our binary release rather than checking out the
> souce, building and testing.
> I guess we can archive a testing.jar for user, so they can test their binary
> jre directly without any building.
>
> Within a testing.jar and a build.xml, we can run test through one command:
>
> $> ant -Dtest.jre.dir=${path}/jre
>
> What's more, there are two kinds of test, some are harmony implementation
> dependent tests.
> And the rest are public api tests.
> We can publish the public API tests for other independent implementation.
> (Though the candidates are hard to find right now.)
>
> Even RI can use our test if they want.
>
> Any comments? Suggestions?
>

Probably a good idea. It should also consider the case that people
developing a module may only care about the tests of that module.

Thanks,
xiaofeng

> --
> Sean Qiu
> China Software Development Lab, IBM
>


-- 
http://xiao-feng.blogspot.com