This topic describes how to submit defects from within Sprinter.
The following table describes the ways to submit a defect:
When you submit a defect using Sprinter's Smart Defect, you can indicate the type of information to automatically add to your defect:
After you select which information to include, the New Defect dialog opens with the selected information already entered in the defect's description. You then fill in the other defect fields and submit the defect.
For details on configuring the information to include in your defect, see Smart Defect Settings dialog box.
|New Defect||You can open the New Defect Details dialog box directly from Sprinter and manually fill in all the defect fields. The annotation is saved with the Sprinter test
|Link existing defect for ALM users||You can link to an existing defect in Application Lifecycle Management from Sprinter . The annotation is saved as a linked entity in Application Lifecycle Management.|
You can continue your test run without disrupting its flow by creating a Defect Reminder.
A defect reminder enables you to summarize the defect in your application. The reminder is included with the test results and can be viewed at the end of your test. You can then submit the defect later from the test Results. The same information you have available during the test is also available to you from the results. So you can include screen captures, movies, and step or action information in the defect at that time.
The following guidelines apply:
For ALM users, when you submit an ALM defect using Sprinter, the defect is created in the ALM server, domain, and project that you configured when you logged in.
For ALM Octane users, when you submit a defect using Sprinter, the defect is created in the Octane server, shared space, and workspace that you selected when you logged in.
When you submit a defect using Sprinter to an external system (not ALM), the defect is created in the DTS server and project that you configured in the DTS settings.