close<\/code> methods will use it.<\/p>\n\n\n\ndef go(self):
self.page.get(self.url)
def close(self):
self.page.close()<\/pre>\n\n\n\nNothing special here, but now you know: to make a webdriver object go to a web page, you use webdriver.get(url_of_page)<\/code>. We’ll see this in action soon. Also, the close<\/code> method closes the browser (really??).<\/p>\n\n\n\nThe next thing our BasePage<\/code> class needs is a way to grab elements. But before we get to that, we’re going to make the BaseElement<\/code> class and then come back to this one.<\/p>\n\n\n\nBaseElement Class<\/h2>\n\n\n\n
This is my favorite part. The BaseElement<\/code> well represent elements on a page such as buttons, input boxes, and other such things. It will also allow us to manipulate those objects, which is obviously a necessity when testing browser features.<\/p>\n\n\n\nOnce we’re on a page, we only need two things to select an element: the property we’re going to select it by, and the value of that thing. For example, if we want to enter text into an input box with an id of “username”, the by<\/code> is “id,” and the value<\/code> is “username”.<\/p>\n\n\n\nUsually, we do this by writing something like web_driver.find_element(By.ID, \"username\")<\/code> but there’s one thing we have to worry about.<\/p>\n\n\n\nWebdrivers are fast<\/em><\/strong> as heck. Sometimes our tests will fail because the test is looking for an element that has not yet rendered. The element could load only a split second after the test script tries to get it, but by then it’s too late, and the test will fail because it couldn’t find the element. <\/p>\n\n\n\nTo combat this, sometimes developers will put in sleep<\/code> commands. Every time you want to do that, I want you to slap yourself in the face with a newspaper and yell “no! bad developer!” <\/p>\n\n\n\nWe don’t use sleeps for two reasons. One, if you have 200 tests that interact with an average of 3 elements per test, and each time you select an element, you sleep for 2 seconds, your test can never run faster than 20 minutes. Two, you actually don’t know if your sleep is long enough. Maybe that element is having a hard day and takes 4 seconds to render but you only waited for 2. Luckily, there is a solution, so let’s just jump into the code.<\/p>\n\n\n\n
We’ll start with the constructor and the method that returns an actual web element object we can manipulate:<\/p>\n\n\n\n
from selenium.webdriver.support import expected_conditions as ec\nfrom selenium.webdriver.common.keys import Keys\nfrom selenium.webdriver.support.wait import WebDriverWait\n\n\nclass BaseElement:\n def __init__(self, by, value, driver, name=''):\n self.driver = driver\n self.by = by\n self.value = value\n self.name = name\n self.locator = (self.by, self.value)\n self.element = self.web_element()\n\n def web_element(self):\n return WebDriverWait(self.driver, 10).until(ec.visibility_of_element_located(locator=self.locator))<\/code><\/pre>\n\n\n\nThe solution to the problem of slow rendering web elements is in the web_element<\/code> method. Notice we use a method called WebDriverWait<\/code>. This comes from selenium and takes two parameters: a web driver object and a timeout. The timeout is the only time you’re allowed to hardcode seconds, and this attribute basically says “ok, after x amount of seconds, we’re just goonna assume the element isn’t rendering.” You can adjust this as you see fit.<\/p>\n\n\n\nWe also call the until<\/code> method which takes in an expected_conditions<\/code> object (which we’re calling ec<\/code> in the code above) property. In this case, we use the property of visibility_of_element_located<\/code> which basically says “when it shows up on the page” and pass it the element’s locator (which we’ll talk about in a second).<\/p>\n\n\n\nThis is all a fancy way of saying “give me this element as soon as it shows up on the page; if it takes more than 10 seconds, give up.”<\/p>\n\n\n\n
Also notice in the constructor we are creating a tuple called locator<\/code>. This is going to be populated with values that will come from the BasePage<\/code> object, but let’s talk about it real quick. The by<\/code> parameter will be translated in the BasePage<\/code> object to return an actual By<\/code> object, which could be Id, Xpath, class name, or a few other things. The “value” part of this tuple is the value of the Id, Xpath, class name or whatever of the element we’re trying to find. To reuse the example of the username input box, the locator tuple would be (\"id\", \"username\")<\/code>.<\/p>\n\n\n\nWhat good is having an element object if we can’t do stuff to it? Let’s finish up this class by adding some fairly self explanatory methods and one decorated method:<\/p>\n\n\n\n
def click(self):\n self.element.click()\n\ndef input_text(self, text):\n self.element.send_keys(text)\n\ndef clear(self):\n self.element.clear()\n\ndef clear_text(self):\n self.element.send_keys(Keys.CONTROL + 'a')\n self.element.send_keys(Keys.DELETE)\n\ndef select_drop_down(self, index):\n self.element.select_by_index(index)\n\n@property\ndef text(self):\n return self.element.text<\/code><\/pre>\n\n\n\n These methods manipulate the object and let us click, add text, and clear the object. One note about the clear_text<\/code> method: The pure clear<\/code> method does not always work the way you would expect, so this method essentially gets inside the element, types control+a (the keyboard shortcut for selecting all), and presses the delete key.<\/p>\n\n\n\nThe text<\/code> method lets us evaluate the text in the element and works for input boxes, paragraph elements, and just about anything else that might have text in it. The @property<\/code> line is called a “decorator” and to be honest with you, I have no idea what it’s for. But this code will not work without it. *shrug*<\/p>\n\n\n\nNow let’s head back to our BasePage<\/code> class and finish it out. We’re getting close to being done!<\/p>\n\n\n\nBack to BasePage<\/h2>\n\n\n\n
The last part of the BasePage<\/code> class will be the element_by<\/code> method in which we will take in “indicator” and “location” as arguments. The indicator will be used to get that By<\/code> object we talked about earlier, and the locator will be the value. Here’s the code:<\/p>\n\n\n\ndef element_by(self, indicator, locator):\n indicator = indicator.lower()\n indicator_converter = {\n \"id\": By.ID,\n \"xpath\": By.XPATH,\n \"selector\": By.CSS_SELECTOR,\n \"class\": By.CLASS_NAME,\n \"link text\": By.LINK_TEXT,\n \"name\": By.NAME,\n \"partial link\": By.PARTIAL_LINK_TEXT,\n \"tag\": By.TAG_NAME\n }\n return BaseElement(indicator_converter.get(indicator), locator, self.page)<\/code><\/pre>\n\n\n\nAs you can see, there are quite a few ways to identify an element outside of its Id.<\/p>\n\n\n\n
Side Note<\/h3>\n\n\n\n
I do want to caution you about one thing regarding selectors. Try to avoid using xpath when you can. The reason for this is because if an element changes places on a screen either by function or because of tweaks in design, your xpath patter has to change, making the test very fragile. Grab by unique IDs when you can.<\/p>\n\n\n\n
One More Thing<\/h2>\n\n\n\n
Before we write the test, I want you to write one more thing for the sake of keeping the code readable. Make a package called tests<\/code> and create 2 files, helpers<\/code> and test_feature<\/code>. We’re going to make one method in the helper class that will keep us from having a six foot wide line of code in our tests later. Here’s helpers.py<\/code>:<\/p>\n\n\n\nfrom selenium.webdriver.support import expected_conditions as ec\nfrom selenium.webdriver.support.wait import WebDriverWait\n\n\ndef evaluate_element_text(element, text):\n WebDriverWait(element.driver, 10).until(ec.text_to_be_present_in_element(element.locator, text))\n return element.text == text\n<\/code><\/pre>\n\n\n\nThis is going to take in an element object and some text we expect to have and return true or false. Instead of writing that long line every time we need to evaluate an element’s text, we’ll just call this method.<\/p>\n\n\n\n
See it in Action!<\/h2>\n\n\n\n
We are officially done building our framework and it’s time to write our first test script. Open test_features.py<\/code> and lets get started.<\/p>\n\n\n\nFirst, we do our imports, then we’ll do a little set up:<\/p>\n\n\n\n
import unittest\nfrom Configs import Config\nfrom Page import BasePage\nfrom tests import helpers as helper\n\n\nclass TestFeature(unittest.TestCase):\n cf = Config.Config()\n cf.base_url = 'erikwhiting.com'\n cf.subdomain = ''\n cf.base_url += '\/newsOutlet'\n bp = BasePage.Page(cf)<\/code><\/pre>\n\n\n\nThen, we can write all the tests for that page that we want. For our example, we’re going to go to the news site, enter “Hello” in the input box, click the transmit button, and then make sure the div that gets transmitted to has the word “Hello” in it. Behold!<\/p>\n\n\n\n
def test_write_and_click(self):\n bp = self.bp\n bp.go()\n bp.element_by(\"id\", \"sourceNews\").input_text(\"Hello\")\n bp.element_by(\"id\", \"transmitter\").click()\n english_div = helper.evaluate_element_text(bp.element_by(\"id\", \"en1\"), \"Hello\")\n self.assertTrue(english_div)\n bp.close()<\/code><\/pre>\n\n\n\nBasically, in the first part we instantiate our Config<\/code> object, and use it to create our BasePage<\/code> object. From there, the test script is pretty easy to write. We go()<\/code> to the URL, get the element with the ID “sourceNews” and input “Hello” into it. We find the element with the “transmitter” ID, and click()<\/code> it. Then we find the element with ID “en1”, send it to our helper method along with the text we expect, and then use the unittest<\/code> method assertTrue<\/code> to evaluate it.<\/p>\n\n\n\nIn a terminal in your project root, write:<\/p>\n\n\n\n
$> python -m unittest tests.test_configs<\/code><\/pre>\n\n\n\nand hit enter. See the browser go!<\/p>\n\n\n\n
Closing Remarks<\/h2>\n\n\n\n
Did that seem like a lot of work? Well, it may have been, but there’s some things to keep in mind. Not only are we getting elements in an efficient non-sleep way, but we are capturing a lot of functionality in just a couple of classes. All the automated tests we write from here on out will be a breeze, and that’s the real time saver.<\/p>\n\n\n\n
One more thing, a bit of a self plug. If you’re interested in this project, you are more than welcome to make a pull request on its github. The first goal of this project is to be as easy and configurable as possible. The second goal is to then be turned into a testing DSL to allow less technical users to write tests. No pressure though! Just throwing it out there.<\/p>\n\n\n\n
The Tests<\/h2>\n\n\n\n
Like I said earlier, I really wanted to do this tutorial in a TDD type of way, since I love<\/em><\/strong> TDD, but that would have made this already long article even more so. But, as promised, there are the tests that are included in the GitHub repo:<\/p>\n\n\n\ntest_config.py<\/code><\/p>\n\n\n\nimport unittest\nfrom Configs import Config\n\n\nclass TestConfigs(unittest.TestCase):\n\n test_url = 'eriktest.com'\n test_sub_domain = 'test'\n test_port = '5000'\n\n def test_config_returns_basic_url(self):\n cf = Config.Config()\n cf.base_url = self.test_url\n cf.subdomain = ''\n cf.port = ''\n self.assertEqual(cf.url(), 'http:\/\/' + self.test_url)\n\ndef test_config_returns_url_with_subdomain(self):\n cf = Config.Config()\n cf.base_url = self.test_url\n cf.subdomain = self.test_sub_domain\n cf.port = ''\n self.assertEqual(cf.url(), 'http:\/\/' + self.test_sub_domain + '.' + self.test_url)\n\n def test_config_returns_url_with_port_only(self):\n cf = Config.Config()\n cf.base_url = self.test_url\n\t\tcf.subdomain = ''\n\t\tcf.port = self.test_port\n\t\tself.assertEqual(cf.url(), 'http:\/\/' + self.test_url + ':' + self.test_port)\n\n def test_config_returns_url_with_port_and_subdomain(self):\n cf = Config.Config()\n cf.base_url = self.test_url\n cf.subdomain = self.test_sub_domain\n cf.port = self.test_port\n val_to_test = 'http:\/\/' + self.test_sub_domain + '.' + self.test_url + ':' + self.test_port\n self.assertEqual(cf.url(), val_to_test)\n<\/code><\/pre>\n\n\n\ntest_base_page.py<\/code><\/p>\n\n\n\nimport unittest\nfrom Configs import Config\nfrom Page import BasePage\n\n\nclass TestBasePage(unittest.TestCase):\n cf = Config.Config()\n cf.driver = 'TestDriver'\n cf.base_url = 'TestMe.com'\n\ndef test_base_page_returns_config_url(self):\n bp = BasePage.Page(self.cf)\n self.assertEqual(bp.url, self.cf.url())\n\ndef test_bast_page_returns_config_url_with_sub_dir(self):\n bp = BasePage.Page(self.cf, 'about')\n self.assertEqual(bp.url, self.cf.url() + '\/about')<\/code><\/pre>\n\n\n\ntest_feature.py<\/code><\/p>\n\n\n\nimport unittest\nfrom Configs import Config\nfrom Page import BasePage\nfrom tests import helpers as helper\n\n\nclass TestFeature(unittest.TestCase):\n cf = Config.Config()\n cf.base_url = 'erikwhiting.com'\n cf.subdomain = ''\n cf.base_url += '\/newsOutlet'\n bp = BasePage.Page(cf)\n\ndef test_write_and_click(self):\n bp = self.bp\n bp.go()\n bp.element_by(\"id\", \"sourceNews\").input_text(\"Hello\")\n bp.element_by(\"id\", \"transmitter\").click()\n english_div = helper.evaluate_element_text(bp.element_by(\"id\", \"en1\"), \"Hello\")\n self.assertTrue(english_div)\n bp.close()\n<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"Developers have unit tests to test atomic functionality and integration tests to test system interoperability. Web developers have to take it a step further and test actual browser behavior. This can be done in many ways, but most often it’s with some implementation of Selenium webdriver and an xUnit testing framework. In this article, I’m…<\/p>\n","protected":false},"author":1,"featured_media":119,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[17],"tags":[18,20,19,10],"class_list":["post-109","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-testing","tag-python","tag-tdd","tag-test-automation","tag-testing"],"aioseo_notices":[],"jetpack_featured_media_url":"https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2019\/09\/david-clode-RAfIk-ZKbPk-unsplash.jpg?fit=5886%2C3818&ssl=1","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/pb90KY-1L","jetpack-related-posts":[{"id":486,"url":"https:\/\/erikscode.space\/index.php\/2021\/09\/28\/improving-browser-automation-tests-how-to-add-microsoft-edge-and-edgedriver-to-linux-ci-systems\/","url_meta":{"origin":109,"position":0},"title":"Improving Browser Automation Tests: How to Add Microsoft Edge and Edgedriver to Linux CI Systems","author":"erik","date":"September 28, 2021","format":false,"excerpt":"Lately, the Microsoft Edge browser has been growing in popularity, recently unseating Firefox as the 3rd most popular web browser and approaching Safari in the number two spot. This means that any web application with a potentially wide user base should include MS Edge tests in its automated test suite.\u2026","rel":"","context":"In "SVC, CI\/CD, and More"","block_context":{"text":"SVC, CI\/CD, and More","link":"https:\/\/erikscode.space\/index.php\/category\/svc-ci-cd-and-more\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1559,"url":"https:\/\/erikscode.space\/index.php\/2023\/09\/16\/test-driven-development-with-python-a-primer\/","url_meta":{"origin":109,"position":1},"title":"Test-Driven Development with Python: a Primer","author":"erik","date":"September 16, 2023","format":false,"excerpt":"Making sure the software we build works the way we (and our customers) want it to work is called, unsurprisingly, software testing. Software testing is an enormous topic; indeed, there are entire books, courses, conferences, academic journals, and more about the topic. One can even make a career out of\u2026","rel":"","context":"In "Python"","block_context":{"text":"Python","link":"https:\/\/erikscode.space\/index.php\/category\/language-specific\/python\/"},"img":{"alt_text":"brown python","src":"https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/snake-ball-python-python-regius-beauty-53140.jpeg?fit=1200%2C827&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/snake-ball-python-python-regius-beauty-53140.jpeg?fit=1200%2C827&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/snake-ball-python-python-regius-beauty-53140.jpeg?fit=1200%2C827&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/snake-ball-python-python-regius-beauty-53140.jpeg?fit=1200%2C827&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/snake-ball-python-python-regius-beauty-53140.jpeg?fit=1200%2C827&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":126,"url":"https:\/\/erikscode.space\/index.php\/2019\/10\/14\/example-tdd-workflows\/","url_meta":{"origin":109,"position":2},"title":"Example TDD Workflows","author":"erik","date":"October 14, 2019","format":false,"excerpt":"This article isn't designed to sell you on the benefits of TDD, it is simply a tutorial (in Java and JUnit) to get you acclimated to the typical workflow. TDD can be counter-intuitive, so we'll go slow and keep it simple. Test Driven Development, or TDD, is a development process\u2026","rel":"","context":"In "Testing"","block_context":{"text":"Testing","link":"https:\/\/erikscode.space\/index.php\/category\/testing\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2019\/10\/TDDCycle.jpg?fit=833%2C654&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2019\/10\/TDDCycle.jpg?fit=833%2C654&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2019\/10\/TDDCycle.jpg?fit=833%2C654&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2019\/10\/TDDCycle.jpg?fit=833%2C654&ssl=1&resize=700%2C400 2x"},"classes":[]},{"id":232,"url":"https:\/\/erikscode.space\/index.php\/2020\/04\/20\/5-great-programming-books-rarely-mentioned-in-great-programming-books-articles\/","url_meta":{"origin":109,"position":3},"title":"5 Great Programming Books Rarely Mentioned in “Great Programming Books” Articles","author":"erik","date":"April 20, 2020","format":false,"excerpt":"Originally posted on dev.to If you search something like \"programming books\" or \"books developers should read\" you will get a lot of articles listing the same 5 or 6 books. In this article, I want to bring to your attention some stellar books on coding that don't get the love\u2026","rel":"","context":"In "Book Reviews and Suggested Reading"","block_context":{"text":"Book Reviews and Suggested Reading","link":"https:\/\/erikscode.space\/index.php\/category\/suggested-reading\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1729,"url":"https:\/\/erikscode.space\/index.php\/2023\/09\/25\/how-to-debug-code-with-python-examples\/","url_meta":{"origin":109,"position":4},"title":"How to Debug Code (with Python Examples)","author":"erik","date":"September 25, 2023","format":false,"excerpt":"Often in your programming career, you will inadvertently write flawed code that introduces some fault into your codebase. These faults are called bugs and the activity of fixing bugs is called \u201cdebugging.\u201d Of course, as developers, we try to write correct code every time, but writing bugs is simply a\u2026","rel":"","context":"In "Python"","block_context":{"text":"Python","link":"https:\/\/erikscode.space\/index.php\/category\/language-specific\/python\/"},"img":{"alt_text":"green yellow and red multicolored insect in close up photography","src":"https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/canthigaster-cicada-fulgoromorpha-insect-proboscis-60016.jpeg?fit=1200%2C926&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/canthigaster-cicada-fulgoromorpha-insect-proboscis-60016.jpeg?fit=1200%2C926&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/canthigaster-cicada-fulgoromorpha-insect-proboscis-60016.jpeg?fit=1200%2C926&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/canthigaster-cicada-fulgoromorpha-insect-proboscis-60016.jpeg?fit=1200%2C926&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2023\/09\/canthigaster-cicada-fulgoromorpha-insect-proboscis-60016.jpeg?fit=1200%2C926&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":343,"url":"https:\/\/erikscode.space\/index.php\/2021\/02\/01\/site-update-and-2021-roadmap\/","url_meta":{"origin":109,"position":5},"title":"Site Update and 2021 Roadmap","author":"erik","date":"February 1, 2021","format":false,"excerpt":"Good morning everyone, it's been a while since I've written a blog post. To keep you all informed, I'd like to make a quick post about where I've been and what the plans are for this year. Where Did eriksCodeSpace Go? The year 2020 was a crazy one for me\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2021\/02\/map.jpg?fit=1200%2C800&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2021\/02\/map.jpg?fit=1200%2C800&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2021\/02\/map.jpg?fit=1200%2C800&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2021\/02\/map.jpg?fit=1200%2C800&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/erikscode.space\/wp-content\/uploads\/2021\/02\/map.jpg?fit=1200%2C800&ssl=1&resize=1050%2C600 3x"},"classes":[]}],"_links":{"self":[{"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/posts\/109","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/comments?post=109"}],"version-history":[{"count":0,"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/posts\/109\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/media\/119"}],"wp:attachment":[{"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/media?parent=109"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/categories?post=109"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/erikscode.space\/index.php\/wp-json\/wp\/v2\/tags?post=109"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}