diff options
| author | cvs2git | 2006-08-22 19:23:43 +0000 |
|---|---|---|
| committer | cvs2git | 2006-08-22 19:23:43 +0000 |
| commit | 11032262b8e8ee47658d393cfdcef3faec8a9414 (patch) | |
| tree | bdf5e78efa712215d767e3297ee73d60b64b19b0 | |
| parent | 1ed09a7ee3f6aeb833117422047409b70cf3f9c1 (diff) | |
| download | org.eclipse.mylyn-R_0_6_1_prerefactoring.tar.gz org.eclipse.mylyn-R_0_6_1_prerefactoring.tar.xz org.eclipse.mylyn-R_0_6_1_prerefactoring.zip | |
This commit was manufactured by cvs2svn to create tagR_0_6_2R_0_6_1_prerefactoring
'R_0_6_1_prerefactoring'.
Sprout from master 2006-07-27 18:51:24 UTC mkersten 'Progress on: 151896: Trac connector: update dependency to Apache XML-RPC 3.0'
Delete:
org.eclipse.mylyn.tests/tests-manual.html
| -rw-r--r-- | org.eclipse.mylyn.tests/tests-manual.html | 206 |
1 files changed, 0 insertions, 206 deletions
diff --git a/org.eclipse.mylyn.tests/tests-manual.html b/org.eclipse.mylyn.tests/tests-manual.html deleted file mode 100644 index a6e7ba3d..00000000 --- a/org.eclipse.mylyn.tests/tests-manual.html +++ /dev/null @@ -1,206 +0,0 @@ -<html> - <body> - <h2>Mylar Manual Tests</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>Migration: Ensure that offline reports still open correctly (if not - lost completely).</li> - <li>Bug Editor Hyperlinking - <font color="#FF6600">URL Hyperlinks</font>, Bug hyperlinks (bug# 123, bug 12312, duplicate bug links), stack trace file links</li> - </ul> - <ul> - <li>Test of Search > Search... > Bugzilla Search tab - <ul> - <li>Requires that a bugzilla repository is - configured in the Mylar Task Repositories view</li> - <li>Test opening non-local report</li> - <li>Test opening report with local task</li> - </ul> - <li>Test Bugzilla Query Wizard</li><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>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><font color="#FF6600">Upon submitting new bug editor user is - presented with credentials error dialog (June 29, 2006 [0.6] Posting - Error - Ensure proper configuration... dialog occurs rather than - correct error message)</font></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><font color="#FF6600">Error Dialog presented on product update or selection of Next: The - user name or password you entered is not valid... (June 29, 2006 - [0.6] Posting Error - Ensure proper configuration... dialog occurs - rather than correct error message)</font></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>Make sure submission of comment doesn't remove - dependencies</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) - (June 29, 2006 [0.6])</font></li> - <li>Synchronize Reports (invalid userid and password)<ul> - <li>Report Download Failed Dialog: Ensure proper repository - configuration in Task Repositories view.</li> - </ul></li> - <li>Product configuration caching<ul> - <li>Run new bug wizard</li> - <li>Restart, rerun, products should appear immediately</li> - </ul></li> - <li>Synchronizing while disconnected should not put errors in the - eclipse log<ul> - <li><font color="#FF6600">java.net.UnknownHostException: - mylar.eclipse.org<br> - at java.net.PlainSocketImpl.connect(Unknown Source)<br> - at java.net.Socket.connect(Unknown Source)<br> - at sun.net.NetworkClient.doConnect(Unknown Source)<br> - at sun.net.www.http.HttpClient.openServer(Unknown Source)<br> - at sun.net.www.http.HttpClient.openServer(Unknown Source)<br> - at sun.net.www.http.HttpClient.<init>(Unknown Source)<br> - at sun.net.www.http.HttpClient.New(Unknown Source)<br> - at sun.net.www.http.HttpClient.New(Unknown Source)<br> - at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown - Source)<br> - at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown - Source)<br> - at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)<br> - at - org.eclipse.mylar.internal.bugzilla.core.AbstractReportFactory.collectResults(AbstractReportFactory.java:66)<br> - at - org.eclipse.mylar.internal.bugzilla.core.RepositoryReportFactory.populateReport(RepositoryReportFactory.java:58)<br> - at - org.eclipse.mylar.internal.bugzilla.core.BugzillaRepositoryUtil.getBug(BugzillaRepositoryUtil.java:91)<br> - at - org.eclipse.mylar.internal.bugzilla.ui.tasklist.BugzillaOfflineTaskHandler.downloadTaskData(BugzillaOfflineTaskHandler.java:66)<br> - at - org.eclipse.mylar.provisional.tasklist.SynchronizeTaskJob.run(SynchronizeTaskJob.java:82)</font></li> - </ul> - </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 - presented asking if user wants to refresh and reopen.</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> - </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> - </ul> - - <p><b>SDK Integration</b></p> - <ul> - <li>Problems 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> |