{"id":89,"date":"2020-07-07T12:14:00","date_gmt":"2020-07-07T12:14:00","guid":{"rendered":"https:\/\/fluxtech.me\/blog\/?p=89"},"modified":"2021-12-10T12:12:23","modified_gmt":"2021-12-10T12:12:23","slug":"self-testing-by-developers-the-hot-potato","status":"publish","type":"post","link":"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/","title":{"rendered":"Self-Testing by Developers. The Hot Potato"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Testing is for QA engineers, right? Nevertheless, we find it to be an essential part of developers\u2019 work as well. Self-testing often raises controversial questions among <a href=\"https:\/\/fluxtech.me\/blog\/?p=137&amp;preview=true\">developers<\/a> and becomes a hot potato that gets tossed around in development teams. You\u2019ll often hear things like:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Why should developers do testing: it\u2019s a QA task;<\/li><li>Developers can\u2019t test because they have a different mindset;<\/li><li>Developers don\u2019t have time, etc.<\/li><\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"600\" src=\"https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_koCL5gFm-1jfCNtA14_Eow-1024x600.png\" alt=\"\" class=\"wp-image-92\" srcset=\"https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_koCL5gFm-1jfCNtA14_Eow-1024x600.png 1024w, https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_koCL5gFm-1jfCNtA14_Eow-300x176.png 300w, https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_koCL5gFm-1jfCNtA14_Eow-768x450.png 768w, https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_koCL5gFm-1jfCNtA14_Eow-1536x900.png 1536w, https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_koCL5gFm-1jfCNtA14_Eow.png 2000w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Self-testing is like checking your pockets before leaving the house. You\u2019re checking for the keys, wallet, phone. Your main aim is to leave the house for work BUT you need to be sure that everything is in its right place. Plus, you want to ensure that everything will be safe and secure after you come back home. So you check the water supply, heaters, lights, take out the trash, and feed your pet. Of course, you do, and if you have a pinch of doubt about not turning off the iron, you return to recheck it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Self-testing is similar to this routine. Its aim is to leave the product safe and sound after implementing a new feature or fixing a problem. Before we go any further, let\u2019s shed some light on the notions of self-testing, unit testing, and smoke testing, as other categories related to the topic, and underline why unit\/smoke test should not be taken as self-testing.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What is Self-testing?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Self-testing is a type of testing executed by a software developer after the code is written and integrated into the system, to check whether their piece of code delivers the expected result when integrated into the whole system of the product.&nbsp;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By comparison, unit testing is done during development with the goal of validating the result of the code in isolation. Smoke testing is a kind of software testing performed after the software is built to ascertain that the critical functionalities of the program are working fine.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For starters, let\u2019s make it clear that self-testing done by developers is considerably different from testing done by QA engineers. Developers are expected to make sure the new feature is integrated into the system successfully. On the other hand, in addition to the main flow, QA specialists consider every possible positive and negative case, they consider the feature from the point of view of all possible users, as well as from the perspective of business. Moreover, they test it in connection with other modules somehow related to it and suggest improvements to make the feature better.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">By contrast, no one expects developers to do all that, right? To put it another way, developers are expected to verify, while QAs follow verification up with validation. Meaning, they make sure development meets business goals.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">With that in mind, let\u2019s list out some weighty arguments <em>in favor of self-testing.<\/em><\/p>\n\n\n<!-- This site is converting visitors into subscribers and customers with OptinMonster - https:\/\/optinmonster.com :: Campaign Title: Blog subscription --><div id=\"om-ln58chpofeel7of5zhoo-holder\"><\/div><script>(function(d){var s=d.createElement('script');s.type='text\/javascript';s.src='https:\/\/a.omappapi.com\/app\/js\/api.min.js';s.async=true;s.dataset.campaign='ln58chpofeel7of5zhoo';s.dataset.user='154387';d.getElementsByTagName('head')[0].appendChild(s);})(document);<\/script><!-- \/ OptinMonster -->\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Whatever you do, do it well.<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">This is not just a motivational quote, it\u2019s a lifestyle. So self-testing is a helpful habit to bring into your life. You deliver better code as a result of self-testing. As a result, you see <a href=\"https:\/\/hackernoon.com\/self-testing-for-solo-devs-d3f9e7ae03b4\" target=\"_blank\" rel=\"noreferrer noopener\">better results<\/a> and set challenging benchmarks, and become a better developer. Defining standards for oneself has always been an essential key to self-development.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Taking a fresh glance at your code<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">As a result of self-testing, you begin to acknowledge the possible weaknesses of your code. One can fix most issues in a more mechanical way, but after fixing them make sure you have time to look at your own code with a fresh glance. This will allow you to understand the weak points, and improve, as well as find better solutions leaving you with optimized code, better quality, and performance.<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Prevent instead of fixing<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">You say you don\u2019t have time\u2026Ok. Imagine there is a defect in the code. You know you could have prevented it. The QA specialist finds it, does some research, reports a bug, then the PM takes a look at it, prioritizes it, and assigns it to you anyway. Assume you are already working on another feature. Now, you have to interrupt your work and dive back into the previous feature. So a stitch in time saves nine!<\/p>\n\n\n\n<h4 class=\"wp-block-heading\"><strong>Fast delivery, better product<\/strong><\/h4>\n\n\n\n<p class=\"wp-block-paragraph\">Deadlines are an inevitable part of projects, and when projects are in production, deadlines are often very pressing. When self-testing is not done by the developer and main flows and integration are not tested and verified, then testing of the feature takes plenty of time to verify all those bug fixes and finalize testing, which, in its turn, causes delays in the project.<\/p>\n\n\n\n<h2 class=\"has-large-font-size wp-block-heading\"><strong>Steps to Guide You in Self-Testing<\/strong><\/h2>\n\n\n\n<h3 class=\"has-normal-font-size wp-block-heading\"> \ud83d\udc4c D<strong>o it <\/strong>as a must until it becomes a habit<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When estimating the implementation of a feature, make sure you factor in self-testing time. If you are dividing the main task or story into manageable sub-tasks, make sure you also have a separate sub-task for self-testing. The fact that there is such a task urges you to resolve it ensures you are delivering a complete feature.<\/p>\n\n\n\n<h3 class=\"has-normal-font-size wp-block-heading\" id=\"082c\">\ud83e\udd18 Think like a user, stay a developer<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\" id=\"ee94\">High-quality code is not a guarantee for trouble-free features. Features need to be checked manually in the context of the whole system. Think like a user: Is it convenient to use the application? Is it secure to store or transfer sensitive data? Being in a user\u2019s shoes while testing your own code is a trusted method to becoming a successful developer.<\/p>\n\n\n\n<h3 class=\"has-normal-font-size wp-block-heading\" id=\"c1da\">\ud83e\udd1d Sharing is caring<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\" id=\"7ecf\">Helping other team members to have a better understanding of the technical implementation of the feature is as important as implementing it. Jot down your comments, specific steps, endpoints, routes, even worries regarding some weak points of the code, and inform other team members how the new module can affect other parts of the application. Passing this kind of information on in written form also reduces time-consuming verbal discussions full of potential misunderstandings.<\/p>\n\n\n\n<h3 class=\"has-normal-font-size wp-block-heading\" id=\"dedd\">\u270a Resist dark forces<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\" id=\"9216\">Never pretend that you\u2019ve done self-testing when actually you haven\u2019t. Never lie. It becomes obvious whether the feature has gone through self-testing or not when it fails on the first or second step. If you have a time constraint and can\u2019t manage to do self-testing, inform your fellow QA about it, and highlight the parts that need to be tested more scrupulously.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;&#8211;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Here at Flux Technologies, we have been practicing a self-testing policy for almost a year. As a result, we had a remarkable reduction of bugs (25\u201335%) in just a month.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We asked the developers to assess the effectiveness of the self-testing policy in terms of the product they are currently working on and in terms of their own productivity and code quality from 1 (not effective at all) to 10 (very effective). And most of them (60%) find self-testing very effective both for the product and the code.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"840\" height=\"378\" src=\"https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_plPYRTuP3e9xhuXU3fAlpQ.png\" alt=\"\" class=\"wp-image-90\" srcset=\"https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_plPYRTuP3e9xhuXU3fAlpQ.png 840w, https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_plPYRTuP3e9xhuXU3fAlpQ-300x135.png 300w, https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_plPYRTuP3e9xhuXU3fAlpQ-768x346.png 768w\" sizes=\"auto, (max-width: 840px) 100vw, 840px\" \/><\/figure><\/div>\n\n\n\n<p class=\"wp-block-paragraph\">Also, we asked to list some pros and cons of the self-testing policy and combining the answers received from the survey, we got the whole picture that, we guess, doesn\u2019t need any further comments.<\/p>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_A5vEbI5jfGGSxp3KN1TQ2g.png\" alt=\"\" class=\"wp-image-91\" srcset=\"https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_A5vEbI5jfGGSxp3KN1TQ2g.png 1024w, https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_A5vEbI5jfGGSxp3KN1TQ2g-300x225.png 300w, https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_A5vEbI5jfGGSxp3KN1TQ2g-768x576.png 768w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Testing is for QA engineers, right? Nevertheless, we find it to be an essential part of developers\u2019 work as well. Self-testing often raises controversial questions among developers and becomes a hot potato that gets tossed around in development teams. You\u2019ll often hear things like: Why should developers do testing: it\u2019s a QA task; Developers can\u2019t [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":92,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"footnotes":""},"categories":[15],"tags":[39,27,41],"class_list":["post-89","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-development","tag-quality-assurance","tag-tips","tag-web-development"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v20.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Self-Testing by Developers. The Hot Potato - Flux Technologies<\/title>\n<meta name=\"description\" content=\"Why should developers self-test? It\u2019s a QA task. Developers can\u2019t test because they have a different mindset. We&#039;ve heard it all before...\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Self-Testing by Developers. The Hot Potato - Flux Technologies\" \/>\n<meta property=\"og:description\" content=\"Why should developers self-test? It\u2019s a QA task. Developers can\u2019t test because they have a different mindset. We&#039;ve heard it all before...\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/\" \/>\n<meta property=\"og:site_name\" content=\"Flux Technologies\" \/>\n<meta property=\"article:published_time\" content=\"2020-07-07T12:14:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-12-10T12:12:23+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_koCL5gFm-1jfCNtA14_Eow.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2000\" \/>\n\t<meta property=\"og:image:height\" content=\"1172\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Flux Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Flux Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/\",\"url\":\"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/\",\"name\":\"Self-Testing by Developers. The Hot Potato - Flux Technologies\",\"isPartOf\":{\"@id\":\"https:\/\/fluxtech.me\/blog\/#website\"},\"datePublished\":\"2020-07-07T12:14:00+00:00\",\"dateModified\":\"2021-12-10T12:12:23+00:00\",\"author\":{\"@id\":\"https:\/\/fluxtech.me\/blog\/#\/schema\/person\/41b838e552fdb243119410f480f6944d\"},\"description\":\"Why should developers self-test? It\u2019s a QA task. Developers can\u2019t test because they have a different mindset. We've heard it all before...\",\"breadcrumb\":{\"@id\":\"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/fluxtech.me\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Self-Testing by Developers. The Hot Potato\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fluxtech.me\/blog\/#website\",\"url\":\"https:\/\/fluxtech.me\/blog\/\",\"name\":\"Flux Technologies\",\"description\":\"Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fluxtech.me\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/fluxtech.me\/blog\/#\/schema\/person\/41b838e552fdb243119410f480f6944d\",\"name\":\"Flux Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/fluxtech.me\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/c1c5fc3228772412cf7cb45ed9c2aa6fc008d50d756869eea81624b68d4c4ef6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/c1c5fc3228772412cf7cb45ed9c2aa6fc008d50d756869eea81624b68d4c4ef6?s=96&d=mm&r=g\",\"caption\":\"Flux Team\"},\"sameAs\":[\"https:\/\/fluxtech.me\/blog\"],\"url\":\"https:\/\/fluxtech.me\/blog\/author\/fluxblogadmin\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Self-Testing by Developers. The Hot Potato - Flux Technologies","description":"Why should developers self-test? It\u2019s a QA task. Developers can\u2019t test because they have a different mindset. We've heard it all before...","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:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/","og_locale":"en_US","og_type":"article","og_title":"Self-Testing by Developers. The Hot Potato - Flux Technologies","og_description":"Why should developers self-test? It\u2019s a QA task. Developers can\u2019t test because they have a different mindset. We've heard it all before...","og_url":"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/","og_site_name":"Flux Technologies","article_published_time":"2020-07-07T12:14:00+00:00","article_modified_time":"2021-12-10T12:12:23+00:00","og_image":[{"width":2000,"height":1172,"url":"https:\/\/fluxtech.me\/blog\/wp-content\/uploads\/2021\/11\/1_koCL5gFm-1jfCNtA14_Eow.png","type":"image\/png"}],"author":"Flux Team","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Flux Team","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/","url":"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/","name":"Self-Testing by Developers. The Hot Potato - Flux Technologies","isPartOf":{"@id":"https:\/\/fluxtech.me\/blog\/#website"},"datePublished":"2020-07-07T12:14:00+00:00","dateModified":"2021-12-10T12:12:23+00:00","author":{"@id":"https:\/\/fluxtech.me\/blog\/#\/schema\/person\/41b838e552fdb243119410f480f6944d"},"description":"Why should developers self-test? It\u2019s a QA task. Developers can\u2019t test because they have a different mindset. We've heard it all before...","breadcrumb":{"@id":"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fluxtech.me\/blog\/self-testing-by-developers-the-hot-potato\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/fluxtech.me\/blog\/"},{"@type":"ListItem","position":2,"name":"Self-Testing by Developers. The Hot Potato"}]},{"@type":"WebSite","@id":"https:\/\/fluxtech.me\/blog\/#website","url":"https:\/\/fluxtech.me\/blog\/","name":"Flux Technologies","description":"Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fluxtech.me\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/fluxtech.me\/blog\/#\/schema\/person\/41b838e552fdb243119410f480f6944d","name":"Flux Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/fluxtech.me\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/c1c5fc3228772412cf7cb45ed9c2aa6fc008d50d756869eea81624b68d4c4ef6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/c1c5fc3228772412cf7cb45ed9c2aa6fc008d50d756869eea81624b68d4c4ef6?s=96&d=mm&r=g","caption":"Flux Team"},"sameAs":["https:\/\/fluxtech.me\/blog"],"url":"https:\/\/fluxtech.me\/blog\/author\/fluxblogadmin\/"}]}},"_links":{"self":[{"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/posts\/89","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/comments?post=89"}],"version-history":[{"count":7,"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/posts\/89\/revisions"}],"predecessor-version":[{"id":358,"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/posts\/89\/revisions\/358"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/media\/92"}],"wp:attachment":[{"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/media?parent=89"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/categories?post=89"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fluxtech.me\/blog\/wp-json\/wp\/v2\/tags?post=89"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}