<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="https://idle-ti.me/feed_style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <tabi:metadata xmlns:tabi="https://github.com/welpo/tabi">
        <tabi:base_url>https:&#x2F;&#x2F;idle-ti.me</tabi:base_url>
        <tabi:separator>
            •
        </tabi:separator>
        <tabi:about_feeds>This is a web feed, also known as an Atom feed. Subscribe by copying the URL from the address bar into your newsreader. Visit About Feeds to learn more and get started. It&#x27;s free.</tabi:about_feeds>
        <tabi:visit_the_site>Visit website</tabi:visit_the_site>
        <tabi:recent_posts>Recent posts</tabi:recent_posts>
        <tabi:last_updated_on>Updated on $DATE</tabi:last_updated_on>
        <tabi:default_theme></tabi:default_theme>
        <tabi:post_listing_date>date</tabi:post_listing_date>
        <tabi:current_section>chaos engineering</tabi:current_section>
    </tabi:metadata><link rel="extra-stylesheet" href="https://idle-ti.me/skins/lowcontrast_orange.css?h=43aaccb17d8ec616ace4" /><title>idle-ti.me - chaos engineering</title>
        <subtitle>Performance engineering &amp; observability — articles, curated tools, and projects by Jérôme Ramette.</subtitle>
    <link href="https://idle-ti.me/tags/chaos-engineering/atom.xml" rel="self" type="application/atom+xml"/>
    <link href="https://idle-ti.me/tags/chaos-engineering/" rel="alternate" type="text/html"/>
    <generator uri="https://www.getzola.org/">Zola</generator><updated>2026-06-11T00:00:00+00:00</updated><id>https://idle-ti.me/tags/chaos-engineering/atom.xml</id><entry xml:lang="en">
        <title>Reading Performance Testing by Use Case</title>
        <published>2026-06-11T00:00:00+00:00</published>
        <updated>2026-06-11T00:00:00+00:00</updated>
        <author>
            <name>Jérôme Ramette</name>
        </author>
        <link rel="alternate" href="https://idle-ti.me/blog/performance-testing-by-use-case/" type="text/html"/>
        <id>https://idle-ti.me/blog/performance-testing-by-use-case/</id>
        <summary type="html">Most performance-testing programmes have a load generator. Few have a representative dataset. Almost none can inject failures while measuring user-perceived latency. The reasons are multi-causal — a culture that treats performance as a release-time formality, plans that under-budget the supporting work, applications whose testability was never designed in, and a tool catalogue organised by category rather than by intent. This article reframes performance testing around seven use cases — API load testing in CI&#x2F;CD, full-stack validation, microservice resilience, database benchmarking, frontend optimisation, capacity planning, and pre-production data realism — and uses them as the spine of a practical campaign-setup guide: what each test is trying to prove, what testability hooks it requires, what it realistically costs, what cultural pre-requisites it has, and which combination of tools assembles it.</summary>
        </entry>
</feed>
