6.4. Creating an issue

6.4. Creating an issue
	Chapter 6. Execute

After the execution of a test case or test suite has been finished, an issue in an issue management system can be created. For this at least one issue management system has to be configured and defined for the selected project. How an issue management system is configured is described in Section 8.5.4, “ Issue Management ” , how an issue management system is defined for a project is explained in Section 5.1.2.7, “Editing the Issue Management Properties of a Project” .

The execution of a test case is described in Section 6.1.1, “ Run Single Test Case ” and the execution of a test suite is described in Section 6.1.2, “ Run Test Suite ” .

To create a new issue, click on the Create Issue button on the results page, that is displayed after the execution of a test case or test plan.

By default the system uses the credentials entered at the login screen to authenticate the user against the issue management system. If the credentials entered at login does not suffice and the issue management system has not yet been used during the session, Klaros-Testmanagement will request new authentication information in a dialog window. Otherwise, the user is directed directly to the issue creation page.

The content of the issue management page is mostly dependent on the used issue management system and its capabilities, but all pages for the different issue management systems have some elements in common:

Issue Management System	When there are more than one issue management systems are configured for the project, the issue management system where the new issue is created can be selected in the issue management system drop-down field.
Save	The Save button creates or updates an issue in the selected issue management system.
Cancel	The Cancel discards unsaved changes and goes back to the Execute a Single Test Case , or the Execute a Test Suite page.
New	After an issue has been saved an additional New button is provided to allow to create more than one issue.

For the JIRA issue tracker additionally the following fields are available:

Summary	A short summary of the issue.
Type	The type of the issue, e.g. a bug or an improvement.
Priority	The priority of the issue.
Components	The components of the system that are affected, multiple selections are allowed here.
Affected Versions	The version of the system in which the issue appeared, multiple selections are allowed here.
Fixed Versions	The version of the system in which the issue has been fixed. Multiple selections are allowed here.
Due Date	The date when the issue should be fixed.
Description	A longer description of the issue.
Test Environment	A description of the test environment in which the issue occurred.

Figure 6.12. Jira Issue Page

For the Trac issue tracker the following fields are available:

Summary	A short summary of the issue.
Type	The type of the issue, e.g. a defect or enhancement
Priority	The priority of the issue.
Components	The component of the system that is affected.
Version	The version of the system that is affected.
Milestone	The milestone of the system that is affected.
Description	A detailed description of the issue
Keywords	Keywords for the issue.

Figure 6.13. Trac Issue Page

For the Redmine issue tracker the following fields are available:

Summary	A short summary of the issue.
Issue Type	The type of the issue, e.g. a defect or enhancement
Priority	The priority of the issue.
Assignee	The assignee of the issue.
Version	The version of the system that is affected.
Category	The category of the system that is affected.
Milestone	The milestone of the system that is affected.
Description	A detailed description of the issue
Estimated time [hours]	The estimated time in hours for the issue.

Figure 6.14. Redmine Issue Page

For the Bugzilla issue tracker the following fields are available:

Summary	A short summary of the issue.
Platform	The paltform of the issue.
Importance	The priority and type of the issue.
Components	The components of the issue.
Version	The version of the system that is affected.
Milestone	The milestone of the system that is affected.
Description	A detailed description of the issue

Figure 6.15. Bugzilla Issue Page

For the Mantis issue tracker the following fields are available:

Summary	A short summary of the issue.
Priority	The priority and type of the issue.
Category	The category of the issue.
Version	The version of the system that is affected.
Description	A detailed description of the issue.
Additional Information	A text field for additional information about the issue.
Status	A current status of the issue.
Resolution	A current resultion of the issue.

Figure 6.16. Mantis Issue Page

	Tip
	To change the state of the related test case just activate the Update Test Case State? and choose the new state from the drop down box.

For a more detailed information about each field please consult the documentation of the respective issue management system.

The created issues can be inspected in the Issues section in the Evaluate section see Section 7.3, “Issues” for more details.


6.3. Import Results		Chapter 7. Evaluate