> For the complete documentation index, see [llms.txt](https://docs.simplifyqa.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplifyqa.ai/admin-controls-and-configurations/manage-projects-and-users/project-settings/configure-auto-logging-of-defects.md).

# Configure Auto-logging of Defects

Auto-logging of defects is a feature in software testing tools that automatically creates defect reports when a test case fails. This process eliminates the manual effort required by testers to document and report defects, streamlining the entire testing process.

When a test case fails, the tool captures relevant information such as:

* **Test case ID and name**
* **Test steps and expected results**
* **Actual results and error messages**
* **Screenshots or logs**

This information is then used to automatically create a defect, which can be managed in defect management.

This document provides step-by-step instructions on how to configure the auto-logging of defects when a test case or test suite fails

### Steps to Configure Auto-Logging:

1. **Enable Auto-Logging**

* **Navigate to Project Settings:** Go to **Admin** > **Projects** > **\[Project Name]** > **Project Settings**.

<figure><img src="https://2640723101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxErCxeVwmOt7GY9s22U%2Fuploads%2FupBKEHzmEmRvD42jhCCW%2Fimage.png?alt=media&amp;token=0977b4d7-199d-4691-8781-610366e83510" alt=""><figcaption></figcaption></figure>

* Locate the option for 'Auto-Logging of Defects'.

<figure><img src="https://2640723101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxErCxeVwmOt7GY9s22U%2Fuploads%2FvBoL7GPccyeSiqhv35r8%2Fimage.png?alt=media&amp;token=1c1f6230-ca99-4072-b915-9d33bf5805db" alt=""><figcaption></figcaption></figure>

* Enable the toggle switch to activate the feature.

<figure><img src="https://2640723101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxErCxeVwmOt7GY9s22U%2Fuploads%2FlSUAMFp3psdPV3hI5RN9%2Fimage.png?alt=media&amp;token=e57417a1-66fb-4c67-98e1-eb5e9cbc31fb" alt=""><figcaption></figcaption></figure>

2. **Set Default Fields:**

* **Assignee:** Specify the default assignee for auto-logged defects.
* **Status:** Set the default status for newly created defects (e.g., "Open," "New").
* **Priority:** Define the default priority for auto-logged defects (e.g., "High," "Medium," "Low").
* **Labels:** Assign default labels to help categorise and filter defects (e.g., "Functional," "Performance", "Production").

<figure><img src="https://2640723101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxErCxeVwmOt7GY9s22U%2Fuploads%2FIkAoD1EGa6qLqVtICGfU%2Fimage.png?alt=media&amp;token=cdd32809-5e7e-4033-9c58-69d7c5aba071" alt=""><figcaption></figcaption></figure>

3. **Test the Configuration:**

* Execute a test case or test suite.
* When a test case or test suite fails verify that a new defect is automatically created in failed report and defect management with the correct information.
* Auto-logged defect would be tagged in the failed step of the respective execution report or can be accessed in defect management as well.

<figure><img src="https://2640723101-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMxErCxeVwmOt7GY9s22U%2Fuploads%2FBi9Ora6XyGCsaKpWtDsj%2F17.png?alt=media&amp;token=75edf093-6379-44cf-9b96-b1c17a4ac0c0" alt=""><figcaption></figcaption></figure>

* Check the default values for assignee, status, priority, and labels.
* Ensure that the mapping between test case and defect fields is accurate.

{% hint style="info" %}
**Additional Tips:**

* **Regular Review:** Periodically review the auto-logged defects to ensure it remains accurate and up-to-date.
* Auto-logging can create duplicate defects if multiple test cases fail for the same reason. Use this feature judiciously to prevent unnecessary clutter in your defect management.
  {% endhint %}