[jira] Updated: (HARMONY-5000) [buildtest][eut] need to run suites one by one

["Vladimir Beliaev (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HARMONY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Beliaev updated HARMONY-5000:
--------------------------------------

    Attachment: 02-H5000.patch
                01-H5000.sh

Here is the patch. In short its idea is:

1. "summary-reporter" is renamed to "utils", because a new utility class has been added

2.  build.xml extracts the list of suites from eclipse-testing/test.xml with the simple SAX parser. This list is stored to eclipse-testing/eut.suites.run.properties file defining "tests.list" property.

3. build.xml runs the EUT suites one by one where the suites are defined with "tests" property (as previsoly, the "," separator must be used) or extracted from eclipse-testing/test.xml (if "tests" is undefined or empty).

The changes relate to this 3 steps, I hope most of them I either readable or well commented.

Thanks
Vladimir Beliaev

> [buildtest][eut] need to run suites one by one
> ----------------------------------------------
>
>                 Key: HARMONY-5000
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5000
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: build - test - ci
>         Environment: any
>            Reporter: Vladimir Beliaev
>         Attachments: 01-H5000.sh, 02-H5000.patch
>
>
> This corresponds to task #4 in the root JIRA. I.e:
> M3 issues with intermittent suite crashes on Linux (which are not reproducible while running suite as stand along unit) indicates it worth redoing EUT Suites running process to run them one by one, not with the help of single running. 
> I'm not yet sure what way this can be done taking into account the way must be universal for both EUT3.2 and EUT3.3.
> One of the options is to run particular testcase for the plugin with the command like:
>    <harmony java> \ 
>       -data workspace \
>       ...
>      -testpluginname org.eclipse.jdt.core.tests.model \
>      -classname org.eclipse.jdt.core.tests.dom.RunAllTests 
> The list of parameters may be taken from tests/eut/config/eut*.suites.properties file (like what plugin the suite belong too and if this suite requires uitestapplication or coretestapplication).
> Another option is to run particular suite by its name (like "jdtdebug" suite). It is closer to existing one. Still it is not clear what way the list of suites can be obtained (normally it is harcoded in unpacked eclipse-testing/test.xml file).
> Thanks
> Vladimir

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.