Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PDE/UI/TestPlan 3.4"
(New page: # Setup Two steps that need to be done before executing any of the scenarios. * Launch Eclipse on a new workspace. * Dismiss the Welcome Page by clicking on the Go to Workbench icon. At...) |
|||
| Line 1: | Line 1: | ||
| − | + | == Setup == | |
Two steps that need to be done before executing any of the scenarios. | Two steps that need to be done before executing any of the scenarios. | ||
| Line 7: | Line 7: | ||
At the end of each scenario, it is recommended to delete all projects from your workspace so that one part does not interfere with the next. | At the end of each scenario, it is recommended to delete all projects from your workspace so that one part does not interfere with the next. | ||
| + | |||
| + | == Scenario A: End-to-End Scenarios == | ||
| + | |||
| + | === A1. A Full Plug-in Development Cycle === | ||
| + | * From the top level menu, select Help > Cheatsheets... > Plug-in Development > Creating an Eclipse Plug-in. Press OK. | ||
| + | * Go through this cheatsheet to explore all stages of the plug-in development cycle. | ||
| + | |||
| + | === A2. Creating an Rich Client Application === | ||
| + | * From the top level menu, select Help > Cheatsheets... > Plug-in Development > Creating a Rich Client Application. Press OK. | ||
| + | * Go through this cheatsheet to create a standalone, fully-branded rich client application. | ||
| + | |||
| + | == Scenario B: Search == | ||
| + | |||
| + | === B1. Classic Plug-in Search === | ||
| + | * From the top level menu, select Search > Search... to bring up the Search dialog. | ||
| + | * Click on the Plug-in Search tab. Enter *.debug.ui.* as a search string. Leave all defaults as-is. Press the Search button. | ||
| + | * Verify that the Search view opens and that it contains 31 hits. | ||
| + | * Double-click on the first hit to open the manifest editor of the org.eclipse.debug.ui plug-in. | ||
| + | * Verify that the editor opens to the plugin.xml source page and that the extension point ID is visible and correctly selected. Also verify that the arrow in the margin is on the correct line. | ||
| + | * Using the Down Arrow in the Search view toolbar, navigate to the next hit. | ||
| + | * Verify that the manifest editor for the org.eclipse.ant.ui plug-in opens with the extension hit visible and correctly selected. | ||
| + | * Press the Down Arrow again. Verify that the selection moves to another hit within the same editor. Verify that a new editor does NOT open. | ||
| + | * Close all manifest editors. | ||
Revision as of 16:22, 23 March 2008
Contents
Setup
Two steps that need to be done before executing any of the scenarios.
- Launch Eclipse on a new workspace.
- Dismiss the Welcome Page by clicking on the Go to Workbench icon.
At the end of each scenario, it is recommended to delete all projects from your workspace so that one part does not interfere with the next.
Scenario A: End-to-End Scenarios
A1. A Full Plug-in Development Cycle
- From the top level menu, select Help > Cheatsheets... > Plug-in Development > Creating an Eclipse Plug-in. Press OK.
- Go through this cheatsheet to explore all stages of the plug-in development cycle.
A2. Creating an Rich Client Application
- From the top level menu, select Help > Cheatsheets... > Plug-in Development > Creating a Rich Client Application. Press OK.
- Go through this cheatsheet to create a standalone, fully-branded rich client application.
Scenario B: Search
B1. Classic Plug-in Search
- From the top level menu, select Search > Search... to bring up the Search dialog.
- Click on the Plug-in Search tab. Enter *.debug.ui.* as a search string. Leave all defaults as-is. Press the Search button.
- Verify that the Search view opens and that it contains 31 hits.
- Double-click on the first hit to open the manifest editor of the org.eclipse.debug.ui plug-in.
- Verify that the editor opens to the plugin.xml source page and that the extension point ID is visible and correctly selected. Also verify that the arrow in the margin is on the correct line.
- Using the Down Arrow in the Search view toolbar, navigate to the next hit.
- Verify that the manifest editor for the org.eclipse.ant.ui plug-in opens with the extension hit visible and correctly selected.
- Press the Down Arrow again. Verify that the selection moves to another hit within the same editor. Verify that a new editor does NOT open.
- Close all manifest editors.