{"id":2087,"date":"2019-11-22T02:34:46","date_gmt":"2019-11-22T02:34:46","guid":{"rendered":"http:\/\/kusuaks7\/?p=1692"},"modified":"2024-02-22T13:28:29","modified_gmt":"2024-02-22T13:28:29","slug":"realizing-value-from-test-automation-value-vs-roi","status":"publish","type":"post","link":"https:\/\/www.experfy.com\/blog\/bigdata-cloud\/realizing-value-from-test-automation-value-vs-roi\/","title":{"rendered":"Realizing Value from Test Automation \u2013&gt; VALUE vs. ROI"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"2087\" class=\"elementor elementor-2087\" data-elementor-post-type=\"post\">\n\t\t\t\t\t\t<section class=\"has_eae_slider elementor-section elementor-top-section elementor-element elementor-element-56d14e5b elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"56d14e5b\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"has_eae_slider elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-4dd94ef6\" data-id=\"4dd94ef6\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-470e419b elementor-widget elementor-widget-text-editor\" data-id=\"470e419b\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tAs we are ready to close another decade of software development and testing, it is in my opinion also a great time to get rid of legacy and outdated terms and methods \u2013 in this short post, I would try and\u00a0<strong>eliminate<\/strong>\u00a0the term\u00a0<strong>ROI<\/strong>\u00a0and recommend replacing it with\u00a0<strong>Value<\/strong>.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-50786a8 elementor-widget elementor-widget-text-editor\" data-id=\"50786a8\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tIf up until few years quality management was trying to justify investments in\u00a0<a href=\"https:\/\/www.perfecto.io\/blog\/automated-test-cases-best-practices\" class=\"broken_link\" rel=\"noopener\">testing<\/a>\u00a0via the\u00a0<strong>ROI<\/strong>\u00a0metric, it is now time for a change.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-b10ded1 elementor-widget elementor-widget-text-editor\" data-id=\"b10ded1\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tWhen implementing continuous testing, and running test automation cycles multiple times a day, in different environment, but different personas, ROI becomes an obsolete term since the measures are much different than before.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-1e80d5f elementor-widget elementor-widget-heading\" data-id=\"1e80d5f\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h3 class=\"elementor-heading-title elementor-size-default\"><h3><strong>Objectives of Continuous Testing<\/strong><\/h3>\n<\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"has_eae_slider elementor-section elementor-top-section elementor-element elementor-element-b09b13a elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"b09b13a\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"has_eae_slider elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-8c17a6c\" data-id=\"8c17a6c\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-d691c3e elementor-widget elementor-widget-text-editor\" data-id=\"d691c3e\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tBefore convincing you to ditch the term ROI, let\u2019s level set on the objectives of modern test automation and especially continuous testing.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-731c4cb elementor-widget elementor-widget-text-editor\" data-id=\"731c4cb\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tFrom the agile testing manifesto, I am marking in bold the key values behind such testing.\n<ul>\n \t<li><b>Continuous testing<\/b>\u00a0over testing at the end.<\/li>\n \t<li>Embracing\u00a0<b>all testing activities\u00a0<\/b>over only automated functional testing.<\/li>\n \t<li>Testing\u00a0<b>what gives value\u00a0<\/b>over testing everything.<\/li>\n \t<li><b>Testing across the team\u00a0<\/b>over testing in siloed testing departments.<\/li>\n \t<li><b>Product coverage\u00a0<\/b>over code coverage.<\/li>\n<\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7b15f56 elementor-widget elementor-widget-text-editor\" data-id=\"7b15f56\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tIf to apply the above, the key goal from such testing is to identify business risks through high-value testing that is done by the entire team across the product and through the entire testing types (functional and non-functional).\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7dd4923 elementor-widget elementor-widget-text-editor\" data-id=\"7dd4923\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tIn the above statements, there is no measure or quantification of anything but the\u00a0<strong>VALUE<\/strong>\u00a0of the tests.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-a5366b4 elementor-widget elementor-widget-heading\" data-id=\"a5366b4\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h3 class=\"elementor-heading-title elementor-size-default\"><h3><strong>The Key Pillars of Continuous Testing<\/strong><\/h3><\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-3e76cfc elementor-widget elementor-widget-text-editor\" data-id=\"3e76cfc\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tTo achieve\u00a0<a href=\"https:\/\/www.perfecto.io\/\" class=\"broken_link\" rel=\"noopener\">continuous testing\u00a0<\/a>organizations should focus on having the ability in house to\u00a0<strong>Create<\/strong>\u00a0test automation,\u00a0<strong>Execute<\/strong>\u00a0it at scale upon demand, in a solid\u00a0<strong>Lab<\/strong>, and at the end of the day \u2013\u00a0<strong>Analyze<\/strong>\u00a0the results using smart methods to make sense of the test results data.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-906aac1 elementor-widget elementor-widget-image\" data-id=\"906aac1\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"image.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<img decoding=\"async\" src=\"https:\/\/www.perfecto.io\/sites\/perfecto.io\/files\/image\/2019-05\/image-smart-test-creation-automation-testing.png\" alt=\"\" \/>\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-2e87a97 elementor-widget elementor-widget-text-editor\" data-id=\"2e87a97\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tIf the above pillars are in line with organizations testing strategy and priority, it would make sense that the tools and techniques used to create and execute the tests will match accordingly.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-63539d0 elementor-widget elementor-widget-text-editor\" data-id=\"63539d0\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tThe big questions here are \u2013\u00a0<em><strong>h<\/strong><strong><em>ow<\/em>\u00a0do i justify any investment of $$ in the above pillars? what measures are relevant? who owns quality per each of these steps? what good looks like<\/strong><\/em>?\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-2c09a4c elementor-widget elementor-widget-heading\" data-id=\"2c09a4c\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h3 class=\"elementor-heading-title elementor-size-default\"><h3><strong>From ROI to Test Value<\/strong><\/h3><\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-171224b elementor-widget elementor-widget-text-editor\" data-id=\"171224b\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tTo address the above questions, let\u2019s identify who is doing testing in today\u2019s Agile and DevOps practices. As DevOps teams are divided into functional groups with test engineers and developers working hand in hand on specific features within iterations and sprints, there is no single person that really does testing. It is a feature team responsibility to deliver high quality and high value software. With that in mind, you will find business testers, developers, and test automation engineers working together and creating automated test scenarios as well as manual exploratory testing to meet their goals. While there might be a modern COE or quality leadership function that oversees the testing strategy within the organizations, determines budgets and tools, the actual work is really done within the teams.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-a355ab3 elementor-widget elementor-widget-text-editor\" data-id=\"a355ab3\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tIf you are in agreement with me that Value is the most important thing in testing, let\u2019s try and break Value into measures:\n<ul>\n \t<li><strong># of flaky tests within cycle<\/strong><\/li>\n \t<li><strong># of tests that repeatedly find defects<\/strong><\/li>\n \t<li><strong># of tests that cause CI jobs to fail<\/strong><\/li>\n \t<li><strong># of tests that fail broken down by root cause (Object ID, Lab, Coding skills, Platform state, etc.).<\/strong><\/li>\n<\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-a8178e3 elementor-widget elementor-widget-text-editor\" data-id=\"a8178e3\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tWhile there are be other metrics, the above ones clearly show if tests are actually living to their expectations of finding bugs, or are simply creating noise and software team wastes.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-70649cf elementor-widget elementor-widget-text-editor\" data-id=\"70649cf\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tLooking at some\u00a0<a href=\"https:\/\/labs.sogeti.com\/how-many-defects-are-too-many\/\" rel=\"noopener\">market standards<\/a>\u00a0show that there is an average of 10-15 defects per\u00a0<strong>KLOC<\/strong>\u00a0(1000 lines of code) and 0.5 defects per KLOC that escapes to production. If to follow this number, it\u2019s clear that the majority of defects that are found and reported today are noise vs. the REAL ones. To be successful in continuous testing requires a discipline and proper measurements of value to ensure that the majority of failed tests that are reported as bugs are indeed issues \u2013 the opposite will cause a mess within the entire DevOps team.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-e8ba706 elementor-widget elementor-widget-text-editor\" data-id=\"e8ba706\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tWith that in mind, teams must acknowledge the fact that quality of testing and quality of product are a moment in time!, hence, you need to continuously measure and maintain it to get the actual state of the product.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7fa1be8 elementor-widget elementor-widget-heading\" data-id=\"7fa1be8\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h3 class=\"elementor-heading-title elementor-size-default\"><h3>How do I Realize Value Than?<\/h3><\/h3>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-d47aac9 elementor-widget elementor-widget-text-editor\" data-id=\"d47aac9\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tTo keep the long story short, there is only 1 place within the testing life cycle that can provide the single pane of glass of your overall testing activities value vs. waste \u2013 it is the\u00a0<strong>TEST REPORT!<\/strong>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-353fbb3 elementor-widget elementor-widget-text-editor\" data-id=\"353fbb3\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tIf you think about the entire life cycle of a test from the moment you write the code, through its debugging, execution and commit into the pipeline, the developer (whoever it may be), says good bye to the test the moment it \u201cpassed\u201d on his environment. The reunion between the test owner and the test only happens in case the test fails in formal test cycles (can be CI, regression triggered by other event, etc.). This means, that there is a blind area from the moment the test was integrated into a suite up until it fails. There is no real reason to review a test if it passes other than being pleased about it (in case it is of course a high value test). Now, think about a suite of 1000 test cases with an average of 10% failures. This means that we now have 100 failed test scenarios that someone needs to review and report about. To add to this the above mentioned fact of\u00a0<strong>10-15 defects per KLOC<\/strong>, the reality would show that\u00a0<strong>at least 80% of the tests are not real bugs<\/strong>. The team now have to deal with debugging of 80 test cases noise that may or may not add value to the product.\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-760f476 elementor-widget elementor-widget-text-editor\" data-id=\"760f476\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tI think (and Hope) that by now the point is clear \u2013&gt;\u00a0<strong>Measuring test automation Value starts with the above metric<\/strong>s, and with the notion of most test cases will not reveal critical bugs when running as regression for the 10x time. To understand what tests add value, what aren\u2019t, and what are simply noise and poor practiced software engineering, you need proper test reporting and quality visibility into each and every domain of your test activities.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-82b7cc5 elementor-widget elementor-widget-text-editor\" data-id=\"82b7cc5\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\tBottom line \u2013 investing time, resources that is money should be made with the value add of these testing in mind. Old fashioned Pass\/Fail per cycle are nice, but cannot keep up with today\u2019s pace of technology, and therefore, requires a more diligent review of how tests behave in real time, over time, per platform, per functional area. And YES \u2013 do not get too attached to your test code, if it doesn\u2019t prove itself after a short amount of time, simply Delete it. You can only assess if the tests bring value via your reporting.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-874be89 elementor-widget elementor-widget-text-editor\" data-id=\"874be89\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t\nThe below visual breaks down the 4 pillars of continuous testing (CT) according to test investments vs. tests value realization.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-32f8929 elementor-widget elementor-widget-image\" data-id=\"32f8929\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"image.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<img decoding=\"async\" src=\"https:\/\/www.perfecto.io\/sites\/perfecto.io\/files\/image\/2019-11\/Cela2.PNG\" alt=\"\" \/>\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Till now quality management was trying to justify investments in&nbsp;testing&nbsp;via the&nbsp;ROI&nbsp;metric, it is now time for a change. When implementing continuous testing, and running test automation cycles multiple times a day, in different environment, but different personas, ROI becomes an obsolete term since the measures are much different than before. The key term for the next 5-10 years when trying to measure and justify investment in testing should be&nbsp;VALUE.<\/p>\n","protected":false},"author":494,"featured_media":2831,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[187],"tags":[95],"ppma_author":[3126],"class_list":["post-2087","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-bigdata-cloud","tag-big-data-amp-technology"],"authors":[{"term_id":3126,"user_id":494,"is_guest":0,"slug":"eran-kinsbruner","display_name":"Eran Kinsbruner","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/?s=96&d=mm&r=g","user_url":"","last_name":"Kinsbruner","first_name":"Eran","job_title":"","description":"Eran Kinsbruner&nbsp;is the lead&nbsp;Technical Evangelist at&nbsp;<a href=\"https:\/\/www.perfectomobile.com\/\" target=\"_blank\" title=\"Perfecto\" rel=\"noopener\">Perfecto<\/a>, the leading cloud-based web, and mobile quality lab. A monthly columnist at&nbsp;<a href=\"https:\/\/www.infoworld.com\/author\/Eran-Kinsbruner\/\">InfoWorld.Com<\/a>, he is the author of the&nbsp;<a href=\"https:\/\/www.amazon.com\/dp\/0692885994\/ref=sr_1_1?ie=UTF8&amp;qid=1493727687&amp;sr=8-1&amp;keywords=eran+kinsbruner\">Digital Quality Handbook<\/a>, and Continuous Testing for DevOps Professionals and the creator and author of the quarterly Digital Test Coverage&nbsp;<a href=\"https:\/\/info.perfectomobile.com\/factors-magazine.html\">factors<\/a>&nbsp;magazine, and co-inventor of the&nbsp;<a href=\"https:\/\/www.google.com\/patents\/US6980916\">test exclusion automated mechanism<\/a>&nbsp;for mobile J2ME testing at Sun Microsystems. He is also a public speaker, researcher, and blogger."}],"_links":{"self":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/2087","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/users\/494"}],"replies":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/comments?post=2087"}],"version-history":[{"count":6,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/2087\/revisions"}],"predecessor-version":[{"id":36094,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/posts\/2087\/revisions\/36094"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/media\/2831"}],"wp:attachment":[{"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/media?parent=2087"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/categories?post=2087"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/tags?post=2087"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.experfy.com\/blog\/wp-json\/wp\/v2\/ppma_author?post=2087"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}