Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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"
| Line 8: | Line 8: | ||
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. | ||
| − | == | + | == End-to-End Scenarios == |
| − | === | + | === A Full Plug-in Development Cycle === |
* From the top level menu, select Help > Cheatsheets... > Plug-in Development > Creating an Eclipse Plug-in. Press OK. | * 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. | * Go through this cheatsheet to explore all stages of the plug-in development cycle. | ||
| − | === | + | === Creating an Rich Client Application === |
* From the top level menu, select Help > Cheatsheets... > Plug-in Development > Creating a Rich Client Application. Press OK. | * 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. | * Go through this cheatsheet to create a standalone, fully-branded rich client application. | ||
| − | == | + | == Search == |
| − | === | + | === Classic Plug-in Search === |
* From the top level menu, select Search > Search... to bring up the Search dialog. | * 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. | * Click on the Plug-in Search tab. Enter *.debug.ui.* as a search string. Leave all defaults as-is. Press the Search button. | ||
| Line 30: | Line 30: | ||
* 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. | * 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. | * Close all manifest editors. | ||
| + | |||
| + | === Plug-in Search in Mixed Namespaces === | ||
| + | * Bring up the New Plug-in Project creation wizard via File > New > Project... > Plug-in Project. Press Next. | ||
| + | * Enter com.example.xyz as the project name. Press Next. | ||
| + | * Accept all defaults and press Finish. Answer Yes when prompted to switch to the Plug-in Development perspective. | ||
| + | * On the Extension Points page of the plug-in manifest editor, press Add... | ||
| + | * Enter org.eclipse.pde.core.parsers as the extension point ID. Enter Parsers as the extension point name. | ||
| + | * Uncheck the checkbox to edit the extension point schema. Press Finish. | ||
| + | * Verify that the extension point was created. Save the file and close the editor. | ||
| + | * Bring up the search dialog via Search > Search... from the top level menu. | ||
| + | * On the Plug-in Search tab, enter org.eclipse.pde.core.* as the search string. In the Limit To group, select Declarations. Press the Search button. | ||
| + | * Verify that the search view opens with 5 matches. | ||
| + | * Double-click on the org.eclipse.pde.core.parsers search hit. Verify that it correctly locates the extension point on the plugin.xml source page of the com.example.xyz plug-in. | ||
| + | * Double-click on the org.eclipse.pde.source search hit. Verify that the extension point declaration is correctly located on the plugin.xml source page of the org.eclipse.pde.core plug-in. | ||
Revision as of 16:26, 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.
End-to-End Scenarios
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.
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.
Search
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.
Plug-in Search in Mixed Namespaces
- Bring up the New Plug-in Project creation wizard via File > New > Project... > Plug-in Project. Press Next.
- Enter com.example.xyz as the project name. Press Next.
- Accept all defaults and press Finish. Answer Yes when prompted to switch to the Plug-in Development perspective.
- On the Extension Points page of the plug-in manifest editor, press Add...
- Enter org.eclipse.pde.core.parsers as the extension point ID. Enter Parsers as the extension point name.
- Uncheck the checkbox to edit the extension point schema. Press Finish.
- Verify that the extension point was created. Save the file and close the editor.
- Bring up the search dialog via Search > Search... from the top level menu.
- On the Plug-in Search tab, enter org.eclipse.pde.core.* as the search string. In the Limit To group, select Declarations. Press the Search button.
- Verify that the search view opens with 5 matches.
- Double-click on the org.eclipse.pde.core.parsers search hit. Verify that it correctly locates the extension point on the plugin.xml source page of the com.example.xyz plug-in.
- Double-click on the org.eclipse.pde.source search hit. Verify that the extension point declaration is correctly located on the plugin.xml source page of the org.eclipse.pde.core plug-in.