<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI-Assisted Development on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/ai-assisted-development/</link><description>Recent content in AI-Assisted Development on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/ai-assisted-development/index.xml" rel="self" type="application/rss+xml"/><item><title>Comprehensive Testing Strategies for Production-Ready Apps</title><link>https://ai-blog.noorshomelab.dev/angular-mastery-enterprise-ai-2026/testing-strategies-production/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-mastery-enterprise-ai-2026/testing-strategies-production/</guid><description>&lt;h2 id="building-confidence-comprehensive-testing-for-enterprise-angular"&gt;Building Confidence: Comprehensive Testing for Enterprise Angular&lt;/h2&gt;
&lt;p&gt;Welcome back, future Angular architect! So far, we&amp;rsquo;ve explored how to build robust, modular, and reactive Angular applications using modern techniques like Standalone Components and Signals. But what happens when your application grows to hundreds of components, dozens of services, and a team of developers? How do you ensure that new features don&amp;rsquo;t break existing ones, or that a refactor doesn&amp;rsquo;t introduce subtle bugs?&lt;/p&gt;</description></item></channel></rss>