Please ensure that you run this test plan with the org.eclipse.ui.intro/debug=true debug
option set. This is the only intro debug option that you need turned on, and if
there are any errors or warnings in the .log then this is a bug. Please open a
defect and include the log.
1. Launch a fresh workbench. Make sure that Intro is automatically opened and is in full mode.
2. Test that root page come up/looks ok. Icons should be there. Hovering over icons causes the icons to show text describing them.
3. Test clicking on each of the links in the root page.
4. In Overview page, test that each of the links brings you to a corresponding topic from the Help System documentation.
5. In the Tutorials page, make sure that clicking on each of the links brings you to the appropriate cheat sheet.
6. In the Samples page, click on any of the links, you should get a pop-up asking you to download the samples. Click Yes. Check that all samples can then be imported automatically into the workbench and that they can be run.
7. In the What's New page, the New and Noteworthy links and the Migration link should launch the Help System and take you to the appropriate page. The New Updates link should launch an Install/Update dialog to update features. The latest news from eclipse.org should also be available as links.
8. Click on the Eclipse Community link, it should open the eclipse.org web site.
9. Click on the curved arrow icon to “Go to the workbench” and make sure that you get the launch bar at the bottom right trim of the workbench window. It should have a button for each welcome page. All should have tooltip, and clicking on each should open Intro in full mode and take you to the appropriate page.
10. Hover over the Return to Workbench and the Close icons in the launch bar to get the "move" cursor. Test drag and drop of Launch bar.
1. Close the workbench with the Intro view opened in full mode. Test that re-launching a workbench opens Intro.
2. Close the workbench with the Intro view opened in standby mode on a cheatSheet (ie: go to Tutorials and click on any of the links). Test that re-launching a workbench opens Intro with the same cheatSheet opened in standby mode.
3. Close the workbench with the Intro view opened in standby mode on the SDK Welcome standby page (ie: double click on the Intro view to bring it to the Standby page). Test that re-launching a workbench opens Intro with the SDK Welcome standby page opened.
4. From a cheatSheet in standby mode, click on Return to Welcome and make sure it takes you back top the last page to where at.
1. Go to Help -> Welcome, note the icon for the menu item
2. Make sure the same icon is used for the Welcome view.
3. In the welcome view toolbar, make sure that the Home icon is enabled and that it has a tooltip.
4. Make sure that the left and right icons are initially disabled, and are subsequently enabled when you navigate to some of the pages. These icons should be disabled if there is no history to navigate to.
5. When the welcome view is in standby mode (e.g. when you open a cheat sheet, or double click on Welcome view) the home, back, and next icons are disabled.
1. Open the General -> Welcome preference page.
2. Change the theme, verify that it works.
3. Add and remove some pages, make it updates accordingly (some pages may be empty)
4. In the Overview, Tutorials, etc tabs, move some items to the Available Extensions and confirm that they no longer show up
5. Move some items to different columns and confirm that the welcome pages react accordingly
6. Change the priority on some items by clicking the icons. Verify that different priorities appear differently in the welcome.
1. On Windows, Linux and Mac, Intro uses the HTML presentation, assuming the browser is properly configured.
2. On all other platforms, intro uses the SWT Forms-based presentation.
3. Click on any of the root page icons. If the links for all the pages (Overview, Tutorials ...) are at the top left corner of the page, you have HTML presentation. If they are centered at the bottom of the page, you have SWT. It is a bug if the correct presentation is not visible on the corresponding platform.
These tests exercise interactions with help system from workbench.
1. Launch "Window"->"Preferences". Preferences dialog will open.
2. Choose "Help" on the left. This should show help preference page on the right
3. On Windows and Linux help uses embedded browser, and the preference should contain a checkbox to use external browser.
4. Choose "Help"->"Help Contents" from the workbench menu, ensure a browser opens and displays Help browser.
5. Go back to help preferences, select "Use external browser". Follow hyperlink to Workbench Browsers preference page. Choose a browser to use, Click "OK".
6. Choose "Help"->"Help Contents" from the workbench menu, ensure a browser selected opens and displays Help.
7. Go back to help preferences. If you have more browser adapters available, try selecting each browser adapter and launch help.
1. Press "F1" key (Ctrl+F1 on GTK, Help on carbon) in the workbench "Navigator" view ("Resources" perspective). This should open help view in the workbench, turned to Related Topics page. Verify "About ..." section displays description of workbench part in focus.
2. Click on one of the related links. A topic should open in the help view.
3. Change help preferences to open context help in an infopop, dialog context help in an infopop, help view document open mode - in editor.
4. Click "back" in the help view to arrive at Related Topics page. Select a link from Dynamic Help section. Verify it opens in the editor area.
5. Press "F1" key (Ctrl+F1 on GTK, Help on carbon) in the workbench "Navigator" view ("Resources" perspective) again. This time it should open an infopop with a description and related links. Focus should be on the first link ("Views").
6. Click "Navigator View" link. This should launch help web browser, and display "Navigator View" document on the right and the list of related topics on the left. The link called "Navigator View" should be selected.
7. Open help preferences, press "F1". and infopop should open.
8. Restore defaults in the the browser preference page, and apply.
9. Press F1 again. A small help view with Related Topics should open adjacent to the preferences dialog.
1. Without closing the browser that opened in the previous test case, choose "Help"->"Help" Contents" from the workbench menu. No new browser window should launch, and the existing help browser should load the table of contents, with lists of books on the left, and "Welcome to Eclipse help" document on the right.
2. Close the help browser. Browser window should close.
1. Choose "Search" from the workbench Help menu. Help search page should open.
2. Type a query "open project" (without quotes), click "Go".
3. Choose a result. The document should open with occurrences of the words "open" and "project" highlighted.
1. Type "active link below" (no quotes) in the search field in the help view, and search.
2. Choose a document titled "Active help" from the search results.
3. Click once "Click here for a Message" link at the bottom of the document.
4. Ensure that a "Hello World" is being displayed in a dialog on top of the workbench.
1. Launch "Window"->"Preferences". Preferences dialog will open.
2. Choose "Help/Help Server" on the left. Enter a port number (for example 2003), in the second field. Click O.K.
3. Restart workbench. Launch help from the menu. Ensure browser opens and displays help content.
4. Go back to Help Server preferences, click "Restore defaults" button, click "OK", restart workbench.
1. Launch "Window"->"Preferences". Open "General"->"Capabilities" preference page.
2. Select all capabilities and deselect "Development".
3. Launch help , by selecting Help->Help Contents from the menu. Verify only two workbench books appear.
4. Select "Show All Topics" button in the navigation toolbar. Confirm.
5. Verify "Show All Topics" toolbar button appears pressed, and all books (including PDE Guide are displayed).
6. Search for "PDE". There should be large number of hits
7. Turn off showing all topics. Verify that PDE Guide disappeared, since it is does not belong to enabled workbench capabilities.
8. Perform search for "PDE". Verify search results were redisplayed and there are no or next to no results.
1. Open the preferences dialog
2. Click on the help button (?) at the lower left part of the dialog
3. Confirm the help tray opens and is usable. Try All Topics, search, bookmarks.
4. Close the tray.
5. Verify that clicking the help button (?) behaves the same way as pressing F1.
6. Try with a dialog that is not resizable. It should show the yellow sticky.
7. Try with a resizable dialog that is short. The dialog should grow a bit to accommodate the tray, then go back to original size when closed.
8. Open the help tray, then close the dialog without explicitly closing the tray.
9. Confirm the dialog properly remembers its size (if applicable to that dialog) and does not include the tray as part of its size.
1. Find some XHTML docs in the help system (you’ll have to import plugin in workspace and look for the .xhtml file extension)
2. Open these docs in the help window and help view; make sure they appear correctly.
3. Open the markup and find the parts that are filtered (e.g. there might be a windows only section)
4. Confirm the parts are filtered from the non-applicable platforms. E.g. if it’s windows only, should only be visible on windows
5. Search for a word in the XHTML doc. It should show up as a potential hit.
6. Change preferences (Help preferences page) to show actual hits.
7. Repeat the same search. It should only find the result if the word is visible in the doc. E.g. on windows it should find it, on linux it shouldn’t.
1. Download and extract the test files zip from http://www.eclipse.org/eclipse/platform-ua/testing/test_files.zip
2. Extract the /help/org.eclipse.help.index.test.zip and place the test plugin in your plugins dir; restart workbench
3. Open Help -> Help Contents
4. Verify that there’s a new index tab at the bottom left.
5. Open it, verify the proper functioning of the index view; make sure it’s usable, easy to understand
6. Type some keywords, open the docs, etc.
7. Do the same in the help view.
1. Browse the platform user docs and look for links that perform actions. For example, opening a preference page, etc.
2. Click on the links in both the help window and help view
3. Confirm: The actions are performed successfully
4. Confirm: The command links have a special appearance that distinguish them from other links
5. When clicking on a link to open a dialog from help window, dialog is visible
1. The main things to look for here are:
2. moving around the navigation views (Contents, Search Results, Links, Bookmarks)
3. opening a book, expanding/collapsing/selecting topic nodes
4. navigating links inside the help pages
5. using toolbar actions for displaying the main table of contents, for hiding or maximizing the navigation frame, for topic/navigation synchronization, printing
6. performing simple searching.
Note: this test is to be done on browser adapters that are based on Internet Explorer or Mozilla. For other browser, refer to the "basic" test.
1. Launch help from the workbench menu: Help->Help Contents. This should open the help view to the main bookshelf that lists the available books.
2. In the Contents page select the Workbench User Guide book. This should expand that book and show it contents. All the other books must still be available in the navigation frame (i.e. only the select book expands).
3. In the table of contents tree navigate to Concepts ->Workbench. Selecting the "Workbench" topic should show some content in the main help area.
4. Click on the "Features" link in the displayed document. This should load a new document.
1. Identify the 6 buttons on the content toolbar (the toolbar is located above the page displaying help pages): Go Back, Go Forward, Show in table of contents, Bookmark document, Print Page, and Maximize.
2. Click the Back button in the content toolbar. This should reload the previous document (Workbench).
3. Click the Forward button in the content toolbar. This should reload the document ("Features").
4. Click maximize icon on the toolbar of the main content frame. This should maximize that particular frame, and "Restore" icon should be shown in place of "Maximize". This time double click on the toolbar, it should restore the original layout. The behavior should be similar to that of the eclipse views.
5. Click on the "Synchronize Navigation" button on the toolbar. This should highlight the "Features" topic in the navigation tree.
6. Print the topic by clicking on the "Print Page" button on the toolbar. This should launch the system print dialog and if you click OK it should print the help page
7. Bookmark the current page, by pressing the "Bookmark document" button on the toolbar.
8. Turn to the Bookmarks tabs and verify it is added there.
9. Turn to the Contents tab and select another topic
10. Turn to the Bookmarks tab and click on the bookmarked topic (Features). This should load that topic in the main content area.
11. Remove bookmark: Select the bookmark topic, right click and select Remove, or choose "Delete bookmark" from the bookmark view toolbar.
12. Add more bookmarks, delete them all using "Remove all bookmarks" button or action on the pop-up menu.
1. In the Search entry field enter the word "participation" without the double quotes. The navigation frame should turn to the Search Results view, and if this was the first time you search the docs, you should see the indexing progress monitor in that page. When indexing is finished (or right away if other searches were performed before) you should get the results. In my case, I got 14 hits, starting with "Synchronize View Integration".
2. Select a search result: "Workspace save participation". You should see the "participation" string highlighted, as well as "particip". This is because the search engine uses word stemming on English, so the highlighting respects the same stemming algorithm.
3. Click on each results. You should see the toolbar title changing to show the book containing the document.
4. Let's narrow the results by book: click on the "Scope" link in the search bar. This should launch the Select Scope Search dialog that let's use define search list. Click on "New" to launch the dialog for defining a new search list. Enter the name "workbench" and select the "Workbench User Guide", click OK to close the dialog. The name "workbench" should now be visible in the list in the Select Scope Search dialog. Select it, and click OK (or double click instead).
5. This should close the dialog and the Search Scope should now display the name "workbench". Note: Sometimes the search bar is not updated right away, so you may have to wait a bit. Search again for the same word, "participation". You should see fewer results (I see 2 hits only).
6. Select the "Crash recovery" hit, and click on "Synchronize Navigation" button on the navigation or content toolbar. This should switch the navigation view to the Contents view, and expand the Workbench User Guide down to the "Crash recovery" topic.
7. Click the "Search Results" tab at the bottom of the navigation tree. This should redisplay the search result you've seen in step 5.
8. Click on the "Contents" tab at the bottom of the navigation tree. This should redisplay the navigation tree as you left it after step 6.
This part test support for advanced search. Perform search either from "Help" page on Eclipse "Search" dialog opened by "Search"->"Search..." and turning to Help page or from the browser opened by "Help"-"Help Contents".
1. Search for 'project close' (no quotes). Documents should be found containing both words. Selecting document should show its contents with occurrences of both words highlighted.
2. Search for 'project AND close' (no quotes). The results should be same as for the previous query
3. Search for 'project OR close' (no quotes). The list of hits should be much longer, with some documents at the top containing both words, and documents down the list containing only one of them.
4. Search for 'project close not navigator' (no quotes). The list of hits should be smaller than in step 1.
5. Exact search:
6. Search for ' "close project" ' (in double quotes). The search results list should be shorter than in step 1.
7. The documents should contain consecutive words close and project (possibly separated by a punctuation).
8. Search scope
9. Search for 'close project' (no quotes). The search results list will show hits.
10. Select a document. Note the book the topic belongs to. The book name is displayed on the toolbar in the browser, directly above the document.
11. Click "Search scope:". The scope selection window will open. Click "New", Select some books or sections, but leave the book that was noted in step 2 unchecked.
12. Type a name for your new scope. Close dialog windows, ensure that the scope name appears on the search tool bar.
13. Click "Go". Verify that the document selected in step 3 does not appear in the list of search results.
14. Click the Search Scope again and remove the scope you just defined. Click OK to close the dialog. The search bar should now have "All topics" in the Search Scope.
Create a file plugin_customization.ini in the root of Eclipse installation. Edit the file and paste the following key/values pairs:
org.eclipse.help/baseTOCS=/org.eclipse.pde.doc.user/toc.xml,/org.eclipse.jdt.doc.isv/toc.xml
org.eclipse.help/ignoredTOCS=/org.eclipse.platform.doc.user/toc.xml,/org.eclipse.jdt.doc.user/toc.xml,/org.eclipse.platform.doc.isv/toc.xml
org.eclipse.help.base/banner=/org.eclipse.help.webapp/advanced/banner.html
org.eclipse.help.base/banner_height=60
org.eclipse.help.base/help_home=http://www.eclipse.org
org.eclipse.help.base/linksView=false
org.eclipse.help.base/bookmarksView=false
org.eclipse.help.base/windowTitlePrefix=false
org.eclipse.help.base/loadBookAtOnceLimit=10
org.eclipse.help.base/dynamicLoadDepthsHint=2
org.eclipse.help.base/advanced.toolbarBackground=green
org.eclipse.help.base/advanced.viewBackground=yellow
org.eclipse.help.base/advanced.toolbarFont=bold
org.eclipse.help.base/advanced.viewFont=italic
org.eclipse.help.base/showDisabledActivityTopics=never
org.eclipse.help.base/activeHelp=false
1. Launch Eclipse, pointing to the ppreferences customization, e.g. eclipse -pluginCustomization plugin_customization.ini
2. From the workbench menu: Help->Help Contents. This should open the help browser. Verify existence of banner frame above search toolbar.
3. The page displayed in the content frame should be eclipse.org page.
4. There should be only two Eclipse books displayed PDE Guide and JDT Development Guide, in that order. Other Eclipse books should not appear.
5. Search for "workbench". Verify there are no hits from Workbench User Guide that is not present.
6. Verify there is only Contents and Search tabs at the bottom of navigation frame, other views (Links and Bookmarks) are not present.
7. Verify the browser title shows product name.
8. Browse navigation tree. There can be small delay expanding second, fourth, etc level of topics. Verify branches expand correctly.
9. Verify help UI background is yellow, and green in the toolbars.
10. Verify fonts are bold in the toolbars, and italic in the rest of the UI.
11. Launch "Window"->"Preferences". Open "Workbench"->"Capabilities preference page. Select all capabilities and deselect "Development".
12. Re launch Help. Verify no books are displayed and "Show All Topics" button is not displayed.
13. Type "active link below" (no quotes) in the search field in the browser, and search.
14. Choose a document titled "Active help" from the search results.
15. Click once "Click here for a Message" link at the bottom of the document.
16. Verify a message informing that active help is not enabled is displayed, and "Hello World" workbench dialog does not appear.
1. Launch eclipse passing "-dir rtl" option on the command line. Open Help.
2. Verify Help UI is rendered right to left.
1. Accessibility support should test for how the help view
2. uses system colors and fonts,
3. uses browser's accessibility support,
4. can be navigated using only the keyboard.
5. Note: Platform considerations for the accessibility tests:
6. on Windows things should work as described;
7. on Linux using the Mozilla browser adapter keyboard navigation works slightly different: Ctrl-Tab and Ctrl-Shift-Tab are to be replaced by Ctrl-F6 and Ctrl-Shift-F6 (this is for frame navigation, see below).
8. on Solaris/AIX/HP, unless you use Mozilla, the default browser adapter for Netscape 4.x has very little accessibility support, both for fonts/colors and for keyboard navigation.
9. System colors and fonts:
10. Observe if the colors and fonts match your system settings. Window backgrounds for navigation views (Contents/Search Results/Links/Bookmarks) should match the system window color (usually white on Windows and gray on Linux). The toolbars should match the button face co lour (usually gray). The font should match the system icon font. Highlight co lour should match the system highlight co lour.
11. Change your system colors/font settings and see if the changes take effect.
12. On Windows, try the high contrast settings: Control Panel -> Accessibility Options -> Display - > Use high contrast.
13. Browser accessibility support:
14. Windows: in IE - > Tools-> Internet Options -> General ->Accessibility play with the settings for Format. Help should behave accordingly.
15. DO NOT turn off style sheet support, help will not work well.
16. Navigation with keyboard only:
Here are the keyboard navigation rules for help (as supported by browsers):
- To move to the next topic in the left frame, press TAB or
DOWN arrow.
- To move to the previous topic , press SHIFT-TAB or
UP arrow.
- To expand/collapse a tree node press RIGHT/LEFT arrow.
- Press Enter to select a topic and have its content displayed
- To scroll all the way up/down press HOME/END.
- To go back/forward press ALT-LEFT/RIGHT ARROW
- To go to the next frame (there are quite a number of frames in the help
system) press CTRL-TAB (On Mozilla 1.2 press
Ctrl-F6).
- To move to previous frame, press SHIFT-CTRL-TAB (On Mozilla
>1.2 press Ctrl-Shift-F6).
- To move to content frame, press ALT-K, and press Tab to place focus inside
the topic
- To print the current page or active frame, press CTRL-P.
17. F1 infopop keyboard accessibility:
18. Press F1 (on GTK - Ctrl-F1, on carbon - Help key) in the workbench Navigator view (Resources perspective). This should launch the infopop with some text and two related links. Focus should be on the first link ("Views"). Click and the help view should open to the selected topic.
19. Get back to the workbench and press F1 again, in the Navigator view. When the infopop comes up, press down/up arrows (or tab) to cycle around the links. Press Esc to dismiss the infopop.
20. On Windows, use Windows Narrator (or JAWS if installed ), repeat the same tests and see if description an links read out correctly.
In addition to the eclipse workbench help scenario, there are two other help uses scenarios: standalone help and info-center (server based) help.
1. Assuming eclipse is installed as d:\eclipse, change directory to d:\eclipse and run the following command: java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter -command start -data infocenter -port 8888
2. Open a browser and navigate to http://localhost:8888/help. You should see the help system, but without the links and bookmarks tabs.
3. Define a working set, search help. Close the browser and reopen. Verify working sets are remembered.
4. Perform ad-hoc testing or follow the steps for the regular workbench scenarios, with the exception of bookmarks, infopop and active help.
5. Shutdown the infocenter by running: java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Infocenter -command shutdown -data infocenter
1. Assuming eclipse is installed as d:\eclipse, change directory to d:\eclipse and run the following command: java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Help -command displayHelp -data standalone
2. The above command should automatically open the browser so you can browse the help. Perform ad-hoc testing or follow the steps in the regular workbench scenario, with the exception of infopop and active help.
3. Shutdown the standalone help by running: java -cp plugins/org.eclipse.help.base_3.1.0.jar org.eclipse.help.standalone.Help -command shutdown -data standalone
1. Disable javascript in the browser that is used by the default browser adapter (normally, that's IE on Windows, Mozilla on Linux and Netscape6+ on others)
2. Launch help and you should see a simple 3-frame layout with links instead of tabs and just the synchronize navigation button available. Books are always expanded and there is no state preservation across views (i.e. when switching between contents/links/search/bookmarks) the page always reloads)
3. Try ad-hoc testing or follow the regular workbench scenario steps above.
4. Instead of step 1, you can launch Netscape 4.7 and navigate to the help system URL. To get this URL, right click in the help browser and select "Properties". Check what the URL is.
1. Help/Search
2. Search for "Creating Rich Client"
3. Expected result: The cheat sheet "Creating a rich client application" should show in the matches at or near the top of the list of search results..
4. Expected Result: The icon should be overlapping blue and white rectangles.
5. Double click on this cheat sheet in the search results.
6. If this is not a clean workbench and you have run this test before restart all tasks using the view menu.
7. Expected result: The cheatsheet opens in the cheat sheet view and displays two panes, a tree and a section containing a description of the cheat sheet and a hyperlink.
8. Resize the cheat sheet view so that it is taller than it is wide.
9. Expected result: The tree appears above the description.
10. Resize the cheat sheet view so that it is wider than it is tall.
11. Expected result: The tree appears to the left of description.
12. Click on the link "Go to Create a plug-in"
13. Expected result: "Create a plug-in is selected in the tree and its description is displayed, with a hyperlink to "Start working on this task".
14. Start the cheat sheet by clicking on the hyperlink and complete the Introduction and the following step.
1. Unzip the self testing cheat sheet from http://www.eclipse.org/eclipse/platform-ua/testing/test_files.zip anywhere on your hard drive.
2. Help -> Cheatsheets ...
3. Expected result: the cheatsheet selection dialog opens.
4. Press the (?) button in the lower left.
5. Expected Result: Context help is opened which is specific to this dialog (This dialog is used to launch a cheat sheet.).
6. Select the radio button "Select a cheat sheet from a file"
7. Hit the Browse... button.
8. Browse to TestCheatSheets.xml in the files you just unzipped.
9. Hit OK to open the cheat sheet.
10. Expected result: The composite cheat sheet opens.
11. If this is not a clean workbench and you have run this test before restart all tasks using the view menu.
12. Work through the steps of the cheat sheet until the root task shows a checkmark (i.e. is complete) and verify that it works in the way it describes itself.
1. Help -> CheatSheets
2. Expected Result: The Cheat Sheet Selection dialog is opened.
3. Select the radio button "Select a cheat sheet from the list"
4. Select the cheat sheet "Java Development/Hello World Application" and hit OK.
5. Expected result: The cheat sheet opens.
6. Complete the introduction and the first steps.
7. Expected result: Next step is "Create a Java project"
8. Click the "Click to perform" hyperlink.
9. Expected result: A dialog titled "New Java Project" opens with the cheatsheet docked to the right of the dialog.
10. Cancel out of this dialog.
1. Click on the cheat sheet view menu.
2. Expected result: 5 cheat sheets are shown in the dropdown menu as well as "Launch Other ..." and "Restart all tasks". One of the cheat sheets in the list is "Building a Rich Client Application", select that menu option.
3. Expected result: Building a rich client Application is opened, the selected task is "Create a plug-in" and the introduction and first step have been completed.