| <html> |
| <body> |
| <h2> </h2> |
| <p align="center"><font size="4">DEPRECATED</font></p> |
| <p><font size="4">This information is now maintained here: http://wiki.eclipse.org/index.php/Mylar_Testing</font></p> |
| <h2> </h2> |
| <h2><strike>Mylar Manual Tests</strike></h2> |
| <p><b>Help</b></p> |
| <ul> |
| <li><b> </b>Help > Help Contents > Mylar > New and Noteworthy |
| [ ensure updated ]</li> |
| </ul> |
| <p><b>Bugzilla Client</b></p> |
| |
| <ul> |
| <li>Offline Reports<ul> |
| <li><font color="#FF6600">Ensure that when a bug report is opened offline that has no offline |
| data the bug page reads: "Repository task data not available, please |
| synchronize." (Aug 17, 2006 [0.6.2] page reads "Could not download |
| task data..."</font></li> |
| <li>In the case of migration ensure that offline reports still open correctly (if not |
| lost completely).</li> |
| </ul> |
| </li> |
| <li>Editor Hyperlinking - URL Hyperlinks, Bug hyperlinks (bug# 123, bug 12312, |
| task# 1, task 12, duplicate bug links), stack trace links</li> |
| <li>Editor menu/commands - Cut/Copy/Paste/Select-all from menu and |
| using shortcut keys</li> |
| <li>Repository Search (Search > Search... > Repository Search tab)<ul> |
| <li>Repository search page<ul> |
| <li>Ensure warning if no repository exists.</li> |
| <li>Cycle through available repository search pages ensuring |
| that they populate with the last search performed on the |
| respective repository</li> |
| <li>Ensure other repository types search pages appear when |
| selected</li> |
| </ul></li> |
| <li>Repository Search Results View<ul> |
| <li>Test opening non-local report (Bug should open in bugzilla |
| editor (blue bin icon) and the browser tab should be available)</li> |
| <li>Test opening report with local data (Bug should open in |
| bugzilla editor (clipboard with blue bin overlay icon) and the |
| Planning tab and Browser tab should be available)</li> |
| </ul></li> |
| </ul></li> |
| <li>Bugzilla Query Wizard</li> (Tasklist)<ul> |
| <li>Create new query</li> |
| <li>Open query to see that parameters are still there</li> |
| <li>Check for error handling (enter invalid number in max returned etc)</li> |
| </ul></li> |
| <li>New Bug submission (valid credentials)<ul> |
| <li>Test new bug submission for each Bugzilla server version</li> |
| </ul></li> |
| <li>Update of Repository Configuration<ul> |
| <li>Test from TaskRepositoriesView context menu</li> |
| <li>Test from BugzillaProductPage</li> |
| <li>A dialog should be produced in either case when an io or login |
| exceptions occur.</li> |
| <li>Configuration caching<ul> |
| <li>Run new bug wizard, update products...</li> |
| <li>Restart eclipse, rerun wizard, products should appear immediately</li> |
| </ul></li> |
| </ul> |
| </li> |
| <li>New Bug submission (invalid credentials)<ul> |
| <li>Remove username and password from a repository configuration in the |
| Task Repositories view</li> |
| <li>Initiate new repository task action</li> |
| <li>Select repository with missing credentials</li> |
| <li>Upon submitting new bug editor user is |
| presented with credentials error dialog</li> |
| </ul></li> |
| <li>New Bug submission (invalid password)<ul> |
| <li>Make repository password invalid in Task Repositories view.</li> |
| <li>Initiate new repository task action.</li> |
| <li>Select repository with invalid password</li> |
| <li>Error Dialog presented on product update or selection of Next: The |
| user name or password you entered is not valid...</li> |
| </ul></li> |
| <li>Submission of changes to a Bugzilla report should result in all |
| parent queries being re-synchronized as well as the task itself being |
| synchronized</li> |
| <li>Ensure submission of comment doesn't remove any depends on / blocks |
| bugs</li> |
| <li>Submission of changes to existing bug with invalid repository |
| credentials<ul> |
| <li>Mylar Bugzilla Client Dialog: Bugzilla could not post your bug since your login name or password is incorrect. |
| Ensure proper repository configuration in Task Repositories view.</li> |
| </ul></li> |
| <li><font color="#FF6600">Bug Compare (ensure attribute compare works) |
| (July 31, 2006 [0.6.1] - Compare button removed)</font></li> |
| <li>Synchronize from context menu (invalid userid and password)<ul> |
| <li><font color="#FF6600">Report Download Failed Dialog: Ensure proper repository |
| configuration in Task Repositories view. (Aug 17, 2006 [0.6.2] - |
| currently upon failure the task remains italic and if the error is |
| not an io related exception it is logged.)</font></li> |
| </ul></li> |
| <li>Synchronizing while disconnected should not put errors in the |
| eclipse log</li> |
| <li>Reports > Task list notification<ul> |
| <li>Open, modify, save, should have outgoing decorator<ul> |
| <li>Case synchronize: should get option to override local changes<ul> |
| <li>If overriding, overlay and changes go away</li> |
| <li>If no override, get conflict icon to show</li> |
| </ul></li> |
| <li>Case open: should retain outgoing overlay</li> |
| <li>Case edit and save again: outgoing overlay remains (should |
| not receive conflict warning)</li> |
| <li>Case submit: outgoing overlay should disappear (should be no incoming |
| upon synchronize)</li> |
| </ul></li> |
| <li>Task in CONFLICT state<ul> |
| <li>Case open: remains with conflict decorator</li> |
| <li>Case synchronize: should get option to override local changes<ul> |
| <li>Case overriding: overlay and changes go away</li> |
| <li>Case no override: changes remain, conflict decorator appears</li> |
| </ul></li> |
| <li>Case edit: Currently state switches to OUTGOING which is |
| correct for now because we migrate their comment into the new |
| report<br> </li> |
| </ul> |
| <p></li> |
| <li>Query hits not yet downloaded<ul> |
| <li>Case open: report downloaded (task icon appears), no decoration</li> |
| <li>Case synchronize: report downloaded (task icon appears), no |
| decoration<br> </li> |
| </ul></li> |
| <li>Open report in external editor and add a comment.<ul> |
| <li>Case synchronize: incoming decoration should appear on task<ul> |
| <li>Case open: task opens with new content, no decoration</li> |
| <li>Case open (bug editor already open): |
| User presented with dialog asking if they want to reopen |
| with latest version</li> |
| <li>Case Background Synchronization incoming state remains</li> |
| </ul></li> |
| <li>Case open: task opens with offline content, user asked if |
| they want to refresh with incoming content.<br> </li> |
| </ul></li> |
| <li>Open, modify, save, should have outgoing decorator, open report in |
| external browser, add comment<ul> |
| <li>Case open: Outgoing decorator remains</li> |
| <li>Case Submit: Dialog:Possible problem posting Bugzilla |
| report... HTML mid-air collision dialog<ul> |
| <li>Overwrite changes dialog (if yes - SYNCHRONIZED, if no - |
| CONFLICT)</li> |
| </ul></li> |
| <li>Case synchronize: should get option to override local changes<ul> |
| <li>If overriding, overlay and changes go away</li> |
| <li>If no override, get conflict icon to show<br> </li> |
| </ul></li> |
| </ul></li> |
| <li>Copy report to a local category, repeat above tests ensuring |
| decoration always </li> |
| <li>Copy report to root category, repeat tests ensuring decoration |
| always matches</li> |
| </ul></li> |
| <li>Check that auto background synchronize works<ul> |
| <li>Ensure that new hits (i.e. reports created using web ui) appear in |
| query after auto sync</li> |
| <li>Ensure that incoming on existing tasks appears after auto |
| synchronization </li> |
| </ul></li> |
| <li>If editor open and task gets incoming, dialog |
| should be presented asking if user wants to refresh and reopen.</li> |
| <li>Check that if changes are made to the notes field of the Planning |
| editor that save still works (editor doesn't remain dirty).</li> |
| <li>Ensure that when offline reports file is deleted, tasks don't |
| suddenly all have incoming status upon synchronizing</li> |
| <li>Reports > Outline View<ul> |
| <li>Clicking on comments in outline view should cause editor to |
| scroll to respective bug on page.</li> |
| </ul></li> |
| <li>DnD Attachments: Ensure all of the following launch the new attachment wizard with |
| the appropriate file specified. |
| <ul><li>Drag a file from the workspace to the attachments section or new comment box.</li> |
| <li>Drag a file from a different application (or desktop) onto the attachments section |
| or new comment box.</li> |
| <li>Drag a region of text from any application (eg. a web browser) onto the attachments |
| section or new comment box.</li> |
| </ul></li> |
| </ul> |
| <p><b>Task List</b></p> |
| <ul> |
| <li>File -> Export -> Mylar Task Data: ensure it works</li> |
| <li>File -> Import -> Mylar Task Data:<ul> |
| <li>Test importing with task in active state</li> |
| </ul> |
| </li> |
| <li>Make a task, make it active, move it to the |
| archive (remove from root category) - file should remain visible in task list</li> |
| <li>Task List Auto-Archive</li> |
| <li>Addition and removal of files from change sets</li> |
| <li>Mylar context sensitive JUnit unit tests</li> |
| <li>Ensure internal browser tab can be disabled (via preferences)</li> |
| <li>Drag and Drop<ul> |
| <li>From category to category: move</li> |
| <li>From query to category: copies</li> |
| <li>Task to external text: copies details</li> |
| <li>Task to external explorer: copies context file (<font color="#FF6600"> |
| July 31, 2006 [0.6.1] - if context doesn't exist need to disable drop?</font> |
| )</li> |
| </ul> |
| |
| </li> |
| </ul> |
| |
| <p><b>SDK Integration</b></p> |
| <ul> |
| <li>Problems view</li> |
| <li>Debug view</li> |
| <li>Eclipse native tasks view</li> |
| <li>History view -> context menu -> Open Corresponding Task</li> |
| </ul> |
| |
| <p><b>Java</b></p> |
| <ul> |
| <li>Run JUnit context test without interesting tests: should get message</li> |
| <li>Run JUnit contexts test with interesting tests, should run</li> |
| <li>Do above for PDE JUnit tests</li> |
| <li>Ensure code folding works properly</li> |
| </ul> |
| <p>PDE</p> |
| <ul> |
| <li>...</li> |
| </ul> |
| </body></html> |
