<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on Aiman Aizuddin</title><link>https://aimanaizuddin.com/tags/testing/</link><description>Recent content in Testing on Aiman Aizuddin</description><generator>Hugo</generator><language>en-MY</language><copyright>Copyright © 2026, Aiman Aizuddin.</copyright><lastBuildDate>Mon, 07 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aimanaizuddin.com/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Putting CI checks before a change becomes a release</title><link>https://aimanaizuddin.com/build-log/putting-ci-before-the-commit/</link><pubDate>Mon, 07 Sep 2026 00:00:00 +0000</pubDate><guid>https://aimanaizuddin.com/build-log/putting-ci-before-the-commit/</guid><description>&lt;p&gt;CI/CD is easy to describe as “automation that deploys code,” but the more valuable part comes earlier: it creates a repeatable way to catch a mistake before it becomes somebody else’s problem.&lt;/p&gt;
&lt;p&gt;For Ledgerlane, the workflow is split into two gates. Continuous integration runs on every pull request and on pushes to &lt;code&gt;main&lt;/code&gt; and &lt;code&gt;staging&lt;/code&gt;. Deployment is a separate workflow, with staging deploying from its branch and public environments requiring a deliberate manual release from &lt;code&gt;main&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>