<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Quality Assurance on code.kiwi.com</title><link>https://code.kiwi.com/tag/quality-assurance/</link><description>Recent content in Quality Assurance on code.kiwi.com</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 17 Mar 2023 19:48:55 +0000</lastBuildDate><atom:link href="https://code.kiwi.com/tag/quality-assurance/index.xml" rel="self" type="application/rss+xml"/><item><title>Skip the UI using API calls</title><link>https://code.kiwi.com/articles/skip-the-ui-using-api-calls/</link><pubDate>Thu, 11 Feb 2021 19:27:00 +0000</pubDate><guid>https://code.kiwi.com/articles/skip-the-ui-using-api-calls/</guid><description>&lt;p&gt;As a QA engineer who would like to start with test automation, the first thing you will learn is how to interact with the page and write automated scripts to replay your actions. But following this path, you may fall into the trap of automating all the actions in your automated tests only through the user interface (UI).&lt;/p&gt;</description></item></channel></rss>