<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Test on Software Factory</title><link>/tags/test/</link><description>Recent content in Test on Software Factory</description><generator>Hugo</generator><language>en</language><atom:link href="/tags/test/index.xml" rel="self" type="application/rss+xml"/><item><title>Assist Tests development</title><link>/use/practices/genai/test/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/use/practices/genai/test/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;a class="td-heading-self-link" href="#introduction" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;This practice shows how GenAI coding assistants can help &lt;strong&gt;design reliable,
reviewable, and maintainable tests&lt;/strong&gt; faster. It is intended for &lt;strong&gt;software
engineers and test engineers&lt;/strong&gt; who need to improve behavioral coverage, explore
edge cases, and strengthen confidence without losing human control. The
assistant is useful for generating candidate scenarios and draft tests, but
&lt;strong&gt;engineers remain responsible for correctness, relevance, determinism, and
&lt;a href="/get-started/glossary/#continuous-integration-and-continuous-delivery-cicd"&gt;CI&lt;/a&gt;

stability&lt;/strong&gt;. To get useful results, provide &lt;strong&gt;clear acceptance criteria&lt;/strong&gt;, the
&lt;strong&gt;system under test contract&lt;/strong&gt;, and the main &lt;strong&gt;project conventions and tooling
constraints&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Shift Left Testing</title><link>/use/practices/test/shift-left-approach/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/use/practices/test/shift-left-approach/</guid><description>&lt;p&gt;This guide provides a definition of Shift Left, outlines its benefits, explains how to implement it
and presents some pitfalls to avoid.&lt;/p&gt;
&lt;p&gt;&lt;img src="/use/practices/test/shift-left-approach/img/devops-shift-left.png" alt="“approach”"&gt;&lt;/p&gt;
&lt;h2 id="definition"&gt;Definition&lt;a class="td-heading-self-link" href="#definition" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Shift Left&lt;/strong&gt; refers to the practice of moving testing activities earlier
in the software development process.&lt;/p&gt;
&lt;p&gt;Instead of waiting until the end of the development cycle to test for defects,
Shift Left advocates for testing activities to begin as soon as possible.&lt;/p&gt;
&lt;p&gt;This approach is aligned with Agile and DevOps methodologies,
promoting ongoing testing throughout the development lifecycle.&lt;/p&gt;</description></item></channel></rss>