{"id":6200,"date":"2016-05-04T19:13:58","date_gmt":"2016-05-04T19:13:58","guid":{"rendered":"http:\/\/www.abstracta.us\/?p=6200"},"modified":"2025-05-05T21:21:17","modified_gmt":"2025-05-05T21:21:17","slug":"yodas-guide-for-agile-testing","status":"publish","type":"post","link":"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/","title":{"rendered":"Yoda\u2019s \u2018The Way of the Jedi Tester\u2019: A Guide for Agile Testing"},"content":{"rendered":"<p><script src=\"https:\/\/abstracta.activehosted.com\/f\/embed.php?id=48\" type=\"text\/javascript\" charset=\"utf-8\"><\/script><!-- Go to www.addthis.com\/dashboard to customize your tools --><script src=\"\/\/s7.addthis.com\/js\/300\/addthis_widget.js#pubid=ra-58d80a50fc4f926d\" type=\"text\/javascript\"><\/script><\/p>\n<h1><span style=\"font-weight: 400; color: #333333;\">Yoda\u2019s Software Testing Principles for Thriving in an Agile Environment<\/span><\/h1>\n<p><span style=\"font-weight: 400; color: #000000;\"><span style=\"color: #333333;\">Did you know there\u2019s more than just one force? Yes, there\u2019s the one that has to do with the connection of all living beings, but there is also one within software known as quality. An old friend of mine, Yoda, recently visited me at a place in a galaxy far, far away called Uruguay and attended the conference, <a href=\"http:\/\/testing.uy\/en\">TestingUY.<\/a><\/span> <span style=\"color: #333333;\">After attending the session, \u201cThe Agile Death of the Tester,\u201d that I gave with agile consultant, <a href=\"https:\/\/uy.linkedin.com\/in\/gabrielmontero\/en\">Gabriel Montero<\/a><\/span><\/span>, <span style=\"color: #333333;\">he wanted to spread our message to all of the testers across the tech-iverse who are entering into the agile galaxy.<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">Here Yoda wrote the principles that he gleaned from it for testers to survive agile which he gave to me to share with you today. \u00a0<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Introduction\"><\/span><strong><span style=\"color: #00b674;\">Introduction<\/span><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"color: #333333;\"><span style=\"font-weight: 400;\">Impossible to see, the future is,<\/span> <span style=\"font-weight: 400;\">but after all of my years of living, I, Jedi Master Yoda, can foresee the longevity and ubiquity of agile. Agile is<\/span><span style=\"font-weight: 400;\">\u00a0an approach to software delivery that focuses on incremental improvements and quick adaptation to change which is sweeping through the \u201ctech-iverse.\u201d <\/span><\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter size-full wp-image-6212\" src=\"http:\/\/www.abstracta.us\/wp-content\/uploads\/2016\/05\/giphy-35.gif\" alt=\"giphy (35)\" width=\"499\" height=\"213\" \/><\/p>\n<p><span style=\"color: #333333;\"><span style=\"font-weight: 400;\">According to the World Quality Report 2015-2016, which surveyed over 1500 testers, 54% said they had adopted agile. But, without its challenges, it hasn\u2019t come. The most reported challenges were: difficulties in identifying the right areas on which testing should focus (33%), lack of appropriate test data and environment (31%), and a lack of professional test expertise in agile teams (31%). <\/span><\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">So why do these challenges arise? Well, young Jedi tester, the traditional paradigm of a tester is not that of an agile team member.<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">At what agile means, let\u2019s take a look. Being agile means you commit to these values which form the Agile Testing Manifesto:<\/span><\/p>\n<ul>\n<li><span style=\"font-weight: 400; color: #333333;\">People and interactions over processes and tools<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Working software over extensive documentation<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Customer collaboration over contract negotiation<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Responding to change over following a plan<\/span><\/li>\n<\/ul>\n<p><strong>Herein, the dilemma lies. In the <i>traditional<\/i> paradigm of testing, testing is not agile because testers:<\/strong><\/p>\n<ul>\n<li><span style=\"font-weight: 400; color: #333333;\">Form an independent team that is part of a process or phase in development (usually left for the end)<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Write test cases based on requirement specifications<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Write test cases based on the customer contract<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Create test plans and maintain those tests<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400; color: #333333;\">So, you testers seem to work counter to agile, but\u2026 fear have you not! There are ways that you can keep up with the changes so the software world doesn\u2019t desert you like those in my world deserted poor planet Tython.\u00a0It is time to unlearn the way you used to think about testing. Instead of seeing yourselves opposed to developers as the light side is opposed to that of the dark, the force of software quality should bring you together to create software that customers and end users love.<\/span><\/p>\n<p><span style=\"color: #000000;\"><br \/>\n<img decoding=\"async\" class=\"aligncenter wp-image-6231\" src=\"http:\/\/www.abstracta.us\/wp-content\/uploads\/2016\/05\/grafico_yoda_new-01-1.png\" alt=\"grafico_yoda_new-01 (1)\" width=\"545\" height=\"545\" \/><\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">Here\u2019s how you can navigate the agile galaxy, a place where you can rise up to the occasion to be a Jedi tester. Like the Jedi warrior who protects peace and justice in my universe, the Jedi tester is one who defends and protects software quality, enhancing the overall software development process, instead of being involved only at the end.<\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"The_Way_of_the_Jedi_Tester\"><\/span><strong><span style=\"color: #00b674;\">The Way of the Jedi Tester<\/span><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400; color: #333333;\">Principles, here are, of the way of the Jedi tester in the agile galaxy of the tech-iverse. In mind, keeping, I am talking about agile in general and apply to any tester, these can. Keeping also in mind that agile doesn\u2019t necessarily mean rapid development, but adaptive development, responsive to change as requirements tend to change. <\/span><\/p>\n<p><b><span style=\"color: #333333;\">I will go over how the Jedi tester adds value during three main activities of agile: planning, doing (development), and analysis for improvement (review).<\/span> <\/b><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Planning_Activities\"><\/span><strong><span style=\"color: #3056a2;\">Planning Activities<\/span><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<h4>Principle 1: In the whole process of releasing a new feature or version, from day 0, participate you will.<\/h4>\n<p><span style=\"font-weight: 400; color: #333333;\">Normally, in the beginning, stakeholders specify and &#8220;close&#8221; the requirements document, sign a contract, and then plan how to do these requirements. In agile, the requirements are not closed, so there is not so much documentation because it is always kept in mind that the requirements will change making it futile to spend time documenting them.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">So, what can the Jedi tester do? Help with these planning activities of agile teams, he or she can: <\/span><\/p>\n<ul>\n<li><span style=\"font-weight: 400; color: #333333;\">Estimation, considering the testing activities to be conducted <\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Prioritization of functionalities, as he\/she has a wider view and can see the big picture<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Defining acceptance criteria. Yes, after understanding what the customer wants, the tester helps to define the product!<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Creating a test strategy. How will the team go about testing? For example, by implementing TDD (test-driven development), the entire development mindset will change, shifting the focus to testing (Next principle, see the).<\/span><\/li>\n<\/ul>\n<h4>Principle 2: Over the detection of bugs, focus on the prevention.<\/h4>\n<p><span style=\"font-weight: 400; color: #333333;\">According to Cem Kaner, testing is a technical and empirical investigation done to provide stakeholders with information about the quality of a product or service. In his definition, he is mentioning detecting and reporting errors, but a Jedi tester should be able to also prevent them.<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">To do so, it is important for testers to ask as many questions as possible before diving into development. This way, both the developers and the customers will imagine a clearer, more thorough image of what they want to make and will have to tackle issues before they arise that you, the tester, have already thought about. For example: Will we need to make multiple versions for different browsers? Will the end user favor design simplicity or performance? <\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">From the initial planning activities, testers should be advocates for changing the traditional paradigm of testing from the one that views it as a later stage in development focused on the detection of bugs to one that views it as an activity carried out in parallel with development to prevent bugs. <\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Software_Development_Activities\"><\/span><strong><span style=\"color: #3056a2;\">Software Development Activities<\/span><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<h4>Principle 3: Using exploratory testing and other activities throughout development, be you concerned with delivering quality products.<\/h4>\n<p><span style=\"font-weight: 400; color: #333333;\">Now you don\u2019t have the input, or all of the normal things that testers are used to working with like contracts, requirements specification documents, use cases or anything that tells you how the system is supposed to behave and so,\u00a0it\u2019s not that easy to write test cases. Test cases helped you to know how to test, with what data, in what context, pre- and post conditions, expected results, etc. How are you to ensure quality without the things you have always held so near and dear? Don\u2019t worry, you already know and have everything you need. Have you the skills to survive, but use them differently you must.<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\"><br \/>\n<img decoding=\"async\" class=\"aligncenter wp-image-6232\" src=\"http:\/\/www.abstracta.us\/wp-content\/uploads\/2016\/05\/grafico_yoda_new-02-1.png\" alt=\"grafico_yoda_new-02 (1)\" width=\"545\" height=\"545\" \/><br \/>\n<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">Not so well suited for agile are test cases in the first place because they require a lot of maintenance and do not quickly adapt to change. So, the Jedi tester must seek out lighter alternatives without diminishing the quality of testing or control. \u00a0Instead of basing everything on test cases, the Jedi tester must change the strategy, aiming to minimize the time dedicated to maintaining documentation and increasing the time taken to add value. <\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">To do so, today\u2019s agile testers are phasing out test cases like last millennium&#8217;s lightsabers, relying more heavily upon activities like mind-mapping, writing checklists, and doing exploratory testing. <\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\"><strong>Exploratory testing, above all of those activities, is one of the best ways can add value during agile development the Jedi tester.<\/strong> <\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">Exploratory software testing is a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the value of her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project. <span style=\"font-weight: 400 color: #333333;\">Lisa Crispin and Janet Gregory, in their book<\/span><b>, <\/b><span style=\"font-weight: 400;\">&#8220;<a href=\"http:\/\/www.amazon.com\/Agile-Testing-Practical-Guide-Testers\/dp\/0321534468\">Agile Testing: A Practical Guide for Testers and Agile Teams<\/a>\u201d<\/span><\/span> state that,<span style=\"font-weight: 400; color: #333333;\">\u00a0\u201cTesting an application with a plan to learn about it as you go, and letting that information guide your testing, is in line with valuing working software and responding to change,\u201d therefore it\u2019s inherently agile! <\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">So, whenever you do exploratory testing, you can be agile, even if the Jedi tester is not working on an agile project. And, as the Jedi tester constantly changes his or her testing, he or she can constantly optimize the value of their work instead of following the same procedures again and again that don\u2019t provide the most value nor allow for creativity. <\/span><\/p>\n<h4>Principle 4: Becoming everyone\u2019s responsibility, QA is. Forming one unified team, work alongside developers.<\/h4>\n<p><span style=\"font-weight: 400; color: #333333;\">Traveling to the agile galaxy, one hears much discussion of test automation. Test automation can occur along all stages of development from unit testing to testing on the UI level. Highly effective it is to automate as many tests at the unit level, which also makes QA the developer\u2019s concern. In this way, developers and testers both bare the responsibility of tending to the force of software quality, further uniting them as members of the same team. <\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">To make this principle work, the Jedi tester must foment collaboration as much as possible, substituting the \u201cI\u201d in testing for the \u201cwe\u201d in the creation of high-quality software.<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">Adopt a new paradigm of testing, one in which you harness the force (no, not my force, your force, the one that is software quality) by working in unison with your fellow developer.<\/span><\/p>\n<h3><span class=\"ez-toc-section\" id=\"Review_Activities\"><\/span><strong><span style=\"color: #3056a2;\">Review Activities<\/span><\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n<h4>Principle 5: The last scrum stages: inspection and adaptation, participate in you will.<\/h4>\n<p><span style=\"font-weight: 400; color: #333333;\">Validating product growth and giving and receiving feedback, the team does in this phase. What can the Jedi tester do? Due to your exploratory nature, you have a more comprehensive understanding of product features so, during the product review, you can:<\/span><\/p>\n<ul>\n<li><span style=\"font-weight: 400; color: #333333;\">Guide demos<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Facilitate communication<\/span><\/li>\n<li><span style=\"font-weight: 400; color: #333333;\">Be an advisor to the customer and developers<\/span><\/li>\n<\/ul>\n<p><span style=\"font-weight: 400; color: #333333;\">It is also important to review the team\u2019s processes as a part of the retrospective. A Jedi tester takes advantage of these moments to give testing a voice and a chance for the opinions of testers to be heard not just amongst themselves. Maybe the rest of the team didn\u2019t realize that some issues could have been solved with the help of testing.<\/span><\/p>\n<h4>Principle 6: By studying, participating in the testing community, seek professional growth continue to, you will.<\/h4>\n<p><span style=\"font-weight: 400; color: #333333;\">And, a good Jedi warrior never fails to improve over time strengthening his or her power <\/span><span style=\"font-weight: 400;\">to wield <\/span><span style=\"font-weight: 400; color: #333333;\">the force, even after formal training is complete. So, a good Jedi tester is one who continually learns about new methods and tools, participates in the intergalactic testing community, etc. Furthermore, makes an ultimate Jedi tester, helping with the training of the next generation of Jedi testers. <\/span><\/p>\n<h2><span class=\"ez-toc-section\" id=\"Closing\"><\/span>Closing<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><span style=\"font-weight: 400; color: #333333;\">No matter what galaxy you live in (agile or waterfall) may the force be with you, meaning may quality be in everything you touch. May you choose the light side of the force to produce software that makes the world a better place instead of using it for evil. Oh yes, be you can, agents of change within your organization and the entire tech-iverse!<\/span><span style=\"font-weight: 400; color: #333333;\"><br \/>\n<\/span><\/p>\n<p><span style=\"font-weight: 400; color: #333333;\">I hope you liked this post! I\u2019d like to acknowledge <span style=\"color: #00b674;\"><a href=\"https:\/\/uy.linkedin.com\/in\/kaleiwhite33\">Kalei White<\/a><\/span> for helping me to write this post, as she is the one who is a fan of Star Wars who helped me out with the more creative aspects. &#8211; Federico<\/span><\/p>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"For_Jedi_Testers_More_Recommended_Texts\"><\/span><strong>For Jedi Testers, More Recommended Texts<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a href=\"https:\/\/abstracta.us\/10-mistakes-companies-make-when-outsourcing-software-testing\">White Paper: 10 Mistakes Companies Make When Outsourcing Software Testing<\/a><br \/>\n<a href=\"http:\/\/abstracta.us\/blog\/test-automation\/best-testing-practices-for-agile-teams-the-automation-pyramid\/\" target=\"_blank\" rel=\"noopener noreferrer\">Best Testing Practices For Agile Teams: The Automation Pyramid<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Yoda\u2019s Software Testing Principles for Thriving in an Agile Environment Did you know there\u2019s more than just one force? Yes, there\u2019s the one that has to do with the connection of all living beings, but there is also one within software known as quality. An&#8230;<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[636],"tags":[68,550],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v14.0.2 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Yoda\u2019s \u2018The Way of the Jedi Tester\u2019: A Guide for Agile Testing | Abstracta<\/title>\n<meta name=\"description\" content=\"In this guide for agile testing, Yoda offers his principles for harnessing the force... of software quality! Here&#039;s how to be a Jedi among testers.\" \/>\n<meta name=\"robots\" content=\"index, follow\" \/>\n<meta name=\"googlebot\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<meta name=\"bingbot\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Yoda\u2019s \u2018The Way of the Jedi Tester\u2019: A Guide for Agile Testing | Abstracta\" \/>\n<meta property=\"og:description\" content=\"In this guide for agile testing, Yoda offers his principles for harnessing the force... of software quality! Here&#039;s how to be a Jedi among testers.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog about AI-powered quality engineering for teams building complex software | Abstracta\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/AbstractaQA\/\" \/>\n<meta property=\"article:published_time\" content=\"2016-05-04T19:13:58+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-05-05T21:21:17+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/abstracta.us\/wp-content\/uploads\/2016\/05\/Guide-for-agile-testing-compressor.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"420\" \/>\n\t<meta property=\"og:image:height\" content=\"236\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@fltoledo\" \/>\n<meta name=\"twitter:site\" content=\"@AbstractaUS\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebSite\",\"@id\":\"https:\/\/abstracta.us\/blog\/#website\",\"url\":\"https:\/\/abstracta.us\/blog\/\",\"name\":\"Blog about AI-powered quality engineering for teams building complex software | Abstracta\",\"description\":\"AI-powered quality engineering\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/abstracta.us\/blog\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/#primaryimage\",\"inLanguage\":\"en-US\",\"url\":\"http:\/\/www.abstracta.us\/wp-content\/uploads\/2016\/05\/giphy-35.gif\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/#webpage\",\"url\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/\",\"name\":\"Yoda\\u2019s \\u2018The Way of the Jedi Tester\\u2019: A Guide for Agile Testing | Abstracta\",\"isPartOf\":{\"@id\":\"https:\/\/abstracta.us\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/#primaryimage\"},\"datePublished\":\"2016-05-04T19:13:58+00:00\",\"dateModified\":\"2025-05-05T21:21:17+00:00\",\"author\":{\"@id\":\"https:\/\/abstracta.us\/blog\/#\/schema\/person\/7421e539de0357d3adb0c69ed469a1c2\"},\"description\":\"In this guide for agile testing, Yoda offers his principles for harnessing the force... of software quality! Here's how to be a Jedi among testers.\",\"breadcrumb\":{\"@id\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/\",\"url\":\"https:\/\/abstracta.us\/blog\/\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/\",\"url\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/\",\"name\":\"Testing Strategy\"}},{\"@type\":\"ListItem\",\"position\":3,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/\",\"url\":\"https:\/\/abstracta.us\/blog\/testing-strategy\/yodas-guide-for-agile-testing\/\",\"name\":\"Yoda\\u2019s \\u2018The Way of the Jedi Tester\\u2019: A Guide for Agile Testing\"}}]},{\"@type\":[\"Person\"],\"@id\":\"https:\/\/abstracta.us\/blog\/#\/schema\/person\/7421e539de0357d3adb0c69ed469a1c2\",\"name\":\"Federico Toledo, Chief Quality Officer at Abstracta\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/abstracta.us\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/6de7ec6536c4028b5c02ad4ec1b9af0d?s=96&d=blank&r=g\",\"caption\":\"Federico Toledo, Chief Quality Officer at Abstracta\"},\"description\":\"Co-founder and COO of Abstracta\",\"sameAs\":[\"https:\/\/twitter.com\/fltoledo\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts\/6200"}],"collection":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/comments?post=6200"}],"version-history":[{"count":13,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts\/6200\/revisions"}],"predecessor-version":[{"id":12387,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/posts\/6200\/revisions\/12387"}],"wp:attachment":[{"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/media?parent=6200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/categories?post=6200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/abstracta.us\/blog\/wp-json\/wp\/v2\/tags?post=6200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}