Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338133 - Import tests DNF when importing from repository
Summary: Import tests DNF when importing from repository
Status: RESOLVED FIXED
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: 3.7 M6   Edit
Assignee: Curtis Windatt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-24 13:19 EST by Curtis Windatt CLA
Modified: 2011-02-24 17:45 EST (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Curtis Windatt CLA 2011-02-24 13:19:02 EST 
N20110222 and later.

Test failures in the nightly builds fail with a DNF.  Kim told me that a CVS dialog is opening up during our import from repository tests, asking for a username and password for the pserver repo.
Comment 1 Curtis Windatt CLA 2011-02-24 13:29:12 EST 
I expect that we will have to programmatically set the CVS login information in the test.

I had to run the tests in a non-UI thread to reproduce locally.

Tomasz is there API the test can use to set up the CVS repo with login data ahead of time?  Or is there another way of surpressing the dialog?
Comment 2 Curtis Windatt CLA 2011-02-24 14:37:18 EST 
Tomasz, Kim, do any of the Team tests actually download things from remote CVS repositories?  Do any tests access remote resources?

I'm not sure if we should even have tests that can't pass without internet access and could potentially be very slow.
Comment 3 Kim Moir CLA 2011-02-24 16:29:19 EST 
The are many tests that access remote resources
1) SWT browser
2) p2 upgrade scenarios
3) team cvs tests

In fact the test bundles for the test runs themselves are installed via the p2 director from the current build's remote p2 repository. So it's not anything to worry about :-)
Comment 4 Curtis Windatt CLA 2011-02-24 17:45:27 EST 
I have put a fix into HEAD.  See ImportFromRepoTestCase and the test plug-in's manifest.  The test will now use some code copied from the CVS tests to set up the cvs location before running the import.