You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Molotkov (JIRA)" <ji...@apache.org> on 2007/01/16 14:08:27 UTC

[jira] Created: (HARMONY-3012) [buildtest][cc] jEdit4.2 Automated GUI test suite with CC integration config

[buildtest][cc] jEdit4.2 Automated GUI test suite with CC integration config
----------------------------------------------------------------------------

                 Key: HARMONY-3012
                 URL: https://issues.apache.org/jira/browse/HARMONY-3012
             Project: Harmony
          Issue Type: New Feature
          Components: build - test - ci
         Environment: All
            Reporter: Vladimir Molotkov


The patch contains jEdit4.2 automated GUI tests suite.

Main purpose of these tests is to make sure that implementation
under test (Harmony's VM's primarily) is able to run jEdit application
and an user is able to perform some work in jEdit. Tests automation is
based on Abbot Java GUI test automation framework (see http://abbot.sourceforge.net).
Also the contribution includes configuration file for CruiseControl (CC)
system integration (see http://sourceforge.net/projects/cruisecontrol).

The contribution must be integrated into 'buildtest' module's trunk
(/harmony/enhanced/buildtest/trunk)

To add contribution to your copy of 'buildtest' module run the
following commands (replace placeholders <...> with your actual paths):

    cd <buildtest-trunk-dir>
    patch --strip=0 --input=<path to jedit4.2_test.patch>
    svn add jedit4.2_test

Please refer to <buildtest-trunk-dir>/jedit4.2_test/readme.txt
for build/tests-run and CC integration details.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (HARMONY-3012) [buildtest][cc] jEdit4.2 Automated GUI test suite with CC integration config

Posted by "Vladimir Molotkov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Molotkov updated HARMONY-3012:
---------------------------------------

    Attachment: jedit4.2_test.patch

> [buildtest][cc] jEdit4.2 Automated GUI test suite with CC integration config
> ----------------------------------------------------------------------------
>
>                 Key: HARMONY-3012
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3012
>             Project: Harmony
>          Issue Type: New Feature
>          Components: build - test - ci
>         Environment: All
>            Reporter: Vladimir Molotkov
>         Attachments: jedit4.2_test.patch
>
>
> The patch contains jEdit4.2 automated GUI tests suite.
> Main purpose of these tests is to make sure that implementation
> under test (Harmony's VM's primarily) is able to run jEdit application
> and an user is able to perform some work in jEdit. Tests automation is
> based on Abbot Java GUI test automation framework (see http://abbot.sourceforge.net).
> Also the contribution includes configuration file for CruiseControl (CC)
> system integration (see http://sourceforge.net/projects/cruisecontrol).
> The contribution must be integrated into 'buildtest' module's trunk
> (/harmony/enhanced/buildtest/trunk)
> To add contribution to your copy of 'buildtest' module run the
> following commands (replace placeholders <...> with your actual paths):
>     cd <buildtest-trunk-dir>
>     patch --strip=0 --input=<path to jedit4.2_test.patch>
>     svn add jedit4.2_test
> Please refer to <buildtest-trunk-dir>/jedit4.2_test/readme.txt
> for build/tests-run and CC integration details.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (HARMONY-3012) [buildtest][cc] jEdit4.2 Automated GUI test suite with CC integration config

Posted by "Vladimir Molotkov (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Molotkov closed HARMONY-3012.
--------------------------------------

    Resolution: Won't Fix

This issue was absoleted by http://issues.apache.org/jira/browse/HARMONY-3633

> [buildtest][cc] jEdit4.2 Automated GUI test suite with CC integration config
> ----------------------------------------------------------------------------
>
>                 Key: HARMONY-3012
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3012
>             Project: Harmony
>          Issue Type: New Feature
>          Components: build - test - ci
>         Environment: All
>            Reporter: Vladimir Molotkov
>         Attachments: jedit4.2_test.patch
>
>
> The patch contains jEdit4.2 automated GUI tests suite.
> Main purpose of these tests is to make sure that implementation
> under test (Harmony's VM's primarily) is able to run jEdit application
> and an user is able to perform some work in jEdit. Tests automation is
> based on Abbot Java GUI test automation framework (see http://abbot.sourceforge.net).
> Also the contribution includes configuration file for CruiseControl (CC)
> system integration (see http://sourceforge.net/projects/cruisecontrol).
> The contribution must be integrated into 'buildtest' module's trunk
> (/harmony/enhanced/buildtest/trunk)
> To add contribution to your copy of 'buildtest' module run the
> following commands (replace placeholders <...> with your actual paths):
>     cd <buildtest-trunk-dir>
>     patch --strip=0 --input=<path to jedit4.2_test.patch>
>     svn add jedit4.2_test
> Please refer to <buildtest-trunk-dir>/jedit4.2_test/readme.txt
> for build/tests-run and CC integration details.

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