Community
Participate
Working Groups
We have to add tests to check creating/applying patches using appropriate patch dialogs. It seems that our current tests check only API, however as we noticed during some recent NBuilds this is not enough.
See bug 270131 for the case to cover in the tests.
Created attachment 131127 [details] Patch_v01 Test for applying a patch using the wizard.
Created attachment 131136 [details] Patch_v02 I added a test to apply a patch from the clipboard.
The test look fine. I think that UITest could be renamed to PatchUITest. AFAIK some util methods to handle UI tests will be duplicated in compare.tests, cvs.tests. I would try to create one common util class available for all team/compare tests, but this would require a new bug and further investigation during 3.6.
Created attachment 131383 [details] Patch_v03 (In reply to comment #4) > I think that UITest could be renamed to PatchUITest. > <text deleted/> Done. Also added a few minor changes.
Patch_v03 released to HEAD.
Created attachment 131386 [details] Patch_B_v01 Another test for creating a patch through a wizard.
Created attachment 131388 [details] Patch_B_v02 Patch_B with fixed concurrency issues.
Patch_B_v02 released to HEAD. Finally we have UI tests for creating/applying patches. Pawel, please verify that everything is in and mark the bug FIXED.
I've checked the HEAD and it's fine. Marking as FIXED.
Created attachment 131851 [details] Patch_B_v03 I forgot to add a folder to "bin.includes" property. This causes the tests to fail on the build machines but causes no trouble when running them from the workspace.
Patch_B_v03 released to HEAD.