Testing

The primary purpose of the Testing page is to provide information on testing activity and to report and work with product defects. The Testing page displays queries for a Requirements, Defect Report, and Action Item artifact types that were defined in Project Tracker. For requirements and defects that are specific to the Testing subpage, the subpage in Lifecycle attribute for the artifact has been set to Testing.

Note: Unlike earlier subpages, you do not promote requirements from Testing to later subpages. Once a requirement has been coded and tested, it can be marked as complete.

You use the Testing page to complete the following tasks:

Finding requirements and action items that are relevant to the Testing subpage

The following procedures describe how to find requirements and action items that are relevant to the Testing subpage.

To view requirements associated with the Testing subpage:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing icon on the page navigation toolbar or the Testing link in the left navigation pane.
  4. In the Requirements column of the activity area, click one of the following.
    Note that the activity area is either directly below the page navigation toolbar or at the top of the page. It is the area with a light blue background:
    Add new - To enter a requirement that may be considered for inclusion in the product.
    View active requirements flagged for discussion - View requirements that have a Flagged for Discussion attribute value that is set to "Yes" and a Status attribute value of Submitted, Started, On hold, or Reopened.
    View active requirements currently in testing - To view requirements that have been accepted into the release and for which coding work can start or is in progress. For requirements that appear when you click this link, the value of the subpage in Lifecycle attribute is testing, and the value of the Accepted into Current subpage attribute is Yes. The value of the Status attribute is Submitted, Started, On hold, or Reopened.
    View active requirements ready for testing - To view requirements that have been proposed for the coding but have not yet officially been accepted into this subpage. For requirements that appear when you click this link, the value of the subpage in Lifecycle attribute is Testing, and the value of the Accepted into Current subpage attribute is No. The value of the Status attribute is Submitted, Started, On hold, or Reopened.
    View active requirements in any subpage - These requirements contain Status attributes with one of the following values selected: Submitted, Started, On hold, or Reopened.

To view defects associated with the Testing subpage:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing icon on the page navigation toolbar or the Testing link in the left navigation pane.
  4. In the Defect Reports column of the activity area, click one of the following.
    Note that the activity area is either directly below the page navigation toolbar or at the top of the page. It is the area with a light blue background:
    Add new - To enter a new defect that may be considered for this release.
    View active defect reports flagged for discussion - View defects that have a Flagged for Discussion attribute value that is set to "Yes" and a Status attribute value of Submitted, Started, On hold, or Reopened.
    View active defect reports currently in testing - To view defects that have been deemed necessary to be fixed. For these defects, the value of the subpage in Lifecycle attribute is Testing, and the value of the Accepted into Current subpage attribute is Yes. The value of the Status attribute is Submitted, Started, On hold, or Reopened.
    View active defect reports ready for testing - To view defects that have been found but have not yet officially been accepted into this subpage. For these defects, the value of the subpage in Lifecycle attribute is Testing, and the value of the Accepted into Current subpage attribute is No. The value of the Status attribute is Submitted, Started, On hold, or Reopened.
    View active defect reports in any subpage - These defects contain Status attributes with one of the following values selected: Submitted, Started, On hold, or Reopened.

To view action items associated with the Testing subpage:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing icon on the page navigation toolbar or the Testing link in the left navigation pane.
  4. In the Action Items column of the activity area, click one of the following.
    Note that the activity area is either directly below the page navigation toolbar or at the top of the page. It is the area with a light blue background:
    Add new action item - To enter an action item, for example, conducting a code review or uploading a nightly build results document.
    View active action items that are flagged for discussion - To view action items that have a Flagged for Discussion attribute value that is set to "Yes" and a Status attribute value of Submitted, Started, On hold, or Reopened.
    View active action items that are specific to testing - To view action items that have an Action Item Type attribute value of Testing, and a Status attribute value of Submitted, Started, On hold, or Reopened.
    View active action items of any type - To view action items that have a Status attribute value of Submitted, Started, On hold, or Reopened.

Adding and modifying requirements, defect reports, and action items on the Testing page

In the Testing phase of a project, you code new features, fix bugs, and indicate features that are ready to be promoted to the Testing phase.

During this phase, there may be one or more additional action items that you need to complete. You can add action items on this page. For example, you can add an action item that is a reminder to conduct a code review.

