https://blog.abhipraya.dev/tags/integration-testing/Recent content in Integration-Testing on Daffa AbhiprayaHugoen-us© Daffa AbhiprayaThu, 09 Apr 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-c/s2w2-aptitude/Thu, 09 Apr 2026 00:00:00 +0700https://blog.abhipraya.dev/ppl/part-c/s2w2-aptitude/<h2 id="overview"> <a class="anchor" href="#overview" data-anchor="overview" aria-hidden="true">#</a> Overview </h2> <p>Sprint 2 Week 2 (April 3 to 9) was dominated by a mutation testing sprint: setting up mutmut and Stryker in CI, building integration test infrastructure from scratch, and writing mutation-killing tests. The week also delivered three application features and a meta-level improvement to AI workflow. Each area required learning at least one technology or concept not covered in standard Fasilkom coursework.</p> <hr> <h2 id="1-mutation-testing-with-mutmut-python"> <a class="anchor" href="#1-mutation-testing-with-mutmut-python" data-anchor="1-mutation-testing-with-mutmut-python" aria-hidden="true">#</a> 1. Mutation Testing with mutmut (Python) </h2> <p>Mutation testing is a technique where a tool injects small faults (&ldquo;mutants&rdquo;) into your source code (flipping operators, changing constants, removing lines) and checks whether your test suite catches each fault. If a test fails, the mutant is &ldquo;killed.&rdquo; If no test fails, the mutant &ldquo;survives,&rdquo; meaning your tests have a blind spot.</p>