platform-vcm-home/2_0_testing.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.1, Wed May 22 19:38:25 2002 UTC revision 1.2, Wed May 22 20:17:33 2002 UTC
# Line 205  Line 205 
205  <p>Choose Remove from View. Selected nodes should disappear. Refresh the view. The nodes should reappear.</p>  <p>Choose Remove from View. Selected nodes should disappear. Refresh the view. The nodes should reappear.</p>
206  <h3>Synchronize Outgoing Changes</h3>  <h3>Synchronize Outgoing Changes</h3>
207  <p>If you choose Synchronize Outgoing Changes from the navigator, the sync view should be populated with <b>only the Outgoing Changes and Conflicts</b>. This operation should be significantly faster in many cases. In this case, ensure that Refresh does not cause Incoming Changes to appear.</p>  <p>If you choose Synchronize Outgoing Changes from the navigator, the sync view should be populated with <b>only the Outgoing Changes and Conflicts</b>. This operation should be significantly faster in many cases. In this case, ensure that Refresh does not cause Incoming Changes to appear.</p>
208    <h3>Working with Branches</h3>
209    <p>Try any and all of the above, but use a branch instead of HEAD. Behaviour should be identical. The sync view decorator should show you the name of the branch.</p>
210    <h3>Using Mixed Tags</h3>
211    <p>Using Team->Branch, Replace With->Branch or Version, and Team->Tag as Version, you can create a project which has different tags mixed into it. For example, one folder may be shared as V2_0, a single file may be attached to the branch NEW_FEATURE_BRANCH, and the root of the project may be attached to HEAD. We need to test usage of these projects in the sync view. For example, if developer 1 has project P shared with HEAD, and folder P/F is shared with branch B, have developer 2 release a change to folder F in HEAD, and have developer 1 perform a sync. In this case developer 1 should not see the incoming change.</p>
212    
213  <h1>Section 3: Migration from 1.0 to 2.0</h1>  <h1>Section 3: Migration from 1.0 to 2.0</h1>
214  Both the below tests require a workspace created using 1.0 which contains  Both the below tests require a workspace created using 1.0 which contains
Legend:
Removed from v.1.1  
changed lines
  Added in v.1.2