[jbosstools-issues] [JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing
Pavol Srna (JIRA)
jira-events at lists.jboss.org
Thu Nov 7 09:26:03 EST 2013
[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921355#comment-12921355 ]
Pavol Srna commented on JBIDE-13869:
------------------------------------
Hi [~mickael_istria], How is this suppose to work? Our favorite use case would be to: cd to integration-test folder and execute: {code} mvn clean verify -Prun-on-installed-application -Dtycho.surefire.runtimePath=/home/psrna/jbdevstudio-7.1.0.Beta1/studio/ {code}
Then I would expect that tycho installs our integration tests to the tycho.surefire.runtimePath and run them. So basically I should see JBDS screen/UI when running the tests. Right? But I didn't see anything similar ..
> 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
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
>
> 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