{"id":380,"date":"2022-02-22T23:08:04","date_gmt":"2022-02-22T23:08:04","guid":{"rendered":"http:\/\/rainforestqa.com\/ui-testing-tools\/"},"modified":"2025-03-18T13:13:16","modified_gmt":"2025-03-18T13:13:16","slug":"ui-testing-tools","status":"publish","type":"post","link":"https:\/\/www.rainforestqa.com\/blog\/ui-testing-tools","title":{"rendered":"A detailed comparison of UI testing tools and what to look for"},"content":{"rendered":"\n<p>The goal of user interface (UI) testing is to verify that:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>All visible elements in a software product work properly <em>and<\/em>&nbsp;<\/li>\n\n\n\n<li>All of those elements appear with the correct colors, fonts, shapes, and positioning.&nbsp;<\/li>\n<\/ol>\n\n\n\n<p>However, most software testing tools either test the appearance of the application or the functionality\u2014few tools do <em>both<\/em> well.<\/p>\n\n\n\n<p>To test functionality, most automated software testing tools primarily interact with the underlying code of an application, while assuming that the visual layer (what the user sees) is rendering properly.&nbsp;<\/p>\n\n\n\n<p>These test scripts might include steps like \u201cclick on the \u2018Sign Up\u2019 button\u201d and \u201cverify that the confirmation message is visible.\u201d While that might sound like the test is verifying the appearance of the Sign Up button, the test script is actually just looking for the presence of the code that <em>represents<\/em> the Sign Up button. As long as the code for the element exists and the visibility is set to visible, the test will pass.<\/p>\n\n\n\n<p>In reality, there are a variety of situations where the code for an element, like a Sign Up button, can be present and have the correct visibility setting, but the appearance of the element will have some error in the UI. It could be rendering off-screen or beneath another element because of an accidental change to the positioning settings in the CSS.&nbsp;<\/p>\n\n\n\n<p>Because of this, many teams take one of the following approaches to testing the appearance of an application:&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>They use human testers to manually interact with various user paths looking for visual bugs (which is time-consuming and prone to human error), or<\/li>\n\n\n\n<li>They use additional plugins to insert screenshot checkpoints that compare the whole page or sections of the page to baseline images (but this method catches every single visual change, not just visual bugs, making it hard to find the signal in the noise).<\/li>\n<\/ul>\n\n\n\n<p>Either way, you\u2019ll end up needing two tools or methods to complete one job. In contrast, Rainforest QA, our no-code automated testing tool, tests both the functionality and appearance of an application simultaneously.<\/p>\n\n\n\n<p>In this post, we\u2019ll show you how we designed Rainforest to overcome the biggest challenges of UI testing, and we\u2019ll also compare it to 13 other UI testing tools.&nbsp;<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>How Rainforest QA tests the appearance and functionality of the UI without coded test scripts&nbsp;<\/li>\n\n\n\n<li>Code-based UI Testing Tools with Screenshot Plugins for Visual Validation<\/li>\n\n\n\n<li>Code-based UI Testing Tools with No Visual Validation&nbsp;<\/li>\n<\/ul>\n\n\n\n<p><em><a href=\"https:\/\/www.rainforestqa.com\/talk-to-sales\">Talk to us<\/a> about setting up a personalized demo and see why Rainforest is the easiest way to to run automated UI tests without having to code.<\/em><\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.rainforestqa.com\/blog\/ui-testing-tools\/#How_Rainforest_QA_Tests_the_Appearance_and_Functionality_of_the_UI_without_Coded_Test_Scripts\" >How Rainforest QA Tests the Appearance and Functionality of the UI without Coded Test Scripts<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.rainforestqa.com\/blog\/ui-testing-tools\/#Code-based_Tools_with_Screenshot_Plugins_for_Visual_Validation\" >Code-based Tools with Screenshot Plugins for Visual Validation<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.rainforestqa.com\/blog\/ui-testing-tools\/#Code-based_Tools_with_No_Visual_Validation\" >Code-based Tools with No Visual Validation<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_Rainforest_QA_Tests_the_Appearance_and_Functionality_of_the_UI_without_Coded_Test_Scripts\"><\/span>How Rainforest QA Tests the Appearance and Functionality of the UI without Coded Test Scripts<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Rainforest is a no-code automated UI testing tool with a drag-and-drop editor that lets you create automated tests that mimic how users interact with the final, visual layer of your website or app. You can test the functionality of the application and validate the appearance at the same time.<\/p>\n\n\n\n<p>Here\u2019s a detailed look into how that works:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">All-in-one UI Testing Tool<\/h3>\n\n\n\n<p>Automated tests created in Rainforest navigate through the app on the visual layer just like a user would\u2014looking for buttons, clicking on links, putting text into forms, etc.&nbsp;<\/p>\n\n\n\n<p>Rainforest validates the visual content by looking for precise screenshots of on-page elements (like a sign-up button), while also validating the overall functionality of the page by completing typical user actions.<\/p>\n\n\n\n<p>Instead of checking whether elements are present in the underlying code, Rainforest tests use pixel matching to complete each test step. To create a test or edit a step in an existing test, you would choose from a drop-down menu of actions (i.e. click, fill, etc.) and take small screenshots of the element you want to apply the action to.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/61b250fa0b013466232fafc2_Add%20a%20Click%20Action.gif\" alt=\"Try for Free button example in Rainforest QA\"\/><\/figure>\n\n\n\n<p>To start the test, you just hit \u201cRun Test\u201d and you\u2019ll automatically have access to our network of virtual machines to run your test on, allowing you to run hundreds of tests simultaneously.<\/p>\n\n\n\n<p>This makes it a true <strong>no-code testing solution <\/strong>that lets anyone\u2014including non-developers\u2014create, edit, and run tests.&nbsp;<\/p>\n\n\n\n<p>In addition to letting anyone test both the visual layer and the functionality of your app, Rainforest QA comes equipped with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Access to multiple operating systems and browsers, including current and older versions of Chrome, Firefox, Internet Explorer, etc.<\/li>\n\n\n\n<li>Jira integrations so you can automatically create tickets for tests that need debugging. Tickets include the failed test steps, a screenshot from the failed step, and a link back to the failed test in Rainforest.<\/li>\n\n\n\n<li>A CLI and integrations with CI tools (including Circle CI and GitHub) to incorporate Rainforest tests into any CI\/CD pipeline.<\/li>\n\n\n\n<li>An API to integrate your testing process into any software stack.<\/li>\n\n\n\n<li>Built-in test data like randomized email addresses, credit card numbers, names, etc.<\/li>\n\n\n\n<li>Integrations with Slack, Microsoft Teams, and email, so your team can get real-time notifications of test failures and other updates.<\/li>\n\n\n\n<li>A worldwide <a href=\"https:\/\/www.rainforestqa.com\/features\/crowdsourced-testing\" target=\"_blank\" rel=\"noopener\">community of human QA testers<\/a> available on-demand, 24&#215;7 for <a href=\"https:\/\/www.rainforestqa.com\/blog\/manual-vs-automated-testing\" target=\"_blank\" rel=\"noopener\">manual testing<\/a>. Many teams find this to be useful for tests that can\u2019t be automated or that need subjective feedback.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Results You Can Trust with Specific Screenshots, Smart Suggestions, and Text-matching<\/h3>\n\n\n\n<p>Many tools that use screenshots to verify visual elements compare screenshots of the entire page or of large sections of the page. With Rainforest tests, you take the screenshots yourself (rather than letting the tool take the screenshot for you) so they can be as large or as small as you choose. Then, the test only checks the box of pixels that you defined in the test.&nbsp;<\/p>\n\n\n\n<p>That means that there can be minor changes to <em>other sections<\/em> of the page, and the test will pass as long as all the elements you included in the screenshot were present. If you take a small screenshot that only includes the element (and not any of the surrounding area), the test will pass even if the location of the element is changed.<\/p>\n\n\n\n<p>For example, in the image below, the screenshot of the \u2018Start for free\u2019 button is limited to only what is contained in the button (i.e., text and color).&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/62153957058a1e82eb675d6d_start-for-free-test-1.png\" alt=\"\"\/><\/figure>\n\n\n\n<p>If your screenshot includes some of the background and surrounding elements (as seen in the next image), the test will be sensitive to the position of the element relative to the background and other elements included in the screenshot.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/6215396b5de56dbabe09bd7c_start-for-free-test-2.png\" alt=\"\"\/><\/figure>\n\n\n\n<p>If the test does fail, Rainforest highlights the failed test step and makes suggestions for a new screenshot based on the closest match found.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/621539aefa399b3af9326251_attempted-to-find-match.png\" alt=\"Attempted to find a match: &quot;Talk to a human button&quot; was changed to &quot;Talk to Sales&quot;\"\/><\/figure>\n\n\n\n<p>This example shows a fairly obvious difference (someone updated the copy on this page to say \u201cTalk to Sales\u201d instead of \u201cTalk to a human\u201d), however, there can be cases where the difference isn\u2019t immediately obvious (one letter is serifed while the others are san-serif, for example).&nbsp;<\/p>\n\n\n\n<p>In these cases, Rainforest helps you compare the differences between the two screenshots by layering them one on top of the other.&nbsp;&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/621536086650d1dc1252a7ca_where-to-button.gif\" alt=\"&quot;Where to?&quot; Button test in Rainforest QA\"\/><\/figure>\n\n\n\n<p>If you want to update the screenshot, all it takes is a click of your mouse.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/621539e8c0d806344fe69141_update-action-screenshot.png\" alt=\"Update action screenshot: Replace the action screenshot with the closest match found or crop your own new screenshot.\"\/><\/figure>\n\n\n\n<p>You may run into situations where you want to make sure the test will pass even if there are some visual changes. Let\u2019s say you updated the styling (font, color, shapes, etc.) of your app to reflect a rebrand, but you haven\u2019t updated your test suite yet. Since all of the buttons now have different styling, the visual changes will trigger failures across your test suite.&nbsp;<\/p>\n\n\n\n<p>To provide more flexibility in situations like this, Rainforest offers <a href=\"https:\/\/help.rainforestqa.com\/docs\/text-matching\" target=\"_blank\" rel=\"noopener\">text matching<\/a> to allow tests to pass even if there have been minor changes to visual elements. You can toggle text matching on or off for any test step.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/61e87ebca2109d4dfdb31937_visual-regression-testing-9.png\" alt=\"\"\/><\/figure>\n\n\n\n<p>With text matching turned on, Rainforest will use optical character recognition (OCR) to search for text in the element in your screenshot if it can\u2019t find an exact match of the screenshotted element. If it finds the matching text anywhere on the screen, the test step will pass. Even so, you\u2019ll be notified in the test results page that there was a visual change (see the Element Mismatch warning in the screenshot below), letting you know that you need to update the screenshots.&nbsp;<\/p>\n\n\n\n<p>And if you didn\u2019t intend to change the styling of your buttons, you\u2019ll have a chance to investigate the change before pushing code to production.&nbsp;<\/p>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/62153d923450457220bba12a_rainforest-signup-flow-element-mismatch.png\" alt=\"Rainforest Signup Flow: Element Mismatch Example\"\/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Easy Failure Categorization with Video Replays<\/h3>\n\n\n\n<p>Being able to see exactly how a test played out is often crucial to finding and fixing visual bugs. Often teams need to see test steps that led up to or follow the failed test step in order to understand why the test failed. Additionally, it can often be helpful to compare a failed test run to a successful test run to see where the change occurred.&nbsp;<\/p>\n\n\n\n<p>This is why Rainforest automatically records a video of every test it runs (regardless of whether the test passes or fails). When a test fails, you can review the video to see the actual point of failure and everything leading up to (and following) it.<\/p>\n\n\n\n<p>With many automated software testing tools, you might have to sort through lines of code in order to identify why a test failed. With Rainforest, anyone can look at test results and video recordings, know exactly what happened in the test, and quickly understand why the test failed.&nbsp;<\/p>\n\n\n\n<p><em><a href=\"https:\/\/www.rainforestqa.com\/talk-to-sales\">Talk to us<\/a> about setting up a Rainforest plan that&#8217;s right for you.<\/em><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Code-based_Tools_with_Screenshot_Plugins_for_Visual_Validation\"><\/span>Code-based Tools with Screenshot Plugins for Visual Validation<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>We\u2019ll now discuss some UI testing tools that take a traditional code-based approach to verifying the functionality of elements in the UI, but use screenshots to verify the appearance of the app.<\/p>\n\n\n\n<p>A few common test automation tools that use screenshots for visual validation are:<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Squish<\/h3>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/6215365388ed864b254e2d1a_squish-froglogic-homepage.png\" alt=\"Squish by Froglogic homepage: Automated GUI Testing that works.\"\/><\/figure>\n\n\n\n<p>Squish is a record-and-playback tool that supports JavaScript, Perl, Python, and Ruby with screenshot checkpoints. This means it records your movements in code as you manually click through a user path. When you playback your recording, the tool just executes the code it generated. Then, at any point, you can verify an element using a screenshot or lines of code.&nbsp;<\/p>\n\n\n\n<p>When using the screenshot option, it automatically takes a screenshot of the whole screen. If this doesn\u2019t fit your need, you can either \u201ccut out\u201d areas that the test should ignore or simply retake a smaller screenshot. Additionally, you can set how strict of a match the test requires to pass.<\/p>\n\n\n\n<p>Each part of the test (other than the actual screenshot) is turned into code.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Applitools<\/h3>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/6215367281ab48631deb2579_applitools-homepage.png\" alt=\"Applitools homepage: Next generation test automation platform powered by Visual AI\"\/><\/figure>\n\n\n\n<p>Applitools is a plugin that lets you work with nearly any test runner (Applitools supports more than 40 application testing frameworks and languages) to insert visual checkpoints with just one line of code (generated for you by Applitools) into any step in an automation test script.&nbsp;<\/p>\n\n\n\n<p>Applitools takes a screenshot of the entire UI and lets you choose between four levels of sensitivity: exact, strict, content, or layout. If none of these levels work for you, you can also manually \u2018carve out\u2019 areas of the UI the test should ignore. Overall, Applitools relies more heavily on programming skills than other visual testing tools.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Ranorex Studio<\/h3>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/6215368d69e762914749e9fb_ranorex-homepage.png\" alt=\"Ranorex homepage: Get a free trial of Ranorex Studio\"\/><\/figure>\n\n\n\n<p>Ranorex is another record-and-playback tool for desktop, mobile, or web applications. You can use the basic record-and-playback feature to create tests entirely written in code, or you can take screenshots to verify visual elements.&nbsp;<\/p>\n\n\n\n<p>Ranorex offers a variety of settings that let you choose how to compare the screenshots, such as pixel by pixel or by overall shapes. You can also choose to have the test look for the screenshot in one specific area of the screen or in any area of the screen.&nbsp;<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">PhantomCSS<\/h3>\n\n\n\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/uploads-ssl.webflow.com\/60da68c37e5767dfb65004c0\/621536a6806a9133bf83514f_phantomcss-github.png\" alt=\"PhantomCSS in GitHub Repository example\"\/><\/figure>\n\n\n\n<p>PhantomCSS is an open source tool built on top of PhantomJS\/CasperJS. It can define the steps of the test script so you can navigate around your app, and then it takes screenshots of each step and uses ResembleJS to compare the images to a baseline.<\/p>\n\n\n\n<p>Unlike other visual tools, PhantomCSS doesn\u2019t offer any features to mitigate sensitivity\u2014you will be notified of <em>any<\/em> inconsistencies.&nbsp;&nbsp;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Code-based_Tools_with_No_Visual_Validation\"><\/span>Code-based Tools with No Visual Validation<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>The following code-based tools are considered UI testing tools, but they offer very few features to test the appearance of an application, so many teams supplement their testing efforts with manual testing or a screenshot plugin from the previous list.&nbsp;<\/p>\n\n\n\n<p>The main advantage of these tools is that you can perform cross-browser testing. Since each browser renders the visual layer of a website with slight differences, it\u2019s difficult to create one test that can validate the visual UI across multiple browsers. But if you\u2019re only checking the functionality of the underlying code, it is possible to write one test and run it through multiple browsers. A few common code-based UI testing tools are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Selenium IDE: <\/strong>Selenium is one of the oldest testing frameworks available. Selenium IDE is the open source record-and-playback version of Selenium.<\/li>\n\n\n\n<li><strong>Appium: <\/strong>Appium is an open source tool built off of Selenium specifically for Android and iOS mobile apps.<\/li>\n\n\n\n<li><strong>Cypress:<\/strong> Cypress is an open source tool made specifically for developers writing tests in JavaScript.<\/li>\n\n\n\n<li><strong>Katalon Studio:<\/strong> Katalon Studio is a popular record-and-playback tool built on the Selenium WebDriver.<\/li>\n\n\n\n<li><strong>AutoIt:<\/strong> AutoIt is a free scripting language for automating interactions with the GUI.<\/li>\n\n\n\n<li><strong>MicroFocus Unified Functional Testing (UFT):<\/strong> UFT is a record-and-playback tool that only supports the VBScript testing language.<\/li>\n\n\n\n<li><strong>TestComplete:<\/strong> TestComplete lets you write test cases yourself using an object repository or using their record-and-playback feature in JavaScript, Python, VBScript.<\/li>\n\n\n\n<li><strong>Eclipse:<\/strong> Eclipse is an open source functional testing tool based on Java for testing SWT, Eclipse and GEF-based applications.<\/li>\n\n\n\n<li><strong>TestProject:<\/strong> TestProject is a free record-and-playback tool for web, mobile, and API testing.&nbsp;<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Get Started with True UI Testing with Rainforest QA<\/h2>\n\n\n\n<p>With a good UI test tool, you can be confident your app is free of visual bugs while also testing the usability of your application. Rainforest QA\u2019s no-code automated testing platform lets you build regression tests that automatically check the visual components of your app. It\u2019s a scalable, all-in-one quality assurance solution that\u2019s appropriate for small teams just getting started with automated GUI testing or QA-mature teams practicing continuous integration and regularly running 500+ automated software tests.<\/p>\n\n\n\n<p><a href=\"https:\/\/www.rainforestqa.com\/talk-to-sales\">Talk to us<\/a> about setting up a Rainforest plan that fits your needs.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This post helps you choose the best UI testing tool for testing both the functionality and the visual layer of your application.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-380","post","type-post","status-publish","format-standard","hentry","category-test-automation"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/posts\/380","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/comments?post=380"}],"version-history":[{"count":9,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/posts\/380\/revisions"}],"predecessor-version":[{"id":3071,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/posts\/380\/revisions\/3071"}],"wp:attachment":[{"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/media?parent=380"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/categories?post=380"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rainforestqa.com\/blog\/wp-json\/wp\/v2\/tags?post=380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}