TS 71 CDevBugtracking

Kenai Bugtracking Test Specification

Author: Michal Strnad
Version: 7.1
Last update: 2011/10/14
Introduction: This document is test specification for NetBeans Bugtracking support.


Comments:Jira bugtracking system support is not a part of distribution - it is available only via update center. All testcases in this specification are written as Bugzilla related but all tests must be executed similarly for JIRA.

Contents


Test suite: Connectors to Bugzilla system

Purpose: This suite covers tests for connections to bugzilla.
Setup: The bugzilla server must be available for some tests or Bugzilla at Kenai is required for other testcases.

  1. Issue Trackers node availability
    1. Open the Services Window (main menu Window|Services).
    2. Check that the "Issue Trackers" node is there at the bottom of the tree
    3. The only popup menu item of Issue Trackers node is "Create Issue Tracker..."
    • EXPECTED RESULT: The popup menu appears properly; check also that Shift-F10/Escape invokes/cancels the popup menu.
  1. Connect to bugzilla testing URLs available at http://netbeans.org/bugzilla
    1. Open the Services Window (main menu Window|Services).
    2. For each of bugzilla URLs available repeat following steps
    3. In Issue Trackers node invoke the popup menu and select Create Issue Tracker..
  1. Already existing name
    1. Select one of the node created in previous testcase
    2. Invoke popup menu and call Edit
    3. Copy the value from Issue Tracker Url textfield
    4. Push Escape to cancel the dialog
    5. In Issue Trackers node invoke the popup menu and select Create Issue Tracker..
    6. Paste the value to the "Name" field
    • EXPECTED RESULT: Red coloured "Issue tracker with the same name already exists" should appear below the Validate button. OK button should be disabled. Cancel the dialog.
  1. Already registered bugzilla
    1. Select one of the node created in former testcase
    2. Invoke popup menu and call Edit
    3. Copy the value from Issue Tracker Url textfield
    4. Push Escape to cancel the dialog
    5. In Issue Trackers node invoke the popup menu and select Create Issue Tracker..
    6. Set the "Name" textfield to "TestingBZ"
    7. "Missing URL" text appears in red below the Validate button
    8. Paste the value to the "Issue Tracker Url" field
    • EXPECTED RESULT: Red coloured "Issue tracker with the same url already exists" should appear below the Validate button. OK button should be disabled. Cancel the dialog.
  1. Wrong URL format
    1. Invoke "Find Issues..." from popup menu of some "Issue Trackers" subnode
    2. Follow the "New" link by the right side of the Issue Tracker combo box
    3. In the "Create Issue Tracker" dialog type the Name to "NB-org1"
    4. Type non bugzilla URL (www.netbeans.org) to the "Issue Tracker Url" textfield
    5. Leave other fields blank
    • EXPECTED RESULT: Red coloured "Wrong URL format" should appear below the Validate button. OK button is disabled. Cancel the dialog.
  1. Host not found
    1. Invoke "Find Issues..." from popup menu of some "Issue Trackers" subnode
    2. Follow the "New" link by the right side of the Issue Tracker combo box
    3. In the "Create Issue Tracker" dialog type the Name to "NB-org2"
    4. Type non bugzilla URL (http://www.netbeans.org) to the "Issue Tracker Url" textfield
    5. Leave other fields blank
    6. Push "Validate" button
    • EXPECTED RESULT: Red coloured "Host not found" should appear below the Validate button. OK button is disabled. Cancel the dialog.
  1. Cancel deletion of an issue tracker
    1. Go to the "Services" window
    2. Expand the "Issue Trackers" node
    3. Select the node with name that was created in former testcases
    4. Invoke popup menu
    5. Select "Remove..."
    6. Push Cancel button at the OK/Cancel dialog that appears
    • EXPECTED RESULT: The dialog disappears but the node stays there in the Services Window.
  1. Delete an issue tracker
    1. Go to the "Services" window
    2. Expand the "Issue Trackers" node
    3. Select the node with name that was created in former testcases
    4. Invoke popup menu
    5. Select "Remove..."
    6. Push OK button at the OK/Cancel dialog that appears
    • EXPECTED RESULT: The dialog disappears and then the node disappears in the Services Window.
  1. Report issue to a valid bugzilla w/o credentials
    1. Create issue tracker to http://kenai-test.cz.oracle.com/bugzilla (without credentials, just put the name and url)
    2. Invoke popup menu action "Report an Issue..."
    3. Fill in the Summary and Description fields
    4. Push "Submit Issue"
      • EXPECTED RESULT: Issue is now created. Verify it by Issue ID.
  1. The "new" disabled of kenai project
    1. Open a Kenai project and display the Find Issues panel for this project
      • EXPECTED RESULT: The "Issue Tracker" combo box and also the "new" is disabled for every Find Issues panel related to kenai project. It is only enabled for standalone (non kenai) bugtrackings.


Test suite: Find Issues lists

Purpose: This suite covers tests for Find Issues panel.
Setup: The bugzilla server must be available for some tests or Bugzilla at Kenai is required for other testcases.

  1. Check the lists default state
    1. Select a subnode of Issue Trackers node in Services window
    2. Invoke popup menu and select Find Issues...
    3. Find Issues panel appears in editor pane as a new tab
    4. Look at the Product, Component, Version, Status, Resolution and Priority lists
    • EXPECTED RESULT: These lists must be filed with values from bugzilla - check that only proper fields are displayed.
  1. Select a single Product
    1. Select a product in the Product list box
    • EXPECTED RESULT: Check that when changing a product the Component list is filed with proper values. Also Version list is changing properly.
  1. Product multiselect
    1. Select 2 or more products at the Product list
    • EXPECTED RESULT: Check that all required components and versions appear in the appropriate list component.



Test suite: Saved Queries

Purpose: This suite covers tests for saving queries.
Setup: The bugzilla server must be available for some tests or Bugzilla at Kenai is required for other testcases.

  1. Cancel the query save
    1. In Find Issues page select some Product and Component push Search button
    2. The list of bugs appears at the bottom of the page
    3. Push "Save this query"
    4. Specify the Name and push Cancel
    • EXPECTED RESULT: The "Save Query" dialog disappears and no query is saved.
  1. Save Query dialog's Help button
    1. In Find Issues page select some Product and Component push Search button
    2. The list of bugs appears at the bottom of the page
    3. Push "Save this query"
    4. Specify the Name and push "Help" button
    • EXPECTED RESULT: Help window appears and the help page for topic "Issue Tracking: Save Issue Query Dialog Box" is displayed.
  1. Save query
    1. In Find Issues page select some Product and Component push Search button.
    2. The list of bugs appears at the bottom of the page.
    3. Push Save this query.
    4. Specify the Name and push Save.
    • EXPECTED RESULT: The query appears as a link at the top right part of proper Find Issues panel.
  1. Save query for a kenai project
    1. In Find Issues page select some Product and Component push Search button
    2. The list of bugs appears at the bottom of the page.
    3. Push Save this query.
    4. Specify the Name and push Save.
    • EXPECTED RESULT: The query appears as a link at the top right part. There appears also new subnode of the Issues node of kenai project in Kenai Dashboard - the name of the node is equal to the assigned query name.
  1. Existing query
    1. In Find Issues page select some Product and Component push Search button
    2. The list of bugs appears at the bottom of the page
    3. Push "Save this query"
    4. Specify the Name of already existing query and push OK
    • EXPECTED RESULT: "Query with the same name already exists" appears at the top of the dialog.
  1. Save as All Issues in kenai project
    1. In Find Issues page select some Product and Component push Search button
    2. The list of bugs appears at the bottom of the page
    3. Push "Save this query"
    4. Type "All Issues" as the query name and push OK
    • EXPECTED RESULT: "Query with the same name already exists" appears at the top of the dialog.
  1. Save as My Issues in kenai project
    1. In Find Issues page select some Product and Component push Search button
    2. The list of bugs appears at the bottom of the page
    3. Push "Save this query"
    4. Type "My Issues" as the query name and push OK
    • EXPECTED RESULT: "Query with the same name already exists" appears at the top of the dialog.
  1. Cancel removal of a query
    1. Save a query and name it "Query for removal"
    2. Push "Remove Query"
    3. In the confirmation dialog push Cancel button
    • EXPECTED RESULT: The confirmation dialog disappears but the query stays there.
  1. Remove query
    1. Display "Query for removal"
    2. Push "Remove Query"
    3. In the confirmation dialog push OK button
    • EXPECTED RESULT: The confirmation dialog disappears and the query is removed form the Find Issues page and from the Kenai dashboard Issues node too.
  1. Mark all issue as unseen
    1. Select a saved query which contains a few issues
    2. In the query page toggle the last column so that it displays the flag icon
    3. Push "Mark All Issues As Seen"
    • EXPECTED RESULT: Flag icons disappear from the table.
  1. Refresh a query
    1. Select a query
    2. Make changes by browser to some issue contained in the query list
    3. Push "Refresh" at the top of the query page
    • EXPECTED RESULT: The issue appears in blue and the Recent Changes column contains the number of changes and the description of made changes.
  1. Modify a query
    1. Display a query and push "Modify Query" at the top of the page
    2. Make some changes - e.g. select some priority to exclude some issues
    3. Push "Save Changes" button
    4. Push "Refresh"
    • EXPECTED RESULT: The table of issues changes properly (less issues is displayed).


Test suite: File and modify issues

Purpose: This suite covers tests reporting and modifying of issues.
Setup: The bugzilla server must be available for some tests or Bugzilla at Kenai is required for other testcases.

  1. File issue
    • EXPECTED RESULT: .
  1. Add a comment to issue
    • EXPECTED RESULT: .
  1. Add attachment to issue
    • EXPECTED RESULT: .
  1. Modify issue fields
    • EXPECTED RESULT: .


Test suite: Versioning related

Purpose: This suite covers tests related to versioning support.
Setup: The bugzilla server must be available for some tests or Bugzilla at Kenai is required for other testcases.

  1. Apply patch
    • EXPECTED RESULT: .
  1. Save patch
    • EXPECTED RESULT: .


Test suite: Operations in Issue Views

Purpose: This suite covers tests for operations in Issue Views.
Setup: The bugzilla server must be available.

  1. Undo/Redo operations
    1. Open the Services Window (main menu Window|Services).
    2. Click "Issue Trackers" node at the bottom of the tree.
    3. Invoke the popup menu and click "Create Issue Tracker..." .
    4. Choose a unique "Name" and fill "Issue Tracker Url" with the url of the correct bugzilla system (for example https://bugzilla.mozilla.org).
    5. Push OK button.
    6. The subnode should appear in the Services Window.
    7. Invoke the popup menu over the subnode and click "Find Issues...".
    8. Select any "Product" and push "Search".
    9. Select any issue from the list that appears at the bottom of the window and double click on it.
    10. Find text area named "Add your comment:" and fill it with some text.
    11. After that should active function "Undo addition (Ctrl+Z)" in the toolbar.
    12. Click on it and verify that filled text was deleted.
    13. Repeat point number 10 and now try shortcut Ctrl+Z.
    14. This should have the same result like in the point 11 (delete text).
  1. Functionality Expand All/Collapse All
    1. Invoke the popup menu over the subnode from previous test case and click "Find Issues...".
    2. Select any "Product" and push "Search".
    3. Select issue from the list that have more comments than one and double click on it (try another issue if your selected doesn't have more comments than one).
    4. Move cursor over the name of author of the any comment and invoke popup menu by right click.
    5. Push "Collapse All".
    6. All comments should be collapse and only names of authors are displayed.
    7. Move cursor over the name of author of the any comment and invoke popup menu by right click.
    8. Push "Expand All".
    9. All comments should be expand and only names of authors are followed by comments.

Test suite: Bugzilla features

Purpose: This suite covers tests for operations with Bugzilla systems.
Setup: The testing bugzilla server must be available and we have the access to do changes.

  1. Reset Assignee to Default
    1. Open the Services Window (main menu Window|Services).
    2. Click "Issue Trackers" node at the bottom of the tree.
    3. Invoke the popup menu and click "Create Issue Tracker..." .
    4. Choose a unique "Name" and fill "Issue Tracker Url" with the url of the correct bugzilla system.
    5. Push OK button.
    6. The subnode should appear in the Services Window.
    7. Invoke the popup menu over the subnode from previous test case and click "Find Issues...".
    8. Select any "Product" and push "Search".
    9. Select any issue from the list and double click on it.
    10. Change field called "Assigned to:" to test@netbeans.org and push "Submit Changes".
    11. Check "Reassign to Default" and push "Submit Changes".
    12. Verify that field called "Assigned to:" contain default value.


  1. Open web browser directly from URL field
    1. Invoke the popup menu over the subnode from previous test case and click "Find Issues...".
    2. Select any "Product" and push "Search".
    3. Select any issue from the list and double click on it.
    4. Fill the field called "URL" with value "show_bug.cgi?id=ISSUE_ID" (value ISSUE_ID replace with real "Issue ID" issue that you selected).
    5. Click on "URL" label.
    6. URL "http://netbeans.org/bugzilla/show_bug.cgi?id=ISSUE_ID" (value ISSUE_ID should be replaced with real "Issue ID" issue that you selected) should be open in web browser.
  1. Added Time tracking

Setup: The testing bugzilla server must be available and we have the access to do changes. Also must be active feature "Time Tracking".

    1. Invoke the popup menu over the subnode from previous test case and click "Report Issues...".
    2. Fill "Summary" with "TestingOnly" and other fields with credentials of your choice and push "Submit Issue".
    3. Should be created new issue with name "TestingOnly". Verify that above "Attachments" are fields named: "Original Est.", "Current Est.", "Hours Worked", "Hours Left", "% Complete", "Gain" and "Deadline". No fields are filled.
    4. Fill the fields "Original Est." with number 50 and "Deadline" with some date.
    5. Fill the field "Add your comment:" and push "Submit Changes".
    6. Verify that fields have been filled correctly (Original Est. has value 50, Gain has also value 50 and deadline is as you chose)
    7. Fill the field "Hours Left" with number 40, field "Add your comment:" with some comment and push "Submit Changes".
    8. Verify that field "Current Est." contains number 40 and the field "Gain:" contains number 10.
    9. Fill the field "Hours Worked" with number 20, field "Add your comment:" with some comment and push "Submit Changes".
    10. Verify that label of field "Hours Worked" contains number 20, field "Gain:" contains number 30 and field "%Complete" contains number 50.
    11. Fill the field "Hours Worked" with number 20, field "Add your comment:" with some comment and push "Submit Changes".
    12. Verify that label of field "Hours Worked" contains number 40, field "Gain:" contains number 50 and field "%Complete" contains number 100.


Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo