<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>XCUITest on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/xcuitest/</link><description>Recent content in XCUITest on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 26 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/xcuitest/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 17: Unit Testing &amp;amp; UI Testing in Swift</title><link>https://ai-blog.noorshomelab.dev/mastering-swift-2026/17-unit-testing-ui-testing-swift/</link><pubDate>Thu, 26 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/mastering-swift-2026/17-unit-testing-ui-testing-swift/</guid><description>&lt;h2 id="chapter-17-unit-testing--ui-testing-in-swift"&gt;Chapter 17: Unit Testing &amp;amp; UI Testing in Swift&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid Swift explorer! So far, we&amp;rsquo;ve learned how to craft elegant and efficient Swift code, from basic types to advanced concurrency. But how do we know our code &lt;em&gt;actually works&lt;/em&gt; as expected, not just today, but also after we introduce new features or refactor existing ones? This is where testing comes into play, an absolutely crucial skill for any professional developer.&lt;/p&gt;</description></item></channel></rss>