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 2009/03/06 08:44:48 UTC
[testing] Proposal for archiving our tests into one bundle
Hi, All
I'm trying to archive our tests into some jars so that user can run the
tests directly as long as they get a copy of our run-time.( like
Harmony-Automated-Tests-M8.zip)
By this means, we can create a testing archive for each module as
well, luni-test.zip, security-test.zip......
I found we have made some efforts to archive our unit test into one bundle.
[1]
Now I plan to supply some patch for it. I've uploaded my completed patch to
HARMONY-6083[2].
(I've assigned this JIRA a port of HARMONY-984).
Below is my ongoing proposal.
trunk
|-- make | |-- run-test.xml * This ant build file
will be used to run tests after archiving (or any other names)
| |-- setting.properties Customer can setting parameters by
this properties file, such as ${test.jre.home}
|
|-- modules | |-- luni
| | |-- build.xml * Add a new task which will
package all luni tests to deploy/build/test/luni
| |
| |-- .... (other module)
|-- ...
|
|-- deploy/build/test (output)
|-- properties.xml Copy from
<trunk>/make/properties.xml, some common tasks
|-- setting.properties Copy from
<trunk>/make/setting.properties, some configuration properties for testing
|-- support.jar, derby.jar... Dependencies
jars will be used while testing
|-- build.xml Copy from
<trunk>/make/run-test.xml
|-- luni
| |-- resources Copy from
<trunk>/modules/luni/src/test/resources, may copy some support files
here,such as policy file in luni.
| |-- excludes Copy
from <trunk>/modules/luni/make/exclude.*, user can exclude tests by this
means.
| |-- luni_tests_impl.jar Tesing
archive
| |-- luni_tests_api.jar Testing
archive.
|
|-- security ...
|-- ... (other module)
Then we can archive whole test folder into one file for user.
User can test our milestone in addition to this file, there is no need to
checkout all src, building, testing....
I'm successfully run the our luni test by this means.
But there is still some extra work to refine the script.
(Your help is appreciated very much.)
What do you think about it?
Any suggestions or commends are welcomed.
[1] https://issues.apache.org/jira/browse/HARMONY-984
[2] https://issues.apache.org/jira/browse/HARMONY-6083
--
Best Regards
Sean, Xiao Xia Qiu
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Sean Qiu <se...@gmail.com>.
I will keep the script customize to our convention which separates
public and implementation dependent tests.
But we need perform extra task to separate them accordingly.
We've tried to use annotation(TestNG) to make it, but most of us prefer Junit.
So we can wait for Junit to support that functionality.
Anyway, that is a huge and hard task. :-(
2009/4/9 Alexei Fedotov <al...@gmail.com>:
> Sean, thanks.
> I think, this is a great step. BTW, I think it makes sense to separate
> implementation independent tests (if any) into a separate bundle. This may
> be a hard task though.
>
> Thanks.
>
>
> On Thu, Apr 9, 2009 at 12:25 PM, Sean Qiu <se...@gmail.com> wrote:
>
>> I guess HDK could pick up it from classlib.
>> So both of them could make use of it.
>>
>> What do you think about it?
>>
>> 2009/4/9 Mark Hindess <ma...@googlemail.com>:
>> >
>> > In message <94...@mail.gmail.com>,
>> Sean
>> > Qiu writes:
>> >>
>> >> 2009/4/9 Alexey Varlamov <al...@gmail.com>:
>> >> > Thanks for doing this work Sean, it's a long-expected move I believe.
>> >> >
>> >>
>> >> Yes, I'll do it by modules.
>> >>
>> >> > Just a minor suggestion: it seems "setting.properties" is in fact
>> >> > "test.properties", let's name it accordingly?
>> >>
>> >> Sure, thanks for reminding.
>> >>
>> >> > Please go ahead with commit anyway.
>> >>
>> >> Great. :-)
>> >
>> > +1
>> >
>> > You mention creating a new artifact to store the tests but I believe the
>> > intention has always been that the current hdk artifact should contain
>> > the test jars.
>> >
>> > Regards,
>> > Mark.
>> >
>> >
>> >
>>
>>
>>
>> --
>> Best Regards
>> Sean, Xiao Xia Qiu
>>
>
>
>
> --
> With best regards / с наилучшими пожеланиями,
> Alexei Fedotov / Алексей Федотов,
> http://www.telecom-express.ru/
> http://people.apache.org/~aaf/
> http://harmony.apache.org/
> http://code.google.com/p/openmeetings/
>
--
Best Regards
Sean, Xiao Xia Qiu
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Mark Hindess <ma...@googlemail.com>.
In message <c3...@mail.gmail.com>,
Alexei Fedotov writes:
>
> Sean, thanks.
> I think, this is a great step. BTW, I think it makes sense to separate
> implementation independent tests (if any) into a separate bundle.
> This may be a hard task though.
Indeed. I thought about this and did a few quick grep's of the tests to see
how difficult it would be. Let's just say I think it is best if Sean doesn't
get distracted by looking at this problem. ;-)
My feeling was that the approach taken by some of the early patches on
JIRA was reasonable. In essence:
1) the compile tests targets in the modules should be extended to create
jar files in the classlib/deploy/build directory
2) the run-tests targets should be modified to run the tests using the
jars as (boot)classpath entries rather than the directories we currently
use
The number of jar files associated with a module would depend on
the current classification of tests which is based on the use of
subdirectories.
The next step might be to create a file in the hdk
classlib/deploy/build/ ant/test.xml that by default runs just the api
tests but with options to run all the tests that could be executed using
for example:
PATH=/test/jre/bin:$PATH ant -f $HDK/build/ant/test.xml
(Somewhat like the ant file for compiling native code that I created[0]).
Making this work for non-harmony JVMs would be a final big step.
Regards,
Mark.
[0] http://svn.apache.org/viewvc?view=rev&revision=667003
> On Thu, Apr 9, 2009 at 12:25 PM, Sean Qiu <se...@gmail.com> wrote:
>
> > I guess HDK could pick up it from classlib.
> > So both of them could make use of it.
> >
> > What do you think about it?
> >
> > 2009/4/9 Mark Hindess <ma...@googlemail.com>:
> > >
> > > In message <94d710af0904082155g176d8abds8a6a725378d5d9ed@mail.gmail.com=
> >,
> > Sean
> > > Qiu writes:
> > >>
> > >> 2009/4/9 Alexey Varlamov <al...@gmail.com>:
> > >> > Thanks for doing this work Sean, it's a long-expected move I believe=
> .
> > >> >
> > >>
> > >> Yes, I'll do it by modules.
> > >>
> > >> > Just a minor suggestion: it seems "setting.properties" is in fact
> > >> > "test.properties", let's name it accordingly?
> > >>
> > >> Sure, thanks for reminding.
> > >>
> > >> > Please go ahead with commit anyway.
> > >>
> > >> Great. :-)
> > >
> > > +1
> > >
> > > You mention creating a new artifact to store the tests but I believe th=
> e
> > > intention has always been that the current hdk artifact should contain
> > > the test jars.
> > >
> > > Regards,
> > > Mark.
> > >
> > >
> > >
> >
> >
> >
> > --
> > Best Regards
> > Sean, Xiao Xia Qiu
> >
>
>
>
> --=20
> With best regards / =D3 =CE=C1=C9=CC=D5=DE=DB=C9=CD=C9 =D0=CF=D6=C5=CC=C1=
> =CE=C9=D1=CD=C9,
> Alexei Fedotov / =E1=CC=C5=CB=D3=C5=CA =E6=C5=C4=CF=D4=CF=D7,
> http://www.telecom-express.ru/
> http://people.apache.org/~aaf/
> http://harmony.apache.org/
> http://code.google.com/p/openmeetings/
>
> --0016e6dd966f34f3eb04671b0f5a--
>
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Alexei Fedotov <al...@gmail.com>.
Sean, thanks.
I think, this is a great step. BTW, I think it makes sense to separate
implementation independent tests (if any) into a separate bundle. This may
be a hard task though.
Thanks.
On Thu, Apr 9, 2009 at 12:25 PM, Sean Qiu <se...@gmail.com> wrote:
> I guess HDK could pick up it from classlib.
> So both of them could make use of it.
>
> What do you think about it?
>
> 2009/4/9 Mark Hindess <ma...@googlemail.com>:
> >
> > In message <94...@mail.gmail.com>,
> Sean
> > Qiu writes:
> >>
> >> 2009/4/9 Alexey Varlamov <al...@gmail.com>:
> >> > Thanks for doing this work Sean, it's a long-expected move I believe.
> >> >
> >>
> >> Yes, I'll do it by modules.
> >>
> >> > Just a minor suggestion: it seems "setting.properties" is in fact
> >> > "test.properties", let's name it accordingly?
> >>
> >> Sure, thanks for reminding.
> >>
> >> > Please go ahead with commit anyway.
> >>
> >> Great. :-)
> >
> > +1
> >
> > You mention creating a new artifact to store the tests but I believe the
> > intention has always been that the current hdk artifact should contain
> > the test jars.
> >
> > Regards,
> > Mark.
> >
> >
> >
>
>
>
> --
> Best Regards
> Sean, Xiao Xia Qiu
>
--
With best regards / с наилучшими пожеланиями,
Alexei Fedotov / Алексей Федотов,
http://www.telecom-express.ru/
http://people.apache.org/~aaf/
http://harmony.apache.org/
http://code.google.com/p/openmeetings/
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Sean Qiu <se...@gmail.com>.
I guess HDK could pick up it from classlib.
So both of them could make use of it.
What do you think about it?
2009/4/9 Mark Hindess <ma...@googlemail.com>:
>
> In message <94...@mail.gmail.com>, Sean
> Qiu writes:
>>
>> 2009/4/9 Alexey Varlamov <al...@gmail.com>:
>> > Thanks for doing this work Sean, it's a long-expected move I believe.
>> >
>>
>> Yes, I'll do it by modules.
>>
>> > Just a minor suggestion: it seems "setting.properties" is in fact
>> > "test.properties", let's name it accordingly?
>>
>> Sure, thanks for reminding.
>>
>> > Please go ahead with commit anyway.
>>
>> Great. :-)
>
> +1
>
> You mention creating a new artifact to store the tests but I believe the
> intention has always been that the current hdk artifact should contain
> the test jars.
>
> Regards,
> Mark.
>
>
>
--
Best Regards
Sean, Xiao Xia Qiu
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Mark Hindess <ma...@googlemail.com>.
In message <94...@mail.gmail.com>, Sean
Qiu writes:
>
> 2009/4/9 Alexey Varlamov <al...@gmail.com>:
> > Thanks for doing this work Sean, it's a long-expected move I believe.
> >
>
> Yes, I'll do it by modules.
>
> > Just a minor suggestion: it seems "setting.properties" is in fact
> > "test.properties", let's name it accordingly?
>
> Sure, thanks for reminding.
>
> > Please go ahead with commit anyway.
>
> Great. :-)
+1
You mention creating a new artifact to store the tests but I believe the
intention has always been that the current hdk artifact should contain
the test jars.
Regards,
Mark.
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Sean Qiu <se...@gmail.com>.
2009/4/9 Alexey Varlamov <al...@gmail.com>:
> Thanks for doing this work Sean, it's a long-expected move I believe.
>
Yes, I'll do it by modules.
> Just a minor suggestion: it seems "setting.properties" is in fact
> "test.properties", let's name it accordingly?
Sure, thanks for reminding.
> Please go ahead with commit anyway.
Great. :-)
>
> --
> Alexey
>
> 2009/4/9 Sean Qiu <se...@gmail.com>:
>> If no one objects, I will start to commit relevant patches.
>>
>> 2009/3/10 Tony Wu <wu...@gmail.com>:
>>> cool. that's Harmony compatibility kit ;-)
>>>
>>> On Tue, Mar 10, 2009 at 2:43 PM, Xiao-Feng Li <xi...@gmail.com> wrote:
>>>> Good suggestion!
>>>>
>>>> -xiaofeng
>>>>
>>>> On Fri, Mar 6, 2009 at 3:44 PM, Sean Qiu <se...@gmail.com> wrote:
>>>>> Hi, All
>>>>>
>>>>> I'm trying to archive our tests into some jars so that user can run the
>>>>> tests directly as long as they get a copy of our run-time.( like
>>>>> Harmony-Automated-Tests-M8.zip)
>>>>> By this means, we can create a testing archive for each module as
>>>>> well, luni-test.zip, security-test.zip......
>>>>> I found we have made some efforts to archive our unit test into one bundle.
>>>>> [1]
>>>>> Now I plan to supply some patch for it. I've uploaded my completed patch to
>>>>> HARMONY-6083[2].
>>>>> (I've assigned this JIRA a port of HARMONY-984).
>>>>> Below is my ongoing proposal.
>>>>>
>>>>> trunk
>>>>> |-- make | |-- run-test.xml * This ant build file
>>>>> will be used to run tests after archiving (or any other names)
>>>>> | |-- setting.properties Customer can setting parameters by
>>>>> this properties file, such as ${test.jre.home}
>>>>> |
>>>>> |-- modules | |-- luni
>>>>> | | |-- build.xml * Add a new task which will
>>>>> package all luni tests to deploy/build/test/luni
>>>>> | |
>>>>> | |-- .... (other module)
>>>>> |-- ...
>>>>> |
>>>>> |-- deploy/build/test (output)
>>>>> |-- properties.xml Copy from
>>>>> <trunk>/make/properties.xml, some common tasks
>>>>> |-- setting.properties Copy from
>>>>> <trunk>/make/setting.properties, some configuration properties for testing
>>>>> |-- support.jar, derby.jar... Dependencies
>>>>> jars will be used while testing
>>>>> |-- build.xml Copy from
>>>>> <trunk>/make/run-test.xml
>>>>> |-- luni
>>>>> | |-- resources Copy from
>>>>> <trunk>/modules/luni/src/test/resources, may copy some support files
>>>>> here,such as policy file in luni.
>>>>> | |-- excludes Copy
>>>>> from <trunk>/modules/luni/make/exclude.*, user can exclude tests by this
>>>>> means.
>>>>> | |-- luni_tests_impl.jar Tesing
>>>>> archive
>>>>> | |-- luni_tests_api.jar Testing
>>>>> archive.
>>>>> |
>>>>> |-- security ...
>>>>> |-- ... (other module)
>>>>>
>>>>>
>>>>> Then we can archive whole test folder into one file for user.
>>>>> User can test our milestone in addition to this file, there is no need to
>>>>> checkout all src, building, testing....
>>>>>
>>>>> I'm successfully run the our luni test by this means.
>>>>> But there is still some extra work to refine the script.
>>>>> (Your help is appreciated very much.)
>>>>>
>>>>> What do you think about it?
>>>>> Any suggestions or commends are welcomed.
>>>>>
>>>>> [1] https://issues.apache.org/jira/browse/HARMONY-984
>>>>> [2] https://issues.apache.org/jira/browse/HARMONY-6083
>>>>>
>>>>> --
>>>>> Best Regards
>>>>> Sean, Xiao Xia Qiu
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Managed Runtime Technology Center, Intel
>>>>
>>>
>>>
>>>
>>> --
>>> Tony Wu
>>> China Software Development Lab, IBM
>>>
>>
>>
>>
>> --
>> Best Regards
>> Sean, Xiao Xia Qiu
>>
>
--
Best Regards
Sean, Xiao Xia Qiu
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Alexey Varlamov <al...@gmail.com>.
Thanks for doing this work Sean, it's a long-expected move I believe.
Just a minor suggestion: it seems "setting.properties" is in fact
"test.properties", let's name it accordingly?
Please go ahead with commit anyway.
--
Alexey
2009/4/9 Sean Qiu <se...@gmail.com>:
> If no one objects, I will start to commit relevant patches.
>
> 2009/3/10 Tony Wu <wu...@gmail.com>:
>> cool. that's Harmony compatibility kit ;-)
>>
>> On Tue, Mar 10, 2009 at 2:43 PM, Xiao-Feng Li <xi...@gmail.com> wrote:
>>> Good suggestion!
>>>
>>> -xiaofeng
>>>
>>> On Fri, Mar 6, 2009 at 3:44 PM, Sean Qiu <se...@gmail.com> wrote:
>>>> Hi, All
>>>>
>>>> I'm trying to archive our tests into some jars so that user can run the
>>>> tests directly as long as they get a copy of our run-time.( like
>>>> Harmony-Automated-Tests-M8.zip)
>>>> By this means, we can create a testing archive for each module as
>>>> well, luni-test.zip, security-test.zip......
>>>> I found we have made some efforts to archive our unit test into one bundle.
>>>> [1]
>>>> Now I plan to supply some patch for it. I've uploaded my completed patch to
>>>> HARMONY-6083[2].
>>>> (I've assigned this JIRA a port of HARMONY-984).
>>>> Below is my ongoing proposal.
>>>>
>>>> trunk
>>>> |-- make | |-- run-test.xml * This ant build file
>>>> will be used to run tests after archiving (or any other names)
>>>> | |-- setting.properties Customer can setting parameters by
>>>> this properties file, such as ${test.jre.home}
>>>> |
>>>> |-- modules | |-- luni
>>>> | | |-- build.xml * Add a new task which will
>>>> package all luni tests to deploy/build/test/luni
>>>> | |
>>>> | |-- .... (other module)
>>>> |-- ...
>>>> |
>>>> |-- deploy/build/test (output)
>>>> |-- properties.xml Copy from
>>>> <trunk>/make/properties.xml, some common tasks
>>>> |-- setting.properties Copy from
>>>> <trunk>/make/setting.properties, some configuration properties for testing
>>>> |-- support.jar, derby.jar... Dependencies
>>>> jars will be used while testing
>>>> |-- build.xml Copy from
>>>> <trunk>/make/run-test.xml
>>>> |-- luni
>>>> | |-- resources Copy from
>>>> <trunk>/modules/luni/src/test/resources, may copy some support files
>>>> here,such as policy file in luni.
>>>> | |-- excludes Copy
>>>> from <trunk>/modules/luni/make/exclude.*, user can exclude tests by this
>>>> means.
>>>> | |-- luni_tests_impl.jar Tesing
>>>> archive
>>>> | |-- luni_tests_api.jar Testing
>>>> archive.
>>>> |
>>>> |-- security ...
>>>> |-- ... (other module)
>>>>
>>>>
>>>> Then we can archive whole test folder into one file for user.
>>>> User can test our milestone in addition to this file, there is no need to
>>>> checkout all src, building, testing....
>>>>
>>>> I'm successfully run the our luni test by this means.
>>>> But there is still some extra work to refine the script.
>>>> (Your help is appreciated very much.)
>>>>
>>>> What do you think about it?
>>>> Any suggestions or commends are welcomed.
>>>>
>>>> [1] https://issues.apache.org/jira/browse/HARMONY-984
>>>> [2] https://issues.apache.org/jira/browse/HARMONY-6083
>>>>
>>>> --
>>>> Best Regards
>>>> Sean, Xiao Xia Qiu
>>>>
>>>
>>>
>>>
>>> --
>>> Managed Runtime Technology Center, Intel
>>>
>>
>>
>>
>> --
>> Tony Wu
>> China Software Development Lab, IBM
>>
>
>
>
> --
> Best Regards
> Sean, Xiao Xia Qiu
>
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Sean Qiu <se...@gmail.com>.
If no one objects, I will start to commit relevant patches.
2009/3/10 Tony Wu <wu...@gmail.com>:
> cool. that's Harmony compatibility kit ;-)
>
> On Tue, Mar 10, 2009 at 2:43 PM, Xiao-Feng Li <xi...@gmail.com> wrote:
>> Good suggestion!
>>
>> -xiaofeng
>>
>> On Fri, Mar 6, 2009 at 3:44 PM, Sean Qiu <se...@gmail.com> wrote:
>>> Hi, All
>>>
>>> I'm trying to archive our tests into some jars so that user can run the
>>> tests directly as long as they get a copy of our run-time.( like
>>> Harmony-Automated-Tests-M8.zip)
>>> By this means, we can create a testing archive for each module as
>>> well, luni-test.zip, security-test.zip......
>>> I found we have made some efforts to archive our unit test into one bundle.
>>> [1]
>>> Now I plan to supply some patch for it. I've uploaded my completed patch to
>>> HARMONY-6083[2].
>>> (I've assigned this JIRA a port of HARMONY-984).
>>> Below is my ongoing proposal.
>>>
>>> trunk
>>> |-- make | |-- run-test.xml * This ant build file
>>> will be used to run tests after archiving (or any other names)
>>> | |-- setting.properties Customer can setting parameters by
>>> this properties file, such as ${test.jre.home}
>>> |
>>> |-- modules | |-- luni
>>> | | |-- build.xml * Add a new task which will
>>> package all luni tests to deploy/build/test/luni
>>> | |
>>> | |-- .... (other module)
>>> |-- ...
>>> |
>>> |-- deploy/build/test (output)
>>> |-- properties.xml Copy from
>>> <trunk>/make/properties.xml, some common tasks
>>> |-- setting.properties Copy from
>>> <trunk>/make/setting.properties, some configuration properties for testing
>>> |-- support.jar, derby.jar... Dependencies
>>> jars will be used while testing
>>> |-- build.xml Copy from
>>> <trunk>/make/run-test.xml
>>> |-- luni
>>> | |-- resources Copy from
>>> <trunk>/modules/luni/src/test/resources, may copy some support files
>>> here,such as policy file in luni.
>>> | |-- excludes Copy
>>> from <trunk>/modules/luni/make/exclude.*, user can exclude tests by this
>>> means.
>>> | |-- luni_tests_impl.jar Tesing
>>> archive
>>> | |-- luni_tests_api.jar Testing
>>> archive.
>>> |
>>> |-- security ...
>>> |-- ... (other module)
>>>
>>>
>>> Then we can archive whole test folder into one file for user.
>>> User can test our milestone in addition to this file, there is no need to
>>> checkout all src, building, testing....
>>>
>>> I'm successfully run the our luni test by this means.
>>> But there is still some extra work to refine the script.
>>> (Your help is appreciated very much.)
>>>
>>> What do you think about it?
>>> Any suggestions or commends are welcomed.
>>>
>>> [1] https://issues.apache.org/jira/browse/HARMONY-984
>>> [2] https://issues.apache.org/jira/browse/HARMONY-6083
>>>
>>> --
>>> Best Regards
>>> Sean, Xiao Xia Qiu
>>>
>>
>>
>>
>> --
>> Managed Runtime Technology Center, Intel
>>
>
>
>
> --
> Tony Wu
> China Software Development Lab, IBM
>
--
Best Regards
Sean, Xiao Xia Qiu
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Tony Wu <wu...@gmail.com>.
cool. that's Harmony compatibility kit ;-)
On Tue, Mar 10, 2009 at 2:43 PM, Xiao-Feng Li <xi...@gmail.com> wrote:
> Good suggestion!
>
> -xiaofeng
>
> On Fri, Mar 6, 2009 at 3:44 PM, Sean Qiu <se...@gmail.com> wrote:
>> Hi, All
>>
>> I'm trying to archive our tests into some jars so that user can run the
>> tests directly as long as they get a copy of our run-time.( like
>> Harmony-Automated-Tests-M8.zip)
>> By this means, we can create a testing archive for each module as
>> well, luni-test.zip, security-test.zip......
>> I found we have made some efforts to archive our unit test into one bundle.
>> [1]
>> Now I plan to supply some patch for it. I've uploaded my completed patch to
>> HARMONY-6083[2].
>> (I've assigned this JIRA a port of HARMONY-984).
>> Below is my ongoing proposal.
>>
>> trunk
>> |-- make | |-- run-test.xml * This ant build file
>> will be used to run tests after archiving (or any other names)
>> | |-- setting.properties Customer can setting parameters by
>> this properties file, such as ${test.jre.home}
>> |
>> |-- modules | |-- luni
>> | | |-- build.xml * Add a new task which will
>> package all luni tests to deploy/build/test/luni
>> | |
>> | |-- .... (other module)
>> |-- ...
>> |
>> |-- deploy/build/test (output)
>> |-- properties.xml Copy from
>> <trunk>/make/properties.xml, some common tasks
>> |-- setting.properties Copy from
>> <trunk>/make/setting.properties, some configuration properties for testing
>> |-- support.jar, derby.jar... Dependencies
>> jars will be used while testing
>> |-- build.xml Copy from
>> <trunk>/make/run-test.xml
>> |-- luni
>> | |-- resources Copy from
>> <trunk>/modules/luni/src/test/resources, may copy some support files
>> here,such as policy file in luni.
>> | |-- excludes Copy
>> from <trunk>/modules/luni/make/exclude.*, user can exclude tests by this
>> means.
>> | |-- luni_tests_impl.jar Tesing
>> archive
>> | |-- luni_tests_api.jar Testing
>> archive.
>> |
>> |-- security ...
>> |-- ... (other module)
>>
>>
>> Then we can archive whole test folder into one file for user.
>> User can test our milestone in addition to this file, there is no need to
>> checkout all src, building, testing....
>>
>> I'm successfully run the our luni test by this means.
>> But there is still some extra work to refine the script.
>> (Your help is appreciated very much.)
>>
>> What do you think about it?
>> Any suggestions or commends are welcomed.
>>
>> [1] https://issues.apache.org/jira/browse/HARMONY-984
>> [2] https://issues.apache.org/jira/browse/HARMONY-6083
>>
>> --
>> Best Regards
>> Sean, Xiao Xia Qiu
>>
>
>
>
> --
> Managed Runtime Technology Center, Intel
>
--
Tony Wu
China Software Development Lab, IBM
Re: [testing] Proposal for archiving our tests into one bundle
Posted by Xiao-Feng Li <xi...@gmail.com>.
Good suggestion!
-xiaofeng
On Fri, Mar 6, 2009 at 3:44 PM, Sean Qiu <se...@gmail.com> wrote:
> Hi, All
>
> I'm trying to archive our tests into some jars so that user can run the
> tests directly as long as they get a copy of our run-time.( like
> Harmony-Automated-Tests-M8.zip)
> By this means, we can create a testing archive for each module as
> well, luni-test.zip, security-test.zip......
> I found we have made some efforts to archive our unit test into one bundle.
> [1]
> Now I plan to supply some patch for it. I've uploaded my completed patch to
> HARMONY-6083[2].
> (I've assigned this JIRA a port of HARMONY-984).
> Below is my ongoing proposal.
>
> trunk
> |-- make | |-- run-test.xml * This ant build file
> will be used to run tests after archiving (or any other names)
> | |-- setting.properties Customer can setting parameters by
> this properties file, such as ${test.jre.home}
> |
> |-- modules | |-- luni
> | | |-- build.xml * Add a new task which will
> package all luni tests to deploy/build/test/luni
> | |
> | |-- .... (other module)
> |-- ...
> |
> |-- deploy/build/test (output)
> |-- properties.xml Copy from
> <trunk>/make/properties.xml, some common tasks
> |-- setting.properties Copy from
> <trunk>/make/setting.properties, some configuration properties for testing
> |-- support.jar, derby.jar... Dependencies
> jars will be used while testing
> |-- build.xml Copy from
> <trunk>/make/run-test.xml
> |-- luni
> | |-- resources Copy from
> <trunk>/modules/luni/src/test/resources, may copy some support files
> here,such as policy file in luni.
> | |-- excludes Copy
> from <trunk>/modules/luni/make/exclude.*, user can exclude tests by this
> means.
> | |-- luni_tests_impl.jar Tesing
> archive
> | |-- luni_tests_api.jar Testing
> archive.
> |
> |-- security ...
> |-- ... (other module)
>
>
> Then we can archive whole test folder into one file for user.
> User can test our milestone in addition to this file, there is no need to
> checkout all src, building, testing....
>
> I'm successfully run the our luni test by this means.
> But there is still some extra work to refine the script.
> (Your help is appreciated very much.)
>
> What do you think about it?
> Any suggestions or commends are welcomed.
>
> [1] https://issues.apache.org/jira/browse/HARMONY-984
> [2] https://issues.apache.org/jira/browse/HARMONY-6083
>
> --
> Best Regards
> Sean, Xiao Xia Qiu
>
--
Managed Runtime Technology Center, Intel