[jbosstools-issues] [JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

Mickael Istria (JIRA) jira-events at lists.jboss.org
Wed Jun 12 09:21:54 EDT 2013


    [ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781172#comment-12781172 ] 

Mickael Istria commented on JBIDE-13869:
----------------------------------------

[~maxandersen]: The difficulty in that task is not to run the test. Eclipse already provides what's necessary to run tests automatically, and we do publish the tests on an update-site for "external" installation and execution.
The difficulty is more to find a simple way to define the target platform. I don't think we can/want to use directly a target definition.

What I can propose you for good efficiency/low price is the following: A CI job that takes the latest build of JBDS, install tests in it, and run some of the tests on demand (that would be a job parameter). WDYT?
                
> Find a way to run testsuite against existing builds but with different TP without requiring publishing
> ------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-13869
>                 URL: https://issues.jboss.org/browse/JBIDE-13869
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>            Reporter: Max Rydahl Andersen
>            Assignee: Mickael Istria
>            Priority: Critical
>             Fix For: 4.0.2.Final, 4.1.0.Beta2
>
>
> Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again.
> Possible options:
> 1) Create new testsuite that depends on all other testsuites and run them in surefire test. 
> 2) use something else than surefire to run the already built testsuites.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list