To add a requirement, defect, or action item that is returned on a query on the Testing page:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing link on the page navigation toolbar or in the left navigation pane.
  4. Click Add new in the activity area, in either the Requirement, Defect Report, or Action item column.
    The activity area is either directly below the page navigation toolbar or at the top of the page. It is the area with a light blue background.
  5. Enter the required information for the requirement, defect, or action item.
  6. If prompted, click Next.
  7. For a defect, in the Application Lifecycle section, select Testing from the subpage in Lifecycle drop-down list.
    For a requirement, in the Application Lifecycle section, select Definition from the subpage in Lifecycle drop-down list. (Typically, new requirements should be assigned to the beginning of the lifecycle.)
    For an action item, in the Submission Information section, select Testing from the Action Item Type drop-down list.
    This ensures the artifact is returned on a query issued from the Testing page.
  8. If you want the artifact to appear on a milestone query on the Project Management page, select the appropriate milestone from the Target Milestone drop-down list.
  9. Complete any other required information (marked with an asterisk, "*").
  10. Click Save Changes.

To indicate that testing can begin for a requirement or defect:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing link on the page navigation toolbar or in the left navigation pane.
  4. In the Requirements or Defect Report column in the activity area, click the Ready for Testing link.
    The activity area is either directly below the page navigation toolbar or at the top of the page. It is the area with a light blue background.
  5. From the query results page, click the link for the requirement or defect that you want to accept into the coding subpage.
  6. Ensure the following settings are applied to this artifact:
    - The value of the subpage in Lifecycle attribute set to Testing.
    - The value of Accepted Into Current subpage? is set to Yes.
    - The value of the Status attribute set to Submitted, Started, On hold, or Reopened.
  7. Click Save Changes.
    You can now view this artifact by clicking the Currently in Testing query link on the Testing landing page.

Indicating that coding needs to be done for a defect

If during testing you find a bug and create a new defect report artifact, you can set the value of its subpage in Lifecycle attribute to Code & Build. This causes the artifact to be returned on the Code & Build page, and it signals that coding should be done to fix the defect.

To ensure a requirement or a defect appears on the Testing page:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing icon in the page navigation toolbar or the left navigation pane.
  4. Click Add new and create a new defect report, or click the Currently in Testing link in the Requirements or Defect Report column of the activity area.
    The activity area is either directly below the page navigation toolbar or at the top of the page. It is the area with a light blue background.
  5. Select the requirement or defect that you want to indicate as requiring coding.
  6. In the Application Lifecycle section, select Code & Build from the subpage in Lifecycle drop-down list.
    Note that the Accepted Into subpage? attribute will be reset to No when you do this.
  7. Click Save Changes.

To generate a defect report based on a requirement that you have tested:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing icon on the page navigation toolbar or the Testing link in the left navigation pane.
  4. In the Action Items column of the activity area, click the link for a query that will return the customer case from which you want to generate a defect, requirement, or action item. The link for Active requirements currently in testing may be appropriate.
  5. Click the link for the requirement where you found a bug during testing.
  6. From the page for viewing the requirement, click Copy artifact.
  7. In the copy page, select the drop-down list for the current project, and click Defect Report.
  8. Click Continue.
    A third Copy Artifact page is displayed. This page lists all artifacts that these two artifact types have in common. These are the attributes that are copied.
  9. Click the Copy artifact(s) button.
  10. You may be prompted to provide a reason.
  11. To ensure that this defect report is visible to developers from the Code & Build page, click the query link in the Defect Report column, and change the subpage in Lifecycle for this defect report to Code & Build.

Reading test documentation and downloading templates

You can access project documentation from the Documentation table on the Testing page. If you are responsible for authoring test documents, you can download templates for these documents from this page and upload draft or completed documents to this page. You or the project administrator can also add new documentation templates to the list.

If you have a content developer role in the project (or have both VersionControl - Commit and VersionControl - Add permissions granted by an administrator), you can also add information to the this page as well as view this page. However, the project administrator may prefer to take requests for additions to this page and be the sole person who actually performs the updates.

The Documentation table on this page contains a View other project documents link. Clicking this link is equivalent to clicking the Documents and files link in the left navigation pane.

Important: If you experience any difficulty uploading documents on this page, ask your project administrator to be sure that two Subversion integrations settings are turned off for the project. The administrator should click the project link on the Projects page, clickEdit project > Tool configuration, then turn off the Message must name artifact and Committer must own artifact settings in the Subversion section of the page.

To view project documentation on the Testing page:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing link on the page navigation toolbar or the left navigation pane.
  4. Scroll to the Process Documents table.
  5. Click the link for the document that you want to read.

