| Summary: | Use smaller repository for SynchronizeViewTest | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Benjamin Muskalla <b.muskalla> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | dariusz.luksza, matthias.sohn, stefan.lay |
| Version: | 0.9.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Benjamin Muskalla
We should use the same local repository which is used for the clone test. In commit e29cc2a4a20e94eda3ea902da3e1894846860813 Matthias introduced a repo which "is now generated, has a much smaller size and its daemon is run as part of the test harness to speedup the UI tests and make them independent from external resources." Take a look at GitCloneWizardTest and SampleTestRepository how I did that for the clone tests. Since changing them to use locally generated repository we never had any problems with these tests anymore. Couldn't you instead of cloning generate a test repo programmatically ? Have a look at GitRepositoriesViewTestBase and its abstract base class LocalRepositoryTestCase I've rewrite SynchronizeViewTest, now it is based on LocalRepositoryTestCase, here is patch for this: http://egit.eclipse.org/r/#change,1677 merged as 57b2c2f4d67f307ff32af541ca7a5ca1b4b97e22 |