Community
Participate
Working Groups
Some states, especially failure states, are tedious to reproduce and occur seldomly in daily work. Therefore, we should have UI regression tests, preferably implemented in SWTBot.
+1
@Matthias, I have a running UI test for the FeatureRebaseHandler, but I need a lot of code from o.e.egit.ui.test. Since it is a fragment, I cannot simply import it. Would it make sense to refactor this and move the code into a new bundle: o.e.egit.common.ui.test? Otherwise, I have to either duplicate several hundred lines of code, or re-invent most of it. Important classes are: - LocalRepositoryTestCase - TestUtil - JobJoiner (I believe this could be removed with SWTBot 2.3.0)
I wouldn't mind if you simply add the gitflow ui tests to the existing org.eclipse.egit.ui.test bundle if this reduces the overhead to implement them I think we should try to update to swtbot 2.3.0 (in another change)
https://git.eclipse.org/r/#/c/51157/
The above patch-set should be merged before the feature rebase fix [1] because it tests the old behaviour. I then have to amend that patch-set to test the new behaviour. [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=470434
Thanks to this tests I found two issues in egit and gitflow code, see https://git.eclipse.org/r/51379 & https://git.eclipse.org/r/51380.
Great! Thanks for fixing this.
Merged with http://git.eclipse.org/c/egit/egit.git/commit/?id=d46e03b5cd2828d4a84153e0537d761f7f7fbc40