To download a project document template from the Testing page:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing link on the page navigation toolbar or the left navigation pane.
  4. In the Process Documents section, click the View document templates link.
  5. Click the link for the template that you want to edit.
  6. Save this file locally and edit it.

To add or update a project document on the Testing page:

  1. Click the Projects page.
  2. Click the link for a project that uses a project template.
  3. Click the Testing link on the page navigator.
  4. In the Process Documents section, click the Upload document link.
  5. Browse to the document that you want to upload.
  6. Click Save.
    Note that this document is saved in the project's version control repository. If you want to rename or delete this document, you must use your version control client.

Viewing and adding work products

On the Testing page, there are links in the activity area to various work products. The activity area is either directly below the page navigation toolbar or at the top of the page. It is the area with a light blue background.

A project administrator may have replaced the link to the test systems with live data. However, if this has not been done, you can configure these links. You can also add test documents at any time.

To upload test documents:

  1. Click the Projects page and click the link for the project where you want to add this documentation.
  2. Click Testing on the page navigation toolbar or in the left navigation pane.
  3. In the Work Products column of the activity area, click the appropriate link, for example View functional test documents.
    The activity area is either directly below the page navigation toolbar or at the top of the page. It is the area with a light blue background.
  4. On the Requirements Documents page, click Upload document.
  5. Browse for the file and click Save.

To configure the work products link to a test system:

  1. If you have not done so already, use Subversion to check out the project template directory.
    For example, you may check out My-Project/trunk/www/cn-project-pages
    Where My-Project is the name of the project you are working on.
  2. Use your version control tool to update the Testing top.html snippet.
    For example, using Subversion, this will be in My-Project/trunk/www/cn-project-pages/Stages/Testing/snippets/top.html
  3. Open the top.html file in an editor.
  4. In the section for work products, edit the following link:
    <div class="launch_icon"> 
    		Launch systems: 
    		</div> 
    		<!-- onclick="return launch(this.href, 1);" makes the link open in a small new window --> 
    		<!-- Use onclick="window.open(this.href); return false;" to make the link open in a normal-sized new window --> 
    		<!-- Edit the title to change tool tip -->
    		<ul>
    		<li><a href="/nonav/cn-project-pages/help/customizing_alm_links.html" 
    		onclick="return launch(this.href, 1);" title="Go to a Web-enabled performance test application 
    		[Note: link may open in new window]" class="helplink">Performance test system</a></li>
    		</ul>

    For example, you might substitute the following:

    <li><a href="http://www.your_url_here.com/" 
    		onclick="window.open(this.href); return false;" 
    		title="Go to a Web-enabled performance test application">
    		Requirements system</a></li>
    As shown in the example, you can change onclick="return launch(this.href, 1);" to onclick="window.open(this.href); return false;" to make the link open in a normal-sized browser window instead of the smaller-sized window.
    Remove onclick="return launch(this.href, 1);" if you do not want the link to open a page in a new browser window.
    Remove or edit title="Go to a Web-enabled performance test application [Note: link may open in new window]" if you do not want text to appear in a tool tip when the user moves the cursor over the link.
    Remove class="helplink" if you do not want the cursor to be a question mark icon for this link.
  5. Submit your changes.

Customizing the Resources links

At the bottom of the Testing landing page, you can provide information that points users to any other information that you think is relevant.

To edit the Resource Links table:

  1. If you have not done so already, use Subversion to check out the project template directory.
    For example, you may check out My-Project/trunk/www/cn-project-pages
    Where My-Project is the name of the project you are working on.
  2. Use Subversion to update the Testing bottom.html snippet.
    For example, using Subversion, this will be in My-Project/trunk/www/cn-project-pages/Stages/Testing/snippets/bottom.html
  3. Open the bottom.html file in an editor.
  4. In the section for resource links, edit a row in the table, such as the following:
    <tr class="a">
    <td>Customizing the ALM Baseline Project template</td>
    <td><a href="http://www.collab.net/training/alm/Customizing_ALM.doc" onclick="window.open(this.href); return false;" title="Note: link may open in new window">http://www.collab.net/training/alm/Customizing_ALM.doc</a></td>
    </tr>

    For example, you can remove onclick="window.open(this.href); return false;" if you do not want the link to open a page in a new browser window.
    Or, you can remove or edit " title="Note: link may open in new window"" if you do not want text to appear in a tool tip when the user positions the cursor over the link.
  5. Alternate between class="a" and class="b" to provide different shades of gray in the table.
  6. Using Subversion, update this file and commit the changes.