{"id":1141,"date":"2017-08-03T10:41:42","date_gmt":"2017-08-03T10:41:42","guid":{"rendered":"https:\/\/www.h2kinfosys.com\/blog\/?p=1141"},"modified":"2025-12-05T05:24:38","modified_gmt":"2025-12-05T10:24:38","slug":"what-is-defect-report","status":"publish","type":"post","link":"https:\/\/www.h2kinfosys.com\/blog\/what-is-defect-report\/","title":{"rendered":"What is Defect Report?"},"content":{"rendered":"\n<p>Software testing is not just about finding bugs it\u2019s about communicating them clearly, accurately, and professionally. No matter how skilled a tester is at identifying issues, the real value lies in how effectively those issues are documented and conveyed to developers. This is where a <strong>Defect Report<\/strong> becomes one of the most powerful tools in the QA process.<\/p>\n\n\n\n<p>A well-written defect report helps teams reproduce issues quickly, understand the impact, plan fixes, and deliver high-quality software. Poorly written ones create confusion, delays, rework, frustration, and even production failures.<\/p>\n\n\n\n<p>Whether you\u2019re a beginner preparing for <a href=\"https:\/\/www.h2kinfosys.com\/courses\/qa-online-training-course-details\/\">QA Tester Training<\/a> interviews or an experienced tester improving your reporting skills, this guide helps you understand <strong>what a defect report is, why it matters, the structure of a good report, and best practices<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Understanding the Definition: What Is a Defect Report?<\/strong><\/h2>\n\n\n\n<p>A <strong>Defect Report<\/strong>, also known as a <strong><a href=\"https:\/\/www.h2kinfosys.com\/blog\/bug-life-cycle\/\" data-type=\"post\" data-id=\"14247\">Bug Report<\/a><\/strong>, is a detailed document that records any flaw, issue, or unexpected behavior identified during software testing. It provides complete information about the defect what it is, where it occurs, how to reproduce it, its severity, impact, and supporting evidence.<\/p>\n\n\n\n<p>In simple terms:<\/p>\n\n\n\n<p>&#x1f449; <strong>A defect report is a written communication between QA and development teams that describes the problem so clearly that anyone can understand and reproduce it.<\/strong><\/p>\n\n\n\n<p>It acts as an official record of issues found during testing, ensuring nothing is missed, ignored, or misunderstood.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why Is a Defect Report Important?<\/strong><\/h2>\n\n\n\n<p>Defect reports are the backbone of structured testing. Without them, teams would rely on memory or informal verbal communication, which leads to:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Missed bugs<\/li>\n\n\n\n<li>Misinterpretations<\/li>\n\n\n\n<li>Delays in release<\/li>\n\n\n\n<li>Poor product quality<\/li>\n<\/ul>\n\n\n\n<p>A clear defect report provides multiple benefits:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Ensures Clear Communication<\/strong><\/h3>\n\n\n\n<p>A well-documented bug eliminates confusion between QA, developer, product owner, and business teams.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Improves Developer Productivity<\/strong><\/h3>\n\n\n\n<p>Developers can reproduce the issue faster when steps and environment details are clear.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Prioritizes Fixes Based on Impact<\/strong><\/h3>\n\n\n\n<p>Severity and priority help teams decide what must be resolved immediately vs later.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Acts as a Historical Record<\/strong><\/h3>\n\n\n\n<p>Defect reports help track recurring problems, regression issues, and improvement areas.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. Enhances Product Quality<\/strong><\/h3>\n\n\n\n<p>Clear documentation ensures bugs are fixed properly and reduces risk of defects leaking into production.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img fetchpriority=\"high\" decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2017\/08\/image-2.png\" alt=\"\" class=\"wp-image-32516\" style=\"width:416px;height:auto\" title=\"\" srcset=\"https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2017\/08\/image-2.png 1024w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2017\/08\/image-2-300x225.png 300w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2017\/08\/image-2-768x576.png 768w, https:\/\/www.h2kinfosys.com\/blog\/wp-content\/uploads\/2017\/08\/image-2-150x113.png 150w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Key Components of a Good Defect Report<\/strong><\/h2>\n\n\n\n<p>A high-quality defect report must be <strong>complete, clear, consistent, and concise<\/strong>. Below are the essential fields included in most bug tracking systems (Jira, Bugzilla, Azure DevOps, QC\/ALM, Trello, etc.).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Defect ID<\/strong><\/h3>\n\n\n\n<p>A unique identifier automatically generated by the tool (e.g., BUG-1023).<br>Used for tracking and referencing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Title \/ Summary<\/strong><\/h3>\n\n\n\n<p>A one-line, crisp description of the defect.<\/p>\n\n\n\n<p><strong>Example:<\/strong><br>\u201cLogin button remains disabled even after entering valid credentials.\u201d<\/p>\n\n\n\n<p><strong>Tips:<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mention the affected function and behavior.<\/li>\n\n\n\n<li>Avoid vague titles like \u201cLogin issue\u201d or \u201cButton not working.\u201d<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Description<\/strong><\/h3>\n\n\n\n<p>A detailed explanation of the defect with context.<\/p>\n\n\n\n<p>Include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>What went wrong<\/li>\n\n\n\n<li>Where it occurred<\/li>\n\n\n\n<li>Expected behavior<\/li>\n\n\n\n<li>Actual behavior<\/li>\n<\/ul>\n\n\n\n<p><strong>Example:<\/strong><br>\u201cWhen the user enters valid email and password, the login button remains disabled. Expected behavior: the button should get enabled.\u201d<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Steps to Reproduce<\/strong><\/h3>\n\n\n\n<p>The <strong>most important<\/strong> part of any defect report.<\/p>\n\n\n\n<p>These steps must be:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Simple<\/li>\n\n\n\n<li>Sequential<\/li>\n\n\n\n<li>Easy to follow<\/li>\n<\/ul>\n\n\n\n<p><strong>Example:<\/strong><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open the login page<\/li>\n\n\n\n<li>Enter a valid email<\/li>\n\n\n\n<li>Enter a valid password<\/li>\n\n\n\n<li>Observe the login button<\/li>\n<\/ol>\n\n\n\n<p>If the issue is not reproducible, note the frequency (e.g., \u201cOccurs 2\/5 times\u201d).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. Environment Details<\/strong><\/h3>\n\n\n\n<p>Include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Browser version<\/li>\n\n\n\n<li>Device<\/li>\n\n\n\n<li>Operating system<\/li>\n\n\n\n<li>Build version<\/li>\n\n\n\n<li>Test environment URL<\/li>\n<\/ul>\n\n\n\n<p>This helps developers replicate the issue in the exact setup.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>6. Severity<\/strong><\/h3>\n\n\n\n<p>Defines <strong>impact<\/strong> of the defect.<\/p>\n\n\n\n<p>Common levels:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Critical<\/strong> \u2013 System crash, data loss<\/li>\n\n\n\n<li><strong>High<\/strong> \u2013 Major functionality broken<\/li>\n\n\n\n<li><strong>Medium<\/strong> \u2013 Partial or moderate impact<\/li>\n\n\n\n<li><strong>Low<\/strong> \u2013 Minor issue, UI defect<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>7. Priority<\/strong><\/h3>\n\n\n\n<p>Defines <strong>urgency<\/strong> of fixing the defect.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>P1 \u2013 Immediate fix needed<\/strong><\/li>\n\n\n\n<li><strong>P2 \u2013 Fix in next sprint<\/strong><\/li>\n\n\n\n<li><strong>P3 \u2013 Fix in backlog<\/strong><\/li>\n<\/ul>\n\n\n\n<p>Severity \u2260 Priority<br>A UI defect may be low severity but high priority before a client demo.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>8. Screenshots \/ Videos \/ Logs<\/strong><\/h3>\n\n\n\n<p>Evidence increases credibility and eliminates guesswork.<\/p>\n\n\n\n<p>Attach:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Screenshots<\/li>\n\n\n\n<li>Console logs<\/li>\n\n\n\n<li>Error codes<\/li>\n\n\n\n<li>Network logs<\/li>\n\n\n\n<li>Video recordings<\/li>\n<\/ul>\n\n\n\n<p>Tools like Loom, Snagit, and browser dev tools help capture issues.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>9. Expected vs Actual Result<\/strong><\/h3>\n\n\n\n<p>Clear comparison helps developers understand the impact instantly.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>10. Module \/ Function \/ Feature<\/strong><\/h3>\n\n\n\n<p>Mention the exact area where issue is found.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>11. Test Data Used<\/strong><\/h3>\n\n\n\n<p>Useful for issues involving:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Payment<\/li>\n\n\n\n<li>User roles<\/li>\n\n\n\n<li>Authentication<\/li>\n\n\n\n<li>Dynamic data<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>12. Assigned To<\/strong><\/h3>\n\n\n\n<p>The developer or team responsible for fixing the defect.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>13. Status<\/strong><\/h3>\n\n\n\n<p>Shows where the defect is in the lifecycle.<\/p>\n\n\n\n<p>Common statuses include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>New<\/li>\n\n\n\n<li>Assigned<\/li>\n\n\n\n<li>In Progress<\/li>\n\n\n\n<li>Fixed<\/li>\n\n\n\n<li>Retest<\/li>\n\n\n\n<li>Closed<\/li>\n\n\n\n<li>Reopened<\/li>\n\n\n\n<li>Deferred<\/li>\n\n\n\n<li>Not a Bug<\/li>\n\n\n\n<li>Duplicate<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>How to Write an Excellent Defect Report: Examples and Best Practices<\/strong><\/h2>\n\n\n\n<p>A strong defect report saves time, reduces frustration, and speeds up resolution. Follow these proven guidelines:<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>1. Be Clear and Specific<\/strong><\/h2>\n\n\n\n<p>Avoid:<br>Page not working.\u201d<br>Checkout page freezes after clicking \u2018Proceed to Pay\u2019 on Chrome 120.\u201d<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>2. Provide Exact Reproduce Steps<\/strong><\/h2>\n\n\n\n<p>No matter how obvious the issue seems to you, developers need clarity.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>3. Avoid Emotionally Charged or Blaming Language<\/strong><\/h2>\n\n\n\n<p>The developer forgot validation again.\u201d<br>Validation is missing for the email field on the <a href=\"http:\/\/registration form\" rel=\"nofollow\">registration form<\/a>.\u201d<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>4. Include Attachments<\/strong><\/h2>\n\n\n\n<p>Images and videos communicate faster than text.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>5. Focus on Facts, Not Assumptions<\/strong><\/h2>\n\n\n\n<p>Stick to observed behavior. Don\u2019t guess the root cause.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>6. Use Proper Formatting<\/strong><\/h2>\n\n\n\n<p>Use bullets, numbers, and spacing for readability.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>7. Always Check for Duplicates<\/strong><\/h2>\n\n\n\n<p>Search existing defects before logging a new one to avoid clutter.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>8. Validate Test Data Properly<\/strong><\/h2>\n\n\n\n<p>Incorrect test data leads to invalid defect reports.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>9. Mention Frequency<\/strong><\/h2>\n\n\n\n<p>If intermittent, specify occurrence rate (e.g., 3\/10 times).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>10. Reproduce Before Reporting<\/strong><\/h2>\n\n\n\n<p>Never log a defect without confirming it is consistent and valid.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Sample Defect Report Template<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Defect ID:<\/strong> AUTO-2345<\/h3>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Title:<\/strong> Login button remains disabled after entering valid credentials.<\/h3>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Description:<\/strong><\/h3>\n\n\n\n<p>The login button on the web application does not get enabled after entering valid email and password. This prevents the user from accessing the account.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Environment:<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Browser: Chrome 120<\/li>\n\n\n\n<li>OS: Windows 11<\/li>\n\n\n\n<li>Build Version: 5.8.2<\/li>\n\n\n\n<li>URL: test.xyz.com<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Severity:<\/strong> High<\/h3>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Priority:<\/strong> P1<\/h3>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Steps to Reproduce:<\/strong><\/h3>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Open the login page<\/li>\n\n\n\n<li>Enter a valid email<\/li>\n\n\n\n<li>Enter a valid password<\/li>\n\n\n\n<li>Observe the login button remains disabled<\/li>\n<\/ol>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Expected Result:<\/strong><\/h3>\n\n\n\n<p>Login button should be enabled once valid input is provided.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Actual Result:<\/strong><\/h3>\n\n\n\n<p>Login button stays disabled, blocking user login.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Attachments:<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Screenshot.png<\/li>\n\n\n\n<li>Screenrecording.mp4<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Status:<\/strong> New<\/h3>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Assigned To:<\/strong> UI Development Team<\/h3>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Common Mistakes QA Testers Make in Defect Reporting<\/strong><\/h2>\n\n\n\n<p>Understanding mistakes helps you avoid them:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. Lack of Detail<\/strong><\/h3>\n\n\n\n<p>\u201cPage not loading\u201d is not enough. Provide steps, URL, logs, and frequency.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Vague Titles<\/strong><\/h3>\n\n\n\n<p>Titles like \u201cIssue found\u201d waste developer time.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. Missing Expected Result<\/strong><\/h3>\n\n\n\n<p>Developers cannot fix something unless they know the intended behavior.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. Using Wrong Severity or Priority<\/strong><\/h3>\n\n\n\n<p>Incorrect classification leads to poor sprint planning.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. Not Reproducing Defect Before Reporting<\/strong><\/h3>\n\n\n\n<p>Intermittent or false defects damage QA credibility.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>6. Unclear Screenshots<\/strong><\/h3>\n\n\n\n<p>Blurred or partial images slow down debugging.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>7. Duplicate Defects<\/strong><\/h3>\n\n\n\n<p>Clutters the backlog and confuses teams.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why Defect Reporting Skills Matter for QA Careers<\/strong><\/h2>\n\n\n\n<p>A QA tester\u2019s value is measured not only by the number of bugs they find but by how well they <strong>communicate defects<\/strong>. These skills directly impact:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Team efficiency<\/li>\n\n\n\n<li>Developer relationships<\/li>\n\n\n\n<li>Sprint planning<\/li>\n\n\n\n<li>Release timelines<\/li>\n\n\n\n<li>Product stability<\/li>\n\n\n\n<li>Your professional reputation<\/li>\n<\/ul>\n\n\n\n<p>In many interviews, hiring managers evaluate defect reporting skills through:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Practical test scenarios<\/li>\n\n\n\n<li>Sample bug reports<\/li>\n\n\n\n<li>Jira exercises<\/li>\n\n\n\n<li>Video-based evidence analysis<\/li>\n<\/ul>\n\n\n\n<p>Clear defect reporting reflects your analytical thinking, attention to detail, and professionalism qualities every successful QA must master.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Real-World Example: Impact of Poor vs Good Defect Reporting<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Scenario 1: Poor Report<\/strong><\/h3>\n\n\n\n<p>\u201cApp crashes sometimes.\u201d<\/p>\n\n\n\n<p>Developers spend hours:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reproducing<\/li>\n\n\n\n<li>Hunting logs<\/li>\n\n\n\n<li>Understanding context<\/li>\n\n\n\n<li>Asking QA for details<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Scenario 2: Good Report<\/strong><\/h3>\n\n\n\n<p>\u201cApp crashes when user imports a 50MB CSV file on Android 14 using Samsung S22. Crash occurs after clicking \u2018Upload\u2019 step 3. See logs and video attached.\u201d<\/p>\n\n\n\n<p>Developers:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Reproduce issue in 2 minutes<\/li>\n\n\n\n<li>Identify memory leak<\/li>\n\n\n\n<li>Apply fix quickly<\/li>\n<\/ul>\n\n\n\n<p><strong>Good defect reporting accelerates development.<\/strong><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Tools Commonly Used for Logging Defects<\/strong><\/h2>\n\n\n\n<p>Below are the most popular tools in QA teams:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Jira<\/strong><\/li>\n\n\n\n<li><strong>Azure DevOps<\/strong><\/li>\n\n\n\n<li><strong>Bugzilla<\/strong><\/li>\n\n\n\n<li><strong>Mantis<\/strong><\/li>\n\n\n\n<li><strong>QC \/ ALM<\/strong><\/li>\n\n\n\n<li><strong>YouTrack<\/strong><\/li>\n\n\n\n<li><strong>Redmine<\/strong><\/li>\n\n\n\n<li><strong>Asana<\/strong><\/li>\n\n\n\n<li><strong>Trello<\/strong><\/li>\n\n\n\n<li><strong>ClickUp<\/strong><\/li>\n<\/ul>\n\n\n\n<p>Most of these tools support:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Custom workflow<\/li>\n\n\n\n<li>Priority\/severity management<\/li>\n\n\n\n<li>Attachments<\/li>\n\n\n\n<li>Dashboards<\/li>\n\n\n\n<li>Notifications<\/li>\n\n\n\n<li>Sprint tracking<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>A <strong>Defect Report<\/strong> is more than just a document it\u2019s a bridge between testers and developers. The quality of this communication directly impacts how fast bugs get fixed and how reliable the final product becomes. The best QA testers are not just good at identifying bugs; they excel at <strong>explaining<\/strong> them clearly.<\/p>\n\n\n\n<p>Mastering defect reporting helps you:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Improve team collaboration<\/li>\n\n\n\n<li>Build trust with developers<\/li>\n\n\n\n<li>Reduce rework<\/li>\n\n\n\n<li>Deliver bug-free releases<\/li>\n\n\n\n<li>Stand out in QA interviews<\/li>\n<\/ul>\n\n\n\n<p>Strong defect reporting is a core skill for every QA professional\u2014and one of the most powerful ways to elevate your career.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Software testing is not just about finding bugs it\u2019s about communicating them clearly, accurately, and professionally. No matter how skilled a tester is at identifying issues, the real value lies in how effectively those issues are documented and conveyed to developers. This is where a Defect Report becomes one of the most powerful tools in [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":32518,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[],"class_list":["post-1141","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-qa-interview-questions-answers"],"_links":{"self":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1141","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/comments?post=1141"}],"version-history":[{"count":2,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1141\/revisions"}],"predecessor-version":[{"id":32519,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/posts\/1141\/revisions\/32519"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media\/32518"}],"wp:attachment":[{"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/media?parent=1141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/categories?post=1141"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.h2kinfosys.com\/blog\/wp-json\/wp\/v2\/tags?post=1141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}