Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341907 - activate tests on hudson build
Summary: activate tests on hudson build
Status: RESOLVED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: tooling (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Steffen Pingel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 368890
  Show dependency tree
 
Reported: 2011-04-05 09:49 EDT by Martin Lippert CLA
Modified: 2012-01-17 17:39 EST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Lippert CLA 2011-04-05 09:49:00 EDT
There are a few unit tests contributed within the virgo tooling bundles. We should activate them for the hudson build (and maybe stabilize + fix before)
Comment 1 Miles Parker CLA 2012-01-11 18:41:13 EST
I've been able to run all of the tests locally successfully except for the SWTBot tests, which are always problematic and may or may not be necessary. Would be good to get this automated before doing any major refactorings, and things have a tendancy to show up on automated build that don't show up locally. I see that the other virgo builds are under testing but I don't know if this is a matter of flipping a switch or something more complicated. Is the person handling virgo hudson builds cc'd on this?
Comment 2 Glyn Normington CLA 2012-01-12 03:35:35 EST
Martin, who raised this bug, handles the Virgo IDE Hudson job.
Comment 3 Martin Lippert CLA 2012-01-12 05:58:13 EST
Please ask Steffen for help with configuring the tests for the hudson build.
Comment 4 Steffen Pingel CLA 2012-01-12 12:31:25 EST
I have fixed the Tycho test configuration and made the following changes:

* Tests in org.eclipse.virgo.ide.export.tests and org.eclipse.virgo.ide.tests are now based on JUnit4
* All classes with SWTbot dependencies were moved to org.eclipse.virgo.ide.ui.tests
* Constraints that prevented compiling the tooling against the latest version of Spring were removed

The next time the Hudson build job runs it should execute tests. Miles, am assuming that you (or Leo) will take over ownership of builds at this point.
Comment 5 Miles Parker CLA 2012-01-12 13:17:35 EST
Hi Steffen,

Thanks! I'm going to need to get access rights for the Hudson job. I'm assuming that should properly wait for committer rights, but if that isn't the case then perhaps someone could grant them. I'm "mparker".

It looks like the current build is stalled out:

https://hudson.eclipse.org/hudson/job/virgo.ide.snapshot/257/console

at:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running org.eclipse.virgo.ide.export.tests.BundleExportTestCase

So I think the next order of business will be to kill that job. :)
Comment 6 Glyn Normington CLA 2012-01-13 05:14:02 EST
(In reply to comment #5)
> I'm going to need to get access rights for the Hudson job. I'm assuming
> that should properly wait for committer rights, but if that isn't the case then
> perhaps someone could grant them. I'm "mparker".

I was able to grant you those rights without you being a committer. With great power comes great responsibility. ;-)