LogoLogo
  • About SimplifyQA
  • Get Started with SimplifyQA
    • Agile & Non-Agile Framework
    • OS Support
    • SimplifyQA Hosting
      • On-premise Installation Guide
        • Pre-requisites
        • Installation Guide
      • Support and Resources
      • Training and Onboarding
    • Explore SimplifyQA for your Application Lifecycle Management
  • SimplifyQA Installation & Setup
    • Setup QAWizard
    • Register QAWizard
    • Setup Android Device
      • How to enable settings in android device?
      • How to register android device?
      • Setup emulators on Android Studio for automation in SimplifyQA
    • Setup iOS Device
      • How to setup iOS device in Apple Developer Account?
      • How to register iOS device?
  • Get to know your Workspace
    • Blueprint of SimplifyQA
    • Key Terminologies
    • Search/Global Search
      • How to use global search?
      • How to use advance search?
      • How to use column sort?
      • How to use column filters?
      • Add or remove columns
    • Rich Text Editor
    • Import & Export
    • Add Attachments
    • Add Linkages
    • Add Comments
    • Manage Cards in board view
    • Configure Watchlist
    • Track Edit History
    • Hierarchy Tree
  • Admin Controls & Configurations
    • Manage Projects & Users
      • Create Project and Invite Users
      • Project Settings
        • Create and Manage Custom Fields
      • Grant Admin Privilege to User
      • Invite/Add Users to Team
      • User Directory and Access Control
      • Configure Page Layout
      • Manage Roles and Privileges
      • Configure Auto-logging of Defects
    • Configure your clients
    • Password settings
  • Release & Sprints
    • Introduction to Releases
    • Create & Manage Release & Sprint
    • Start & Close a Sprint
  • Create and Manage your Requirements
    • Introduction to Requirement Management
    • Create & Manage Epic
    • Create & Manage Features
    • Create & Manage User Stories
  • Introduction to Test Management in SimplifyQA
    • Create a Manual Test Case in SimplifyQA
    • Create an Automation Test Case in SimplifyQA
    • Learn API Testing in SimplifyQA
      • Create an API Test Case in SimplifyQA
      • Quick Test the API
      • Validating API Responses
      • Understanding API Parameterisation
      • Save API Response Data
      • Achieve Data flow for E2E Testing
    • Create Hybrid Test Case in SimplifyQA
    • Leverage Re-usability in your Tests
    • Organise your Test Cases
    • Linking a Test Case to User Story
    • Linking a Test Case to Defect
    • Version Control your Test Case
    • Create a Copy of your Test Case
    • Copy Test Case to different Project
    • Conditional Statements
      • Decision Making Statement
      • Looping Statement
      • BREAK & CONTINUE Statement
    • Supported Actions
    • Utilising Mobile Inspector in SimplifyQA
  • Introduction to Script-less Recording of Test Case
    • Record a Web Test Case in SimplifyQA
    • Record an Android Test Case in SimplifyQA
      • Record an Android Test Case
    • Record Functions in SimplifyQA
    • Understand Object Recognition Mechanism & Self Healing in SimplifyQA
  • Test Data Management
    • Work with the Formulas to Optimise Test Data
    • Import and Export Test Data Sets
  • Introduction to Object Repository
    • Capture Objects for your Tests
    • Organise your Test Objects
    • Parameterise your Test Object Properties
  • Introduction to Parameters
    • Various Types of Parameters
    • Create and Utilise Parameters in your Test Case
    • Understanding Runtime Parameters
  • Defect Management
  • Marketplace
    • Integration with Project Management Tools
      • Integrating SimplifyQA with Jira
        • Configure Web-hooks
        • SimplifyQA Setup for Integration
          • Setup your Account for Jira Integration
          • Configuration in SimplifyQA Admin
          • Steps to Generate a Jira API Token
          • Steps to create SimplifyQA token
          • Steps to get Jira Account ID
          • Synchronisation Functionality Between SimplifyQA and Jira
          • Analyse Logs for Data Synchronisation
        • Mapping Fields for Issue Types
        • Viewing SimplifyQA Test Cases in Jira
  • Legal Documents
    • End-User License Agreement
Powered by GitBook
On this page
  1. Admin Controls & Configurations
  2. Manage Projects & Users

Configure Auto-logging of Defects

PreviousManage Roles and PrivilegesNextConfigure your clients

Last updated 1 month ago

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:

    • Go to Admin > Projects > [Project Name] > Project Settings.

  • Locate the option for "Auto-Logging of Defects".

  • Enable the toggle switch to activate the feature.

  1. 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").

  1. 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.

  • Check the default values for assignee, status, priority, and labels.

  • Ensure that the mapping between test case and defect fields is accurate.

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.