platform-vcm-home/2_1_testing.html
Parent Directory
| 
Revision Log
Revision 1.3 - (view) (download) (as text)
| 1 : | mvalenta | 1.1 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> |
| 2 : | <html> | ||
| 3 : | <head> | ||
| 4 : | |||
| 5 : | <link rel="stylesheet" href="http://dev.eclipse.org/default_style.css" type="text/css"> | ||
| 6 : | <title>Team Testing Roadmap</title> | ||
| 7 : | |||
| 8 : | <meta name="author" content="OTI Employee"> | ||
| 9 : | |||
| 10 : | <meta content="text/html; charset=iso-8859-1" http-equiv="Content-Type"> | ||
| 11 : | </head> | ||
| 12 : | |||
| 13 : | <body> | ||
| 14 : | |||
| 15 : | <h1>Section 1: General CVS Tests</h1> | ||
| 16 : | |||
| 17 : | <h2>CVS Repositories View</h2> | ||
| 18 : | |||
| 19 : | <h3>Adding and Discarding Locations</h3> | ||
| 20 : | These test require an existing repository which contains projects. | ||
| 21 : | <ol> | ||
| 22 : | <li>Add a location to the view.</li> | ||
| 23 : | <li>Ensure that invalid location information is handled properly in the New Location Wizard.</li> | ||
| 24 : | <li>View location properties page and ensure that information is correct and can be changed.</li> | ||
| 25 : | <li>Also change property values when local projects are shared with the location and ensure | ||
| 26 : | the project's sharing information is changed when the location's properties are changed. | ||
| 27 : | <li>Discard a location and ensure it is removed. Also ensure that discarding is not permitted when | ||
| 28 : | projects in the local workspace are shared with the location.</li> | ||
| 29 : | </ol> | ||
| 30 : | |||
| 31 : | <h3>Project Checkout</h3> | ||
| 32 : | These test require an existing repository which contains projects, at least one of which | ||
| 33 : | does not contain a .project file. Ensure that repeating each operation results in the proper overwrite prompting. | ||
| 34 : | <ol> | ||
| 35 : | <li>Perform "Checkout as Project" on a single project. Ensure that repeating results in overwrite prompt.</li> | ||
| 36 : | <li>Perform "Checkout as Project" on multiple projects.</li> | ||
| 37 : | <li>Perform "Checkout as..." on a single project (that contains a .project file) and enter custom name and/or custom location.</li> | ||
| 38 : | <li>Perform "Checkout as..." on a single remote project that does not have a .project file and | ||
| 39 : | ensure that the user is prompted for the project type to create.</li> | ||
| 40 : | <li>Perform "Checkout as..." on multipe projects and enter a custom parent location.</li> | ||
| 41 : | </ol> | ||
| 42 : | |||
| 43 : | <h3>Browsing Tags</h3> | ||
| 44 : | These test require an existing repository which contains projects that have been tagged with both | ||
| 45 : | version and branch tags. | ||
| 46 : | <h4>Refresh Branches and Versions</h4> | ||
| 47 : | <ol> | ||
| 48 : | <li>Select a repository location and perform "Refresh Branches and Versions...". | ||
| 49 : | <li>Select one or more projects that contain a .project file and have been tagged with branch and version tags and click finish.</li> | ||
| 50 : | <li>Expand the respository entry to view ... | ||
| 51 : | <ul> | ||
| 52 : | <li>projects in HEAD,</li> | ||
| 53 : | <li>branches and projects in BRANCHES,</li> | ||
| 54 : | <li>projects and versions in VERSIONS.</li> | ||
| 55 : | </ul> | ||
| 56 : | </ol> | ||
| 57 : | |||
| 58 : | <h4>Configure Branches and Versions</h4> | ||
| 59 : | <ol> | ||
| 60 : | <li>Select a project in the repositories view and perform "Configure Branches and Versions...". | ||
| 61 : | <li>Select some branch and version tags to be remembered.</li> | ||
| 62 : | <li>Expand the respository entry to view ... | ||
| 63 : | <ul> | ||
| 64 : | <li>projects in HEAD,</li> | ||
| 65 : | <li>branches and projects in BRANCHES,</li> | ||
| 66 : | <li>projects and versions in VERSIONS.</li> | ||
| 67 : | </ul> | ||
| 68 : | </ol> | ||
| 69 : | |||
| 70 : | <h3>Working with modules</h3> | ||
| 71 : | These tests require a CVSROOT/modules file on the server that contains valid module definitions. | ||
| 72 : | <ol> | ||
| 73 : | <li>Switch the Repositories View and ensure that the modules are displayed properly.</li> | ||
| 74 : | <li>Perform "Checkout as Module" and ensure that the module is checkout out properly. | ||
| 75 : | Also ensure that repeating results in overwrite prompt.</li> | ||
| 76 : | <li>Perform a "Configure Branches and Versions" on the module, set the autorefresh file and add some tags. | ||
| 77 : | Ensure that the module now appears properly in association with those tags.</li> | ||
| 78 : | </ol> | ||
| 79 : | |||
| 80 : | <h2>Project Sharing</h2> | ||
| 81 : | |||
| 82 : | <h3>Project sharing and disconnecting</h3> | ||
| 83 : | <ol> | ||
| 84 : | <li>Sharing with no CVS folders against existing project</li> | ||
| 85 : | <li>Sharing with CVS folders</li> | ||
| 86 : | <li>Sharing new project with no CVS folders</li> | ||
| 87 : | <li>Disconnect: keeping and deleting CVS folders, reconnecting (as above)</li> | ||
| 88 : | </ol> | ||
| 89 : | |||
| 90 : | <h3>Project sets</h3> | ||
| 91 : | <ol> | ||
| 92 : | <li>Create one, delete projects, load set and ensure got projects back</li> | ||
| 93 : | <li>Test against HEAD, project on branch/version.</li> | ||
| 94 : | </ol> | ||
| 95 : | |||
| 96 : | <h2>CVS workflow</h2> | ||
| 97 : | |||
| 98 : | <h3>Common workflows</h3> | ||
| 99 : | |||
| 100 : | To perform the tests properly, check out the same remote project into two local projects. | ||
| 101 : | |||
| 102 : | <ol> | ||
| 103 : | <li>Commit and Update with incomming, outgoing and conflicting changes and ensure proper behavior.</i> | ||
| 104 : | <li>Update/commit with very large files (> 8 meg)</li> | ||
| 105 : | <li>Replace with (latest, base, branch, version, revision)</li> | ||
| 106 : | <li>Compare with (latest, base, branch, version, revision)</li> | ||
| 107 : | <li>Ensure you are prompted for unsaved changes before performing a CVS action</li> | ||
| 108 : | <li>Tag as Version and ensure that remote is tagged properly.</li> | ||
| 109 : | <li>Tag as Version with dirty local resources and ensure proper prompting.</li> | ||
| 110 : | <li>Change ASCII/Binary Property on projects and resources and ensure proper behavior.</li> | ||
| 111 : | </ol> | ||
| 112 : | |||
| 113 : | <h3>Ignoring resources</h3> | ||
| 114 : | <ol> | ||
| 115 : | <li>Ignoring resources</li> | ||
| 116 : | <li>“Add to .cvsignore”</li> | ||
| 117 : | <li>Add to global ignore list, ensure its now ignored</li> | ||
| 118 : | </ol> | ||
| 119 : | |||
| 120 : | <h3>Global Actions</h3> | ||
| 121 : | Test the following CVS global actions in the CVS Repository Exploring perspective. | ||
| 122 : | <ol> | ||
| 123 : | <li>Synchronize All</li> | ||
| 124 : | <li>New Repository Location</li> | ||
| 125 : | </ol> | ||
| 126 : | |||
| 127 : | <h3>Decorators</h3> | ||
| 128 : | <ol> | ||
| 129 : | <li>Change all the options, apply, see them redraw correctly</li> | ||
| 130 : | <li>Add/remove items, ensure dirty markers update</li> | ||
| 131 : | <li>Add to version control and see decorator change</li> | ||
| 132 : | <li>Performance with large trees expanded</li> | ||
| 133 : | <li>Collapse large tree, exit workspace, restart (should not be as expensive | ||
| 134 : | as if tree had been left expanded)</li> | ||
| 135 : | mvalenta | 1.3 | <li>Close a decorated project and then open it to ensure good response.</li> |
| 136 : | <li>Checkout a project with decorators on to ensure good response.</li> | ||
| 137 : | mvalenta | 1.1 | </ol> |
| 138 : | |||
| 139 : | <h3>Patching</h3> | ||
| 140 : | Creating patches and then comparing with them. In particular, | ||
| 141 : | <ol> | ||
| 142 : | <li>added files</li> | ||
| 143 : | <li>deleted files</li> | ||
| 144 : | <li>added or deleted folders with added or deleted files in them</li> | ||
| 145 : | <li>binary files</li> | ||
| 146 : | </ol> | ||
| 147 : | |||
| 148 : | <h3>Watch/Edit</h3> | ||
| 149 : | <ol> | ||
| 150 : | <li>Turn on watch/edit in preferences (Team/CVS/Watch/Edit)</li> | ||
| 151 : | <li>Turn on the CVS decorators | ||
| 152 : | <li>Check out a project and ensure all files are read-only</li> | ||
| 153 : | <li>Open a file in an editor and start typing. Ensure that decorator an file changes and file is no longer read-only.</li> | ||
| 154 : | <li>Perform a Team/Show CVS Editors on the file and/or project.</li> | ||
| 155 : | <li>Perform a Team/Unedit on the file to ensure that file is returned to base contents and is read-only. | ||
| 156 : | (or perform a Team/Commit and ensure the file is returned to being read-only).</li> | ||
| 157 : | </ol> | ||
| 158 : | |||
| 159 : | <h3>Working with Modules</h3> | ||
| 160 : | These test require valid moduel definitions in the CVSROOT/modules file of the repository | ||
| 161 : | <ol> | ||
| 162 : | <li>Checkout a module and ensure success.</li> | ||
| 163 : | <li>Perform other CVS tests on the local project as if it were a regular project.</li> | ||
| 164 : | </ol> | ||
| 165 : | |||
| 166 : | <h3>Misc</h3> | ||
| 167 : | <ol> | ||
| 168 : | <li>Mixing tags within a project.</li> | ||
| 169 : | <li>Properties pages for projects, folders and files.</li> | ||
| 170 : | <li>CVS Console: ensure written to</li> | ||
| 171 : | <li>Check canceling everywhere there's a progress monitor</li> | ||
| 172 : | <li>Does it cancel in reasonable time?</li> | ||
| 173 : | <li>Is the workspace in an ok state after?</li> | ||
| 174 : | <li>Compression switches, ensure data transfered ok (commit, update)</li> | ||
| 175 : | </ol> | ||
| 176 : | |||
| 177 : | <h1>Section 2: CVS Synchronize View</h1> | ||
| 178 : | <table height="124" border="1" width="99%"> | ||
| 179 : | <tbody> | ||
| 180 : | <tr> | ||
| 181 : | <td width="25%"><b>Change Type</b></td> | ||
| 182 : | <td width="25%"><b>Action</b></td> | ||
| 183 : | <td width="50%"><b>Result</b></td> | ||
| 184 : | </tr> | ||
| 185 : | <tr> | ||
| 186 : | <td width="25%"><b>Incoming File Change</b></td> | ||
| 187 : | <td width="25%">Update</td> | ||
| 188 : | <td width="50%">Remote contents become local. Try with both Text and | ||
| 189 : | Binary files.</td> | ||
| 190 : | </tr> | ||
| 191 : | <tr> | ||
| 192 : | <td width="25%"><b>Incoming File Change</b></td> | ||
| 193 : | <td width="25%">Override and Commit</td> | ||
| 194 : | <td width="50%">Only in Both mode. Prompt for release comment. Cancel | ||
| 195 : | aborts, OK commits local file to server.</td> | ||
| 196 : | </tr> | ||
| 197 : | <tr> | ||
| 198 : | <td width="25%"><b>Incoming File Addition</b></td> | ||
| 199 : | <td width="25%">Update</td> | ||
| 200 : | <td width="50%">Remote contents become local. Try with both Text and | ||
| 201 : | Binary files.</td> | ||
| 202 : | </tr> | ||
| 203 : | <tr> | ||
| 204 : | <td width="25%"><b>Incoming File Addition</b></td> | ||
| 205 : | <td width="25%">Override and Commit</td> | ||
| 206 : | <td width="50%">Only in Both mode. Prompt for release comment. Cancel | ||
| 207 : | aborts, OK commits deletion to server.</td> | ||
| 208 : | </tr> | ||
| 209 : | <tr> | ||
| 210 : | <td width="25%"><b>Incoming File Deletion</b></td> | ||
| 211 : | <td width="25%">Update</td> | ||
| 212 : | <td width="50%">Local file is deleted.</td> | ||
| 213 : | </tr> | ||
| 214 : | <tr> | ||
| 215 : | <td width="25%"><b>Incoming File Deletion</b></td> | ||
| 216 : | <td width="25%">Override and Commit</td> | ||
| 217 : | <td width="50%">Only in Both mode. Prompt for release comment. Cancel | ||
| 218 : | aborts, OK commits local file to server.</td> | ||
| 219 : | </tr> | ||
| 220 : | <tr> | ||
| 221 : | <td width="25%"><b>Outgoing File Change</b></td> | ||
| 222 : | <td width="25%">Commit</td> | ||
| 223 : | <td width="50%">Prompt for release comment. Cancel aborts, OK commits | ||
| 224 : | local file to server.</td> | ||
| 225 : | </tr> | ||
| 226 : | <tr> | ||
| 227 : | <td width="25%"><b>Outgoing File Change</b></td> | ||
| 228 : | <td width="25%">Override and Update</td> | ||
| 229 : | <td width="50%">Only in Both mode. Remote contents become local. Try | ||
| 230 : | with both Text and Binary files.</td> | ||
| 231 : | </tr> | ||
| 232 : | <tr> | ||
| 233 : | <td width="25%"><b>Outgoing File Addition</b></td> | ||
| 234 : | <td width="25%">Add to Version Control</td> | ||
| 235 : | <td width="50%">Adds the file to version control. The icon should change | ||
| 236 : | in the sync view, and Commit should now be enabled.</td> | ||
| 237 : | </tr> | ||
| 238 : | <tr> | ||
| 239 : | <td width="25%"><b>Outgoing File Addition</b></td> | ||
| 240 : | <td width="25%">Add to .cvsignore</td> | ||
| 241 : | <td width="50%">Adds the file to .cvsignore. The file should disappear | ||
| 242 : | from the sync view. The .cvsignore file should appear (if it wasn't visible | ||
| 243 : | already). The file should not appear in subsequent syncs.</td> | ||
| 244 : | </tr> | ||
| 245 : | <tr> | ||
| 246 : | <td width="25%"><b>Outgoing File Addition</b></td> | ||
| 247 : | <td width="25%">Commit</td> | ||
| 248 : | <td width="50%">Commit is only enabled on an outgoing addition if it | ||
| 249 : | has first been added to version control. Prompt for release comment. Cancel | ||
| 250 : | aborts, OK commits local file to server.</td> | ||
| 251 : | </tr> | ||
| 252 : | <tr> | ||
| 253 : | <td width="25%"><b>Outgoing File Addition</b></td> | ||
| 254 : | <td width="25%">Override and Update</td> | ||
| 255 : | <td width="50%">Only in Both mode. Local file is deleted.</td> | ||
| 256 : | </tr> | ||
| 257 : | <tr> | ||
| 258 : | <td width="25%"><b>Outgoing File Deletion</b></td> | ||
| 259 : | <td width="25%">Commit</td> | ||
| 260 : | <td width="50%">Prompt for release comment. Cancel aborts, OK commits | ||
| 261 : | deletion to server.</td> | ||
| 262 : | </tr> | ||
| 263 : | <tr> | ||
| 264 : | <td width="25%"><b>Outgoing File Deletion</b></td> | ||
| 265 : | <td width="25%">Override and Update</td> | ||
| 266 : | <td width="50%">Only in Both mode. File is re-created, remote contents | ||
| 267 : | become local.</td> | ||
| 268 : | </tr> | ||
| 269 : | <tr> | ||
| 270 : | <td width="25%"><b>Conflicting File Change</b></td> | ||
| 271 : | <td width="25%">Override and Commit</td> | ||
| 272 : | <td width="50%">Prompt for release comment. Cancel aborts, OK commits | ||
| 273 : | local file to server. Applies to both auto-mergeable and non-mergeable conflicts.</td> | ||
| 274 : | </tr> | ||
| 275 : | <tr> | ||
| 276 : | <td width="25%"><b>Auto-mergeable Conflicting File Change</b></td> | ||
| 277 : | <td width="25%">Override and Update</td> | ||
| 278 : | <td width="50%">Auto-mergeable conflicts have a two-way red/green arrow. | ||
| 279 : | Dialog prompts user to either auto-merge or replace. If user chooses auto-merge, | ||
| 280 : | then remote changes are merged in with local changes. File should still | ||
| 281 : | be dirty, local changes should still be present, CVS markup should not be | ||
| 282 : | present, and no .# files should have been created. If user chooses replace, | ||
| 283 : | then local changes are discarded and remote contents replace local. No .# | ||
| 284 : | files created, no CVS markup, and the file is not dirty as a result. If | ||
| 285 : | the user chooses cancel nothing happens.</td> | ||
| 286 : | </tr> | ||
| 287 : | <tr> | ||
| 288 : | <td width="25%"><b>Non-mergeable Conflicting File Change</b></td> | ||
| 289 : | <td width="25%">Override and Update</td> | ||
| 290 : | <td width="50%">Dialog prompts user to replace local changes. If user | ||
| 291 : | cancels nothing happens. If user chooses OK, then local changes are discarded | ||
| 292 : | and remote contents replace local. No .# files created, no CVS markup, and | ||
| 293 : | the file is not dirty as a result.</td> | ||
| 294 : | </tr> | ||
| 295 : | <tr> | ||
| 296 : | <td width="25%"><b>Conflicting File Addition</b></td> | ||
| 297 : | <td width="25%">Add to Version Control</td> | ||
| 298 : | <td width="50%">Adds the file to version control. The icon should change | ||
| 299 : | in the sync view, and Override and Commit should now be enabled.</td> | ||
| 300 : | </tr> | ||
| 301 : | <tr> | ||
| 302 : | <td width="25%"><b>Conflicting File Addition</b></td> | ||
| 303 : | <td width="25%">Override and Commit</td> | ||
| 304 : | <td width="50%">Override and Commit is only enabled on an outgoing addition | ||
| 305 : | if it has first been added to version control. Prompt to warn of conflicting | ||
| 306 : | changes. If OK, prompt for release comment. Cancel aborts either dialog. | ||
| 307 : | OK commits local file to server.</td> | ||
| 308 : | </tr> | ||
| 309 : | <tr> | ||
| 310 : | <td width="25%"><b>Conflicting File Addition</b></td> | ||
| 311 : | <td width="25%">Override and Update</td> | ||
| 312 : | <td width="50%">Remote contents become local.</td> | ||
| 313 : | </tr> | ||
| 314 : | </tbody> | ||
| 315 : | </table> | ||
| 316 : | <h2>Variations</h2> | ||
| 317 : | <h3>Container Selection</h3> | ||
| 318 : | <p>Normally, selecting a folder is the same as selecting all of the individual | ||
| 319 : | files underneath it. (The exception to this is if the folder itself is changed, | ||
| 320 : | such as a conflicting addition). Performing any of the above operations | ||
| 321 : | on a folder should behave as if the files underneath it were selected.</p> | ||
| 322 : | <p>Note that if an action is not specified for a change type, it does not | ||
| 323 : | apply to that change type. This is important in container selection.</p> | ||
| 324 : | <p>For example: Commit does not apply to conflicting changes. If you select | ||
| 325 : | a folder with an Outgoing Change and a Conflicting Change in it, Commit | ||
| 326 : | will apply to the Outgoing Change but not to the Conflicting Change.</p> | ||
| 327 : | <h3>Multi-Selection</h3> | ||
| 328 : | <p>If multiple resources are selected, an action is enabled if it applies | ||
| 329 : | to any one or more of the selected resources. Choosing that action will | ||
| 330 : | apply the action only to those resources for which it is applicable.</p> | ||
| 331 : | <p>For example: Commit does not apply to conflicting changes. Selecting an | ||
| 332 : | Outgoing Change and a Conflicting Change will result in Commit being enabled. | ||
| 333 : | Choosing Commit will apply to the Outgoing Change but not to the Conflicting | ||
| 334 : | Change.</p> | ||
| 335 : | <p>Multi-Selection and Container Selection may be used in any combination | ||
| 336 : | with predictable results.</p> | ||
| 337 : | <h2>Specific Scenaria</h2> | ||
| 338 : | <h3>Making Manual Changes</h3> | ||
| 339 : | <p>Create a conflicting file change. Manually edit the left source pane in | ||
| 340 : | the sync view. Hit "Save" on the popup menu. The file should remain a Conflict; | ||
| 341 : | you should get a prompt telling you to Mark as Merged when finished. Choose | ||
| 342 : | Mark as Merged in the popup menu of the tree. The file should change to | ||
| 343 : | an outgoing change. Commit the outgoing change.</p> | ||
| 344 : | <h3>Merging Conflicts</h3> | ||
| 345 : | <p>Try Override and Update with different combinations of Auto-Mergeable | ||
| 346 : | and Non-Mergeable conflicts in the selection. If all conflicts are Non-Mergeable, | ||
| 347 : | then the only choice is to replace with remote or cancel. If one or more | ||
| 348 : | conflicts are Auto-Mergeable, the choices are (a) Auto-Merge any applicable | ||
| 349 : | files, and replace the rest with remote, (b) Replace all files with remote | ||
| 350 : | or (c) Cancel.</p> | ||
| 351 : | <h3>Removing from View</h3> | ||
| 352 : | <p>Choose Remove from View. Selected nodes should disappear. Refresh the | ||
| 353 : | view. The nodes should reappear.</p> | ||
| 354 : | <h3>Synchronize Outgoing Changes</h3> | ||
| 355 : | <p>If you choose Synchronize Outgoing Changes from the navigator, the sync | ||
| 356 : | view should be populated with <b>only the Outgoing Changes and Conflicts</b> | ||
| 357 : | . This operation should be significantly faster in many cases. In this | ||
| 358 : | case, ensure that Refresh does not cause Incoming Changes to appear.</p> | ||
| 359 : | <h3>Working with Branches</h3> | ||
| 360 : | <p>Try any and all of the above, but use a branch instead of HEAD. Behaviour | ||
| 361 : | should be identical. The sync view decorator should show you the name of | ||
| 362 : | the branch.</p> | ||
| 363 : | <h3>Using Mixed Tags</h3> | ||
| 364 : | <p>Using Team->Branch, Replace With->Branch or Version, and Team->Tag | ||
| 365 : | as Version, you can create a project which has different tags mixed into | ||
| 366 : | it. For example, one folder may be shared as V2_0, a single file may be attached | ||
| 367 : | to the branch NEW_FEATURE_BRANCH, and the root of the project may be attached | ||
| 368 : | to HEAD. We need to test usage of these projects in the sync view. For example, | ||
| 369 : | if developer 1 has project P shared with HEAD, and folder P/F is shared | ||
| 370 : | with branch B, have developer 2 release a change to folder F in HEAD, and | ||
| 371 : | have developer 1 perform a sync. In this case developer 1 should not see | ||
| 372 : | the incoming change.</p> | ||
| 373 : | |||
| 374 : | <h1>Section 4: Branching and Merging</h1> | ||
| 375 : | <h2>Main branching scenario</h2> | ||
| 376 : | Here's the main sequence of steps performed over the life cycle of a simple | ||
| 377 : | branch.<br> | ||
| 378 : | <ol> | ||
| 379 : | <li>Load or create a shared project with shared content</li> | ||
| 380 : | <li>Perform a Team/Branch...</li> | ||
| 381 : | <li>Ensure that the tag on the local resources has been updated (either | ||
| 382 : | using the CVS decorators or resource properties)</li> | ||
| 383 : | <li>Make some changes to local resources and commit them (working in a branch | ||
| 384 : | is similar to working in HEAD. See the Synchronize test plan for detaits).</li> | ||
| 385 : | <li>Load HEAD</li> | ||
| 386 : | <li>Optionaly, make some changes to HEAD (may or may not be committed)</li> | ||
| 387 : | <li>Perform a Team/Merge... to merge the branch with HEAD. Merging is similar | ||
| 388 : | to synchronizing but only incoming and conflicting changes are shown. See | ||
| 389 : | the Synchronize test plan for detaits</li> | ||
| 390 : | </ol> | ||
| 391 : | <h2>Variations</h2> | ||
| 392 : | <h3>Comparing branch, root version and HEAD</h3> | ||
| 393 : | After any of the above steps that modify the local content or the remote | ||
| 394 : | content, the success of the operation can ne validated by comparing the local | ||
| 395 : | workspace copy with either HEAD, the branch or the root version specified | ||
| 396 : | when creating the branch. | ||
| 397 : | <h3>Branch with local changes</h3> | ||
| 398 : | Before branching, make some local changes but do not commit them. Changes | ||
| 399 : | can include additions and deletions. After branches ensure that the changes | ||
| 400 : | are still there. On merging ensure that any created or deleted resources | ||
| 401 : | appear properly in the merge editor. | ||
| 402 : | <h3>Don't start working in the branch</h3> | ||
| 403 : | When the branch is created, do not start working in the branch. Ensure | ||
| 404 : | that the workspace was not modified but that the branch and root version | ||
| 405 : | exists remotely (using Comapre With/Branch or Version...) | ||
| 406 : | <h3>Branch on a folder or file</h3> | ||
| 407 : | Branching can also be performed on a folder or file. | ||
| 408 : | <h3>Merge from Head to a branch</h3> | ||
| 409 : | Make some changes to a branch and to HEAD. Merge the changes from HEAD | ||
| 410 : | into the branch before merging the branch with HEAD. | ||
| 411 : | mvalenta | 1.2 | |
| 412 : | |||
| 413 : | <h1>Section 3: Migration from 2.0 to 2.1</h1> | ||
| 414 : | The below tests require a workspace created using 2.0 which contains | ||
| 415 : | projects checked out from a CVS repository.<br> | ||
| 416 : | <h3>Migrating a workspace project created using 2.0 to 2.1</h3> | ||
| 417 : | <ol> | ||
| 418 : | <li>Start Eclipse 2.1 on top of a workspace from 2.0</li> | ||
| 419 : | <li>Select a project that was shared with a CVS repository and chose Team/Share | ||
| 420 : | Project…</li> | ||
| 421 : | <li>Select the Repository location to share with or enter it if it does | ||
| 422 : | not appear in the list.</li> | ||
| 423 : | <li>Upon finish, the user will be prompted to select either HEAD or the | ||
| 424 : | branch to compare against. </li> | ||
| 425 : | <li>The Synchronize view will then be opened and all files will appear | ||
| 426 : | as incoming, outgoing or conflicting additions.</li> | ||
| 427 : | <li>To see the real conflicts, enable “Compare File Contents” available | ||
| 428 : | from the drop down menu in the title bar of the Synchronize View.</li> | ||
| 429 : | <li>Resolve the real incoming, outgoing additions and conflicts as | ||
| 430 : | appropriate (see sync view test plan for a description of sync state resolution)</li> | ||
| 431 : | <li>When all conflicts are resolved, disable “Compare File Contents” and | ||
| 432 : | perform an “Override and Update” on the remaining conflicting additions to | ||
| 433 : | update the sync info of the local resources.</li> | ||
| 434 : | <li>Ensure local copy contains the proper contents (can use Compare With/Latest | ||
| 435 : | from Repository)<br> | ||
| 436 : | </li> | ||
| 437 : | </ol> | ||
| 438 : | |||
| 439 : | mvalenta | 1.1 | </body> |
| 440 : | </html> |
| help@eclipse.org | ViewVC Help |
| Powered by ViewVC 1.0.3 |