Difference between revisions of "Mylyn/Manual Testing"

Revision as of 12:36, 14 May 2007

This document contains the manual testing check-list. Use red to indicate failures.

Execution Environments

• Ensure launch works with JRockit

Documentation

• Help > Help Contents > Mylar > New and Noteworthy [ ensure updated to latest release]

Team

• Open Corresponding Task Action
  • Incoming change set classic mode
  • Incoming change set models mode
  • Outgoing change set classic mode
  • Outgoing change set models mode
  • History view element with old format (e.g. TasksUiPlugin comment before 2006-08)
  • History view element with new format (e.g. TasksUiPlugin comment after 2006-11)

Bugzilla

Test opening of repository tasks (both in and not in Task List). M1 refactoring could have disrupted this.  

Ensure changing summary in local task editor doesn't create additional header (https://bugs.eclipse.org/bugs/show_bug.cgi?id=180749 bug#180749)

3.2.2. Ensure that opening editor with missing task data doesn't block startup. 

• Offline Reports
  • Ensure that when a bug report is opened offline that has no offline data the bug page reads: "Task data not available, please synchronize and reopen."
  • In the case of migration ensure that offline reports still open correctly (if not lost completely).
• Navigate > Open Repository Task, enter bad ID, Should result in invalid id error dialog
• 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)

• Bugzilla Task Editor (Rich editor)
  • When opening remote tasks (ie. from search results view) ensure that posting authenticates properly
  • 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 (March 30, 2007) Cut & Copy from menu broken in Linux due to loss of focus on text

• 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) [2.0 M1]

• 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.
• Synchronizing while disconnected should not put errors in the eclipse log
• Reports > Task list notification
  • Open, modify, save, should have outgoing decorator
    • Case clear outgoing: confirmation dialog should pop up
      • Case confirm: outgoing decorator should go away
      • Case deny: outgoing decorator should remain
    • 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)
  • 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)
  • 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.
  • Open, modify, save, should have outgoing decorator, open report in external browser, add comment
    • Case open: Outgoing decorator remains
    • Case Submit: Mid air collision...synchronize via menu
      • Case Synchronize: 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

• 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. [2.0M3] Getting double notification upon synch
• 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 comment in the editor 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.
• Opening a repository task that has no repository should display warning indicating that the repository must be created.

Task List

• test proxy support using new platform proxy settings 177320

• test auto construction of repositories from clean workspace 174864

• Do a manual refactoring test (change name/url of existing repository) of tasks
• File -> Export -> Mylar Task Data
• File -> Import -> Mylar Task Data
  • Test importing with task in active state
• Data directory change (via Mylar preferences page)
  • Ensure all data is migrated including context and backup folders and contained data
  • Ensure that if 'load' is selected that the target folder is loaded and not overwritten
• 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 Mylar 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)
  • (March 30, 2007) On Linux under 3.2, dragging to external text attempts to open context, dragging to external explorer copies details
• Lazy loading
  • Startup with Task List in fast view mode with a task active, ensure no errors in log
• FOR 0.9 Ensure orphaned tasks span workbench restart
• Delete category that contains a task scheduled for today, task should be revealed in Archive (immediately, not after restart/refresh/etc).

• Test clean install with task list only installed then with only one connector installed. Ensure adding task repository doesn't cause errors.

Trac

• Create Repositories:
  • http://trac.edgewall.org/trac (Trac 0.9 and higher)
    • Validate settings
    • -> Message: Repository is valid
  • http://mylar.eclipse.org/tractest
    • Username: tests@mylar.eclipse.org
    • Password: <password>
    • Repository is valid
    • -> Message: Authentication credentials are valid.
    • -> XML-RPC is selected

• Query (Trac 0.9)
  • Add query for http://trac.edgewall.org
  • -> Repository attributes are displayed in query dialog
  • Select "0.10" for version
  • Finish
  • -> Tickets are marked as incoming
  • -> Notifications popup
  • Open ticket
  • -> Ticket is opened in browser pane
  • -> Ticket is marked as synchronized

• Search
  • Open search
  • Select http://mylar.eclipse.org/tractest
  • -> progress bar is shown while attributes are updated
  • -> attributes are displayed
  • Select http://trac.edgewall.org
  • Search for "ticket" in summary on edgewall.org
  • Double click search result
  • -> Browser is opened
  • Open another search result through context menu
  • -> Browser is opened

• Query and offline handler (XML-RPC)
  • Add query for all tickets in "component1" for http://mylar.eclipse.org/tractest
  • -> All tickets are marked as incoming
  • Edit ticket summary of any ticket in web browser and submit
  • Synchronize query
  • -> Only edited ticket is synchronized and marked as incoming
  • Reopen query
  • -> "component1" is selected

• Create Ticket in Rich Editor (XML-RPC)
  • Select New > Repository Task for http://mylar.eclipse.org/tractest
  • Enter summary and description
  • Select Add to Task Category: root
  • Press Create New
  • -> New Ticket is added to task list
  • Open ticket
  • -> summary and description are correct

• Edit Ticket with Rich Editor (XML-RPC)
  • Open any ticket from query
  • Edit summary and save
  • -> Ticket is marked as outgoing
  • Edit ticket summary in web browser and submit
  • Synchronize ticket in task list
  • -> Conflict warning popus up
  • Select "No" (keep local changes)
  • -> Task is marked as conflicting

• Context attachments (XML-RPC)
  • Activate ticket
  • Create new Java project
  • Open Java file
  • Attach context on active task
  • Retrieve context
  • -> Context is displayed in wizard
  • -> Context is loaded

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

...