https://krkn-chaos.dev/tags/testing/Recent content in Testing on KrknHugoenhttps://krkn-chaos.dev/docs/developers-guide/testing-changes/Mon, 01 Jan 0001 00:00:00 +0000https://krkn-chaos.dev/docs/developers-guide/testing-changes/<p>Test the behavior at the layer you changed, then verify the next integration boundary. A correct Python method does not prove that its image can be discovered or started by the operator.</p> <p>The <a href="https://krkn-chaos.dev/docs/developers-guide/custom-scenario/">hands-on lab</a> supplies the concrete build and run commands. Use this page when deciding what evidence a scenario change needs before contribution.</p> <h2 id="testing-changes-in-krkn"> Plugin and engine tests <a class="td-heading-self-link" href="#testing-changes-in-krkn" aria-label="Heading self-link"></a> </h2> <p>For the development scenario, cover:</p> <ul> <li>A valid configuration and an existing namespace, including one with no pods.</li> <li>A missing namespace and a Kubernetes API failure.</li> <li>Invalid <code>wait</code> values: negative, above 60, fractional, boolean, or missing.</li> <li>Missing or invalid namespace values and unreadable or malformed YAML.</li> <li>The expected return code and useful error context for each failure.</li> </ul> <p>Mock the sleep and cluster helper in unit tests so they remain fast and do not depend on credentials. Verify externally meaningful behavior such as whether pods are listed after a successful namespace check, rather than reproducing the implementation&rsquo;s internal steps in the test.</p>