{"id":93,"date":"2022-04-26T16:41:09","date_gmt":"2022-04-26T11:11:09","guid":{"rendered":"https:\/\/legacit.com\/blog\/?p=93"},"modified":"2022-08-30T12:39:48","modified_gmt":"2022-08-30T07:09:48","slug":"7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us","status":"publish","type":"post","link":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/","title":{"rendered":"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us"},"content":{"rendered":"

It is obvious that nobody appreciates having their mistakes pointed out, but truth be told\u2013 this is what Quality Assurance specialists aka testers do on a daily basis. Developers often treat their apps and their code on a very personal level, in a similar way that painters consider their paintings or musicians, their riffs.<\/span><\/p>\n

So, how do our Quality Assurance Professionals<\/a> deal with developers, especially when they need to report a bug, and how do they avoid getting into possible conflicts?<\/span><\/p>\n

1. We always ensure it\u2019s a bug<\/b><\/h3>\n

Nobody likes to be in a situation like when there is this one person who claims that the team has done something wrong but, in reality, they didn\u2019t; now the team needs to waste time to prove themselves right and show that nothing had in fact gone wrong.<\/span><\/p>\n

No one wants to be that guy and specifically doesn\u2019t want to transform permanently into this person. In order for us to be sure, we always try reproducing the bug we\u2019ve just found. We evaluate it on other operating systems, devices, web browsers, or anything that can help us in being completely sure that the thing we\u2019ve encountered is indeed a bug.<\/span><\/p>\n

2. We avoid being the bad guy at all cost<\/b><\/h3>\n

Sometimes we get so excited upon finding a bug that we completely forget or ignore to check if we did everything correctly.<\/span><\/p>\n

Scenario 1:<\/span><\/p>\n

Tester – \u201cOh My God \u2013 Look, location sharing isn’t working!\u201d\u00a0<\/span><\/p>\n

Coder – \u201cOf course it isn\u2019t, you didn\u2019t give permission to the app to use your location!\u201d<\/span><\/p>\n

Scenario 2:<\/span><\/p>\n

Tester – \u201cI can\u2019t log in!\u201d\u00a0<\/span><\/p>\n

Coder – \u201cObviously not, the password was too short!\u201d<\/span><\/p>\n

Scenario 3:<\/span><\/p>\n

Tester – \u201cHey I reported this bug two weeks ago and it\u2019s still here!\u201d\u00a0<\/span><\/p>\n

Coder – \u201cOf course it is, you\u2019ve downloaded the older version.\u201d<\/span><\/p>\n

\u00a0We ensure that we avoid getting into such situations.<\/span><\/p>\n

3. We are always specific<\/b><\/h3>\n

It is important to be specific. This situation is similar to a scenario where a friend has met with an accident and we’re calling an ambulance \u2013 the more information we provide, the better help our friend will get.\u00a0<\/span><\/p>\n

Likewise, we report the build version, environment, web browser, OS version and type of device \u2013 these are necessary. We give it a clever and unique title, so that even a stranger could easily understand what is going on (we try keeping it short and sweet).<\/span><\/p>\n

4. We become the navigator<\/b><\/h3>\n

Once we have learnt how to reproduce a bug, we try not to hide it. It\u2019s no top secret knowledge! We explain to the developers how to find the bug and, we also explore if there are other ways to reach it. If yes, we include every single one of them.\u00a0 We become the coder\u2019s navigator, we never know where they might find a solution.<\/span><\/p>\n

Another crucial thing to mention is that we ensure that the preconditions that have to be met to find the bug are met. For instance, if we must be logged in, then to which account \u2013 standard, premium, or something else? or, if we happen to find a bug in a search module, was the search filtered or not? etc. This is all highly crucial information.<\/span><\/p>\n

5. It\u2019s best that we show it<\/b><\/h3>\n

If we happen to find a bug that has a pretty complex path, we record it step by step, instead of writing down 16 points with directions. We even try using both methods just to make sure that the explanation is clear, so that no one is forced to reach us to simply understand what the heck we actually had in mind while reporting this particular bug.<\/span><\/p>\n

6. We have an explanation on how it should be fixed<\/b><\/h3>\n

Once we\u2019ve checked and made sure that we\u2019ve found a bug, we try to explain how it should be corrected.<\/span><\/p>\n

We do our best to avoid giving vague information like \u2018the background colour on the settings screen is wrong.\u2019 We avoid making the developer go hunting to look for the proper one in the specifications that have been sent by the client months ago. We ensure that they fix bugs much much faster by giving them all the required information.\u00a0<\/span><\/p>\n

7. We are at our gentle best<\/b><\/h3>\n

As mentioned at the start \u2013 nobody appreciates having their mistakes pointed out, so we believe that it is important for us that we avoid being unnecessarily critical. We strongly believe that we are not censors, teachers or judges and we do not assess \u2013 we only help in ensuring quality.<\/span><\/p>\n

Developing an application can be a complex process that needs a lot of planning and focus. It is unreal to avoid mistakes (sometimes stupid, sometimes petty), bugs and crashes. We ensure that we do not report bugs with a sense of pride, and try to avoid using expressions such as \u201cno surprise\u201d \u201cofcourse\u201d or \u201cagain\u201d when telling people that something isn’t working as it should be.<\/span><\/p>\n

The most important thing that we bear in our mind is that we are a team and are working towards the same goal. There is no space or time for us to look down on anyone in the team, and we ensure that we have fun working together.<\/span><\/p>\n

To Wrap Up<\/b><\/h3>\n

We believe that following all the above steps have helped us become better Quality Assurance Professionals. These rules we follow are short, specific, sweet and gentle, and have improved the work ethic of everyone in our team, allowing us all to produce better applications and software.<\/span><\/p>\n

Legacit is an innovative Mobile App Development Company that provides expertise and consultation in the area of Application Development, Quality Assurance & Testing, and Cloud services, to name a few. We pride ourselves in being steps ahead of the competition in making use of up-to-date technology, empowering our projects in achieving high customer satisfaction by providing quality that is unparalleled.\u00a0<\/span><\/p>\n

If you are in search of Quality Assurance Professionals to help you in testing and maintaining the quality of the software you are developing, please feel free to call on the number 0484 4348888 to initiate a conversation with our experts. You can be assured that our experts have spent decades in this space!<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

It is obvious that nobody appreciates having their mistakes pointed out, but truth be told\u2013 this is what Quality Assurance specialists aka testers do on a daily basis. Developers often treat their apps and their code on a very personal level, in a similar way that painters consider their paintings or musicians, their riffs. So, how do our Quality Assurance Professionals deal with developers, especially when they need to report a bug, and how do they avoid getting into possible conflicts? 1. We always ensure it\u2019s a bug Nobody likes to be in a situation like when there is this one person who claims that the team has done something wrong but, in reality, they didn\u2019t; now the team needs to waste time to prove themselves right and show that nothing had in fact gone wrong. No one wants to […]<\/p>\n","protected":false},"author":1,"featured_media":94,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[39],"tags":[],"class_list":["post-93","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-qa-testing"],"yoast_head":"\n7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us - Legacit Infotech Pvt Ltd<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us\" \/>\n<meta property=\"og:description\" content=\"It is obvious that nobody appreciates having their mistakes pointed out, but truth be told\u2013 this is what Quality Assurance specialists aka testers do on a daily basis. Developers often treat their apps and their code on a very personal level, in a similar way that painters consider their paintings or musicians, their riffs. So, how do our Quality Assurance Professionals deal with developers, especially when they need to report a bug, and how do they avoid getting into possible conflicts? 1. We always ensure it\u2019s a bug Nobody likes to be in a situation like when there is this one person who claims that the team has done something wrong but, in reality, they didn\u2019t; now the team needs to waste time to prove themselves right and show that nothing had in fact gone wrong. No one wants to […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/\" \/>\n<meta property=\"og:site_name\" content=\"Legacit Infotech Pvt Ltd\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/legacit\" \/>\n<meta property=\"article:published_time\" content=\"2022-04-26T11:11:09+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-08-30T07:09:48+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"2560\" \/>\n\t<meta property=\"og:image:height\" content=\"1611\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"legacit\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"legacit\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/\"},\"author\":{\"name\":\"legacit\",\"@id\":\"https:\/\/legacit.com\/blog\/#\/schema\/person\/02819527e1d7c6582caa7261d9c88428\"},\"headline\":\"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us\",\"datePublished\":\"2022-04-26T11:11:09+00:00\",\"dateModified\":\"2022-08-30T07:09:48+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/\"},\"wordCount\":1048,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/legacit.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg\",\"articleSection\":[\"QA Testing\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/\",\"url\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/\",\"name\":\"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us - Legacit Infotech Pvt Ltd\",\"isPartOf\":{\"@id\":\"https:\/\/legacit.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg\",\"datePublished\":\"2022-04-26T11:11:09+00:00\",\"dateModified\":\"2022-08-30T07:09:48+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#primaryimage\",\"url\":\"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg\",\"contentUrl\":\"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg\",\"width\":2560,\"height\":1611},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/legacit.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/legacit.com\/blog\/#website\",\"url\":\"https:\/\/legacit.com\/blog\/\",\"name\":\"Legacit Infotech Pvt Ltd\",\"description\":\"Legacit Infotech Pvt Ltd\",\"publisher\":{\"@id\":\"https:\/\/legacit.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/legacit.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/legacit.com\/blog\/#organization\",\"name\":\"Legacit Infotech Pvt Ltd\",\"url\":\"https:\/\/legacit.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/legacit.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/06\/legacit-logo.png\",\"contentUrl\":\"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/06\/legacit-logo.png\",\"width\":248,\"height\":203,\"caption\":\"Legacit Infotech Pvt Ltd\"},\"image\":{\"@id\":\"https:\/\/legacit.com\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/www.facebook.com\/legacit\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/legacit.com\/blog\/#\/schema\/person\/02819527e1d7c6582caa7261d9c88428\",\"name\":\"legacit\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/legacit.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/15a4987e03c7742e2a7376fc47bfa377b58a9614133d24305d1f58a325a4aead?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/15a4987e03c7742e2a7376fc47bfa377b58a9614133d24305d1f58a325a4aead?s=96&d=mm&r=g\",\"caption\":\"legacit\"},\"sameAs\":[\"https:\/\/legacit.com\/blog\/\"],\"url\":\"https:\/\/legacit.com\/blog\/author\/legacit\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us - Legacit Infotech Pvt Ltd","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/","og_locale":"en_US","og_type":"article","og_title":"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us","og_description":"It is obvious that nobody appreciates having their mistakes pointed out, but truth be told\u2013 this is what Quality Assurance specialists aka testers do on a daily basis. Developers often treat their apps and their code on a very personal level, in a similar way that painters consider their paintings or musicians, their riffs. So, how do our Quality Assurance Professionals deal with developers, especially when they need to report a bug, and how do they avoid getting into possible conflicts? 1. We always ensure it\u2019s a bug Nobody likes to be in a situation like when there is this one person who claims that the team has done something wrong but, in reality, they didn\u2019t; now the team needs to waste time to prove themselves right and show that nothing had in fact gone wrong. No one wants to […]","og_url":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/","og_site_name":"Legacit Infotech Pvt Ltd","article_publisher":"https:\/\/www.facebook.com\/legacit","article_published_time":"2022-04-26T11:11:09+00:00","article_modified_time":"2022-08-30T07:09:48+00:00","og_image":[{"width":2560,"height":1611,"url":"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg","type":"image\/jpeg"}],"author":"legacit","twitter_card":"summary_large_image","twitter_misc":{"Written by":"legacit","Est. reading time":"5 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#article","isPartOf":{"@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/"},"author":{"name":"legacit","@id":"https:\/\/legacit.com\/blog\/#\/schema\/person\/02819527e1d7c6582caa7261d9c88428"},"headline":"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us","datePublished":"2022-04-26T11:11:09+00:00","dateModified":"2022-08-30T07:09:48+00:00","mainEntityOfPage":{"@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/"},"wordCount":1048,"commentCount":0,"publisher":{"@id":"https:\/\/legacit.com\/blog\/#organization"},"image":{"@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#primaryimage"},"thumbnailUrl":"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg","articleSection":["QA Testing"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/","url":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/","name":"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us - Legacit Infotech Pvt Ltd","isPartOf":{"@id":"https:\/\/legacit.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#primaryimage"},"image":{"@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#primaryimage"},"thumbnailUrl":"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg","datePublished":"2022-04-26T11:11:09+00:00","dateModified":"2022-08-30T07:09:48+00:00","breadcrumb":{"@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#primaryimage","url":"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg","contentUrl":"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/04\/blog-01-1-scaled.jpg","width":2560,"height":1611},{"@type":"BreadcrumbList","@id":"https:\/\/legacit.com\/blog\/7-tips-our-quality-assurance-professionals-follow-to-report-bugs-without-developers-hating-us\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/legacit.com\/blog\/"},{"@type":"ListItem","position":2,"name":"7 Tips Our Quality Assurance Professionals Follow to Report Bugs Without Developers Hating Us"}]},{"@type":"WebSite","@id":"https:\/\/legacit.com\/blog\/#website","url":"https:\/\/legacit.com\/blog\/","name":"Legacit Infotech Pvt Ltd","description":"Legacit Infotech Pvt Ltd","publisher":{"@id":"https:\/\/legacit.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/legacit.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/legacit.com\/blog\/#organization","name":"Legacit Infotech Pvt Ltd","url":"https:\/\/legacit.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/legacit.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/06\/legacit-logo.png","contentUrl":"https:\/\/legacit.com\/blog\/wp-content\/uploads\/2022\/06\/legacit-logo.png","width":248,"height":203,"caption":"Legacit Infotech Pvt Ltd"},"image":{"@id":"https:\/\/legacit.com\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/legacit"]},{"@type":"Person","@id":"https:\/\/legacit.com\/blog\/#\/schema\/person\/02819527e1d7c6582caa7261d9c88428","name":"legacit","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/legacit.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/15a4987e03c7742e2a7376fc47bfa377b58a9614133d24305d1f58a325a4aead?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/15a4987e03c7742e2a7376fc47bfa377b58a9614133d24305d1f58a325a4aead?s=96&d=mm&r=g","caption":"legacit"},"sameAs":["https:\/\/legacit.com\/blog\/"],"url":"https:\/\/legacit.com\/blog\/author\/legacit\/"}]}},"_links":{"self":[{"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/posts\/93","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/comments?post=93"}],"version-history":[{"count":2,"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/posts\/93\/revisions"}],"predecessor-version":[{"id":592,"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/posts\/93\/revisions\/592"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/media\/94"}],"wp:attachment":[{"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/media?parent=93"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/categories?post=93"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/legacit.com\/blog\/wp-json\/wp\/v2\/tags?post=93"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}