| Summary: | Import tests DNF when importing from repository | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Curtis Windatt <curtis.windatt.public> |
| Component: | UI | Assignee: | Curtis Windatt <curtis.windatt.public> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | ankur_sharma, kim.moir, tomasz.zarna |
| Version: | 3.7 | ||
| Target Milestone: | 3.7 M6 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Curtis Windatt
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? 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. 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 :-) 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. |