2009/4/9 Alexey Varlamov <alexey.v.varlamov@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 <sean.xx.qiu@gmail.com>:
>> If no one objects, I will start to commit relevant patches.
>>
>> 2009/3/10 Tony Wu <wuyuehao@gmail.com>:
>>> cool. that's Harmony compatibility kit ;-)
>>>
>>> On Tue, Mar 10, 2009 at 2:43 PM, Xiao-Feng Li <xiaofeng.li@gmail.com> wrote:
>>>> Good suggestion!
>>>>
>>>> -xiaofeng
>>>>
>>>> On Fri, Mar 6, 2009 at 3:44 PM, Sean Qiu <sean.xx.qiu@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
|