platform-update-home/doc/Test Scenarios/eclipse update 3.0.html

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

revision 1.11, Tue Jul 29 15:45:27 2003 UTC revision 1.12, Tue Aug 26 18:56:40 2003 UTC
# Line 9  Line 9 
9  <h1>  <h1>
10  Scenario: Updating Eclipse Install Using Eclipse Update 3.0</h1>  Scenario: Updating Eclipse Install Using Eclipse Update 3.0</h1>
11  Last Updated:  Last Updated:
12  <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%A, %B %d, %Y" startspan -->Tuesday, June 24, 2003<!--webbot bot="Timestamp" endspan i-CheckSum="36838" --><p>  <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%A, %B %d, %Y" startspan -->Tuesday, August 26, 2003<!--webbot bot="Timestamp" endspan i-CheckSum="36838" --><p>
13  <i>Note: This is the draft of the new test scenarios that are based on 2.1  <i>Note: This is the draft of the new test scenarios that are based on 2.1
14  version but take into account redesigned Eclipse Update user interface. Some of  version but take into account redesigned Eclipse Update user interface. Some of
15  the old functionality may not be available in the new UI, making some scenarios  the old functionality may not be available in the new UI, making some scenarios
# Line 60  Line 60 
60  and installing various versions of the Eclipse components into the running  and installing various versions of the Eclipse components into the running
61  Eclipse. The update site is populated with features that have their version  Eclipse. The update site is populated with features that have their version
62  numbers modified as part of the build process. They are generally of the  numbers modified as part of the build process. They are generally of the
63  form 2.0.0.QUALIFIER, where the qualifier differs build to build. Note,  form 3.0.0.QUALIFIER, where the qualifier differs build to build. Note,
64  however, that when you install base Eclipse (.zip downloaded from eclipse.org),  however, that when you install base Eclipse (.zip downloaded from eclipse.org),
65  all of its features and plug-ins only use 3 part version identifiers (generally  all of its features and plug-ins only use 3 part version identifiers (generally
66  2.1.0). So all the 2.1.0.Q updates in fact appear more recent that the  3.0.0). So all the 3.0.0.Q updates in fact appear more recent that the
67  build you are running, even though they may in fact be an older build.  build you are running, even though they may in fact be an older build.
68  Note, that when you update the Eclipse components from the update site  Note, that when you update the Eclipse components from the update site
69  and restart you may in fact now be running </font><font color="#FF0000">DIFFERENT  and restart you may in fact now be running </font><font color="#FF0000">DIFFERENT
# Line 75  Line 75 
75  these scenarios.</font><p><font color="#000000">When opening Bugzilla defects, use the  these scenarios.</font><p><font color="#000000">When opening Bugzilla defects, use the
76  Platform/Update  Platform/Update
77  component. Please ALWAYS specify the failing scenario step, and include  component. Please ALWAYS specify the failing scenario step, and include
78  a .zip of the &lt;workspace>/.metadata/ directory</font></td>  a .zip of the eclipse/.config/ directory</font></td>
79  </tr>  </tr>
80  </table>  </table>
81    
# Line 97  Line 97 
97    
98  <ul>  <ul>
99  <li>  <li>
100  A.1. startup Eclipse. On the initial startup with new workspace you should  A.1. startup Eclipse. On the initial startup you should
101  see the splash come up, be taken down down, and come up again before it  see the splash come up, be taken down down, and come up again before it
102  is finally taken down before the Workbench appears. This is due to Eclipse  is finally taken down before the Workbench appears. This is due to Eclipse
103  restart when new features are detected on startup.</li>  restart when new features are detected on startup.</li>
# Line 105  Line 105 
105  <li>  <li>
106  A.2 go to <b>Help>About</b> and click [Feature Details] and [Plug-in Details]  A.2 go to <b>Help>About</b> and click [Feature Details] and [Plug-in Details]
107  to see more details of what is actually running. Note the baseline version  to see more details of what is actually running. Note the baseline version
108  of the various items (most will be 2.1.0)</li>  of the various items (most will be 3.0.0)</li>
109    
110  <li>  <li>
111  A.3. go to <b>Help> Software Updates> Configuration Manager</b> and verify that the features  A.3. go to <b>Help> Software Updates> Manage Configuration...</b> and verify that the features
112  corresponding to the baseline install appear in the "Eclipse Platform&quot; root  corresponding to the baseline install appear in the "Eclipse Platform&quot; root
113  node.</li>  node.</li>
114  </ul>  </ul>
# Line 158  Line 158 
158  &nbsp;</li>  &nbsp;</li>
159    
160  <li>  <li>
161  C.1. select <b>Help&gt;Software Updates&gt;New Updates (Experimental)</b></li>  C.1. select <b>Help&gt;Software Updates&gt;Find and Install...</b></li>
162    
163  <li>  <li>
164  C.2. Make sure that 'Search for updates of the currently installed features'  C.2. Make sure that 'Search for updates of the currently installed features'
# Line 198  Line 198 
198  <li>  <li>
199  C.7. go to Help> About> [Plug-In Details] and [Feature Details] to verify  C.7. go to Help> About> [Plug-In Details] and [Feature Details] to verify
200  you are running new version of the platform (the versions for the items  you are running new version of the platform (the versions for the items
201  will be 2.1.0.&lt;qualifier>)</li>  will be 3.0.0.&lt;qualifier>)</li>
202    
203  <li>  <li>
204  C.8. Go to Help> Software Updates> Configuration Manager, expand "Current Configuration"  C.8. Go to Help> Software Updates>Manage Configuration , expand the tree
205  and verify you now recognize the new version of the platform that was updated</li>  and verify you now recognize the new version of the platform that was updated</li>
206  </ul>  </ul>
207    
# Line 210  Line 210 
210    
211  <ul>  <ul>
212  <li>  <li>
213  D.1. Select <b>Help&gt;Software Updates&gt;Configuration Manager</b> to open the  D.1. Select <b>Help&gt;Software Updates&gt; Manage Configuration...</b> to open the
214  configuration manager window.</li>  configuration manager window.</li>
215  <li>  <li>
216  D.2 Select the current configuration object (the root node) and choose 'Revert  D.2 Select the current configuration object (the root node) and choose 'Revert
# Line 235  Line 235 
235    
236  <li>  <li>
237  D.7. expand the root node and verify all configured features  D.7. expand the root node and verify all configured features
238  are the baseline feature versions (generally 2.1.0)</li>  are the baseline feature versions (generally 3.0.0)</li>
239    
240  <li>  <li>
241  D.8. click "Show Disabled Features" button in the toolbar of the Configuration  D.8. click "Show Disabled Features" button in the toolbar of the Configuration
# Line 243  Line 243 
243    
244  <li>  <li>
245  D.9. go to <b>Help>About</b> dialog, [Plug-In Details] and verify you are in  D.9. go to <b>Help>About</b> dialog, [Plug-In Details] and verify you are in
246  fact running the baseline plug-ins (all 2.1.0, except for the "special cases"  fact running the baseline plug-ins (all 3.0.0, except for the "special cases"
247  like Xerces, Ant, Lucene, Tomcat, etc)</li>  like Xerces, Ant, Lucene, Tomcat, JUnit, etc)</li>
248    
249  <li>  <li>
250  D.10. shut down the workbench</li>  D.10. shut down the workbench</li>
# Line 345  Line 345 
345  letter (one action per letter on the menu)</li>  letter (one action per letter on the menu)</li>
346    
347  <li>  <li>
348  O.5. Open Help> Software Updates> Configuration Manager</li>  O.5. Open Help> Software Updates>Manage Configuration ...</li>
349    
350  <li>  <li>
351  O.6. Expand "Alphabet Soup". Verify "Alphabet Soup 1.0.0" is configured,  O.6. Expand "Alphabet Soup". Verify "Alphabet Soup 1.0.0" is configured,
Legend:
Removed from v.1.11  
changed lines
  Added in v.1.12