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 "Mylyn/Manual Testing"
< Mylyn
(→Trac) |
|||
Line 114: | Line 114: | ||
==Trac== | ==Trac== | ||
− | ... | + | * Create Repositories: |
+ | ** http://trac.edgewall.org/trac (Trac 0.9 and higher) | ||
+ | ** http://mylar.eclipse.org/tractest, tests@mylar.eclipse.org (XML-RPC) | ||
+ | |||
+ | * Query (Trac 0.9) | ||
+ | ** Add query for milestone 0.10 | ||
+ | ** -> Repository attributes are displayed in query dialog | ||
+ | ** Open ticket | ||
+ | ** -> Ticket is opened in browser pane | ||
+ | |||
+ | * Query and offline handler (XML-RPC) | ||
+ | ** Add query for all tickets in "component1" | ||
+ | ** -> All tickets are marked as incoming | ||
+ | ** Edit ticket summary in web browser and save | ||
+ | ** -> Edited ticket is marked as synchronized | ||
+ | ** Synchronize query | ||
+ | ** -> Only edited ticket is synchronized and marked as incoming | ||
+ | ** Reopen query | ||
+ | ** -> "component1" is selected | ||
+ | |||
+ | * Contexts (XML-RPC) | ||
+ | ** Activate ticket | ||
+ | ** Open Java file | ||
+ | ** Attach context | ||
+ | ** Retrieve context | ||
+ | ** -> Context is displayed in wizard | ||
+ | ** -> Context is loaded | ||
+ | |||
+ | * Search | ||
+ | ** Search for "ticket" on edgewall.org | ||
+ | ** Double click ticket | ||
+ | ** -> Error message | ||
+ | ** Open ticket through context menu | ||
+ | ** -> Browser is opened | ||
==SDK Integration== | ==SDK Integration== |
Revision as of 19:19, 25 August 2006
Mylar Help
- Help > Help Contents > Mylar > New and Noteworthy [ ensure updated to latest release]
Bugzilla
- Offline Reports
- 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...")
- In the case of migration ensure that offline reports still open correctly (if not lost completely).
- Editor Hyperlinking - URL Hyperlinks, Bug hyperlinks (bug# 123, bug 12312, task# 1, task 12, duplicate bug links), stack trace links
- Editor menu/commands - Cut/Copy/Paste/Select-all from menu and using shortcut keys
- Repository Search (Search > Search... > Repository Search tab)
- Repository search page
- Ensure warning if no repository exists.
- Cycle through available repository search pages ensuring that they populate with the last search performed on the respective repository
- Ensure other repository types search pages appear when selected
- Repository Search Results View
- Test opening non-local report (Bug should open in bugzilla editor (blue bin icon) and the browser tab should be available)
- 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)
- Repository search page
- Bugzilla Query Wizard (Tasklist)
- Create new query
- Open query to see that parameters are still there
- Check for error handling (enter invalid number in max returned etc)
- New Bug submission (valid credentials)
- Test new bug submission for each Bugzilla server version
- Update of Repository Configuration
- Test from TaskRepositoriesView context menu
- Test from BugzillaProductPage
- A dialog should be produced in either case when an io or login exceptions occur.
- Configuration caching
- Run new bug wizard, update products...
- Restart eclipse, rerun wizard, products should appear immediately
- New Bug submission (invalid credentials)
- Remove username and password from a repository configuration in the Task Repositories view
- Initiate new repository task action
- Select repository with missing credentials
- Upon submitting new bug editor user is presented with credentials error dialog
- New Bug submission (invalid password)
- Make repository password invalid in Task Repositories view.
- Initiate new repository task action.
- Select repository with invalid password
- Error Dialog presented on product update or selection of Next: The user name or password you entered is not valid...
- Submission of changes to a Bugzilla report should result in all parent queries being re-synchronized as well as the task itself being synchronized
- Ensure submission of comment doesn't remove any depends on / blocks bugs
- Submission of changes to existing bug with invalid repository credentials
- 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.
- Bug Compare (ensure attribute compare works) (July 31, 2006 [0.6.1] - Compare button removed)
- Synchronize from context menu (invalid userid and password)
- 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.)
- Synchronizing while disconnected should not put errors in the eclipse log
- Reports > Task list notification
- Open, modify, save, should have outgoing decorator
- Case synchronize: should get option to override local changes
- If overriding, overlay and changes go away
- If no override, get conflict icon to show
- Case open: should retain outgoing overlay
- Case edit and save again: outgoing overlay remains (should not receive conflict warning)
- Case submit: outgoing overlay should disappear (should be no incoming upon synchronize)
- Case synchronize: should get option to override local changes
- Task in CONFLICT state
- Case open: remains with conflict decorator
- Case synchronize: should get option to override local changes
- Case overriding: overlay and changes go away
- Case no override: changes remain, conflict decorator appears
- Case edit: Currently state switches to OUTGOING which is correct for now because we migrate their comment into the new report
- Query hits not yet downloaded
- Case open: report downloaded (task icon appears), no decoration
- Case synchronize: report downloaded (task icon appears), no decoration
- Open report in external editor and add a comment.
- Case synchronize: incoming decoration should appear on task
- Case open: task opens with new content, no decoration
- Case open (bug editor already open): User presented with dialog asking if they want to reopen with latest version
- Case Background Synchronization incoming state remains
- Case open: task opens with offline content, user asked if they want to refresh with incoming content.
- Case synchronize: incoming decoration should appear on task
- Open, modify, save, should have outgoing decorator, open report in external browser, add comment
- Case open: Outgoing decorator remains
- Case Submit: Dialog:Possible problem posting Bugzilla report... HTML mid-air collision dialog
- Overwrite changes dialog (if yes - SYNCHRONIZED, if no - CONFLICT)
- Case synchronize: should get option to override local changes
- If overriding, overlay and changes go away
- If no override, get conflict icon to show
- Copy report to a local category, repeat above tests ensuring decoration always
- Copy report to root category, repeat tests ensuring decoration always matches
- Open, modify, save, should have outgoing decorator
- Check that auto background synchronize works
- Ensure that new hits (i.e. reports created using web ui) appear in query after auto sync
- Ensure that incoming on existing tasks appears after auto synchronization
- If editor open and task gets incoming, dialog should be presented asking if user wants to refresh and reopen.
- Check that if changes are made to the notes field of the Planning editor that save still works (editor doesn't remain dirty).
- Ensure that when offline reports file is deleted, tasks don't suddenly all have incoming status upon synchronizing
- Reports > Outline View
- Clicking on comments in outline view should cause editor to scroll to respective bug on page.
- DnD Attachments: Ensure all of the following launch the new attachment wizard with the appropriate file specified.
- Drag a file from the workspace to the attachments section or new comment box.
- Drag a file from a different application (or desktop) onto the attachments section or new comment box.
- Drag a region of text from any application (eg. a web browser) onto the attachments section or new comment box.
Task List
- File -> Export -> Mylar Task Data: ensure it works
- File -> Import -> Mylar Task Data:
- Test importing with task in active state
- Make a task, make it active, move it to the archive (remove from root category) - file should remain visible in task list
- Task List Auto-Archive
- Addition and removal of files from change sets
- Mylar context sensitive JUnit unit tests
- Ensure internal browser tab can be disabled (via preferences)
- Drag and Drop
- From category to category: move
- From query to category: copies
- Task to external text: copies details
- Task to external explorer: copies context file ( July 31, 2006 [0.6.1] - if context doesn't exist need to disable drop? )
- Lazy loading
- Startup with Task List in fast view mode with a task active, ensure no errors in log
Trac
- Create Repositories:
- http://trac.edgewall.org/trac (Trac 0.9 and higher)
- http://mylar.eclipse.org/tractest, tests@mylar.eclipse.org (XML-RPC)
- Query (Trac 0.9)
- Add query for milestone 0.10
- -> Repository attributes are displayed in query dialog
- Open ticket
- -> Ticket is opened in browser pane
- Query and offline handler (XML-RPC)
- Add query for all tickets in "component1"
- -> All tickets are marked as incoming
- Edit ticket summary in web browser and save
- -> Edited ticket is marked as synchronized
- Synchronize query
- -> Only edited ticket is synchronized and marked as incoming
- Reopen query
- -> "component1" is selected
- Contexts (XML-RPC)
- Activate ticket
- Open Java file
- Attach context
- Retrieve context
- -> Context is displayed in wizard
- -> Context is loaded
- Search
- Search for "ticket" on edgewall.org
- Double click ticket
- -> Error message
- Open ticket through context menu
- -> Browser is opened
SDK Integration
- Problems view
- Debug view
- Eclipse native tasks view
- History view -> context menu -> Open Corresponding Task
Java
- Run JUnit context test without interesting tests: should get message
- Run JUnit contexts test with interesting tests, should run
- Do above for PDE JUnit tests
- Ensure code folding works properly
PDE
...