explaingit

abhivaikar/howtheytest

6,763TypeScriptAudience · developerComplexity · 1/5Setup · easy

TLDR

A curated index of blog posts, videos, and conference talks showing how real companies approach software testing and quality engineering, all gathered in one browsable place.

Mindmap

mindmap
  root((howtheytest))
    What It Is
      Curated index
      Blog posts and videos
      Conference talks
    Topics Covered
      Functional testing
      Chaos engineering
      CI/CD pipelines
      Site reliability
    Audience
      QA engineers
      Developers
      Engineering managers
    How to Use
      Browse by company
      Filter by topic
      Visit official site
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Browse testing strategies from hundreds of companies to inform your own QA approach before designing a test plan.

USE CASE 2

Research how companies handle chaos engineering or CI/CD pipelines for resilience and quality practices.

USE CASE 3

Find conference talks on a specific topic like mobile testing, site reliability, or automated testing.

Tech stack

TypeScript

Getting it running

Difficulty · easy Time to first run · 5min

In plain English

"How They Test" is a curated collection of publicly available resources showing how real software companies approach testing and quality engineering. The project gathers blog posts, videos, and conference talks from hundreds of companies around the world into one browsable index, so anyone curious about how professional engineering teams handle quality can find those materials without hunting across the internet. The README in this repository carries a notice: it is no longer actively maintained. The project has moved to an official website at abhivaikar.github.io/howtheytest/, which has current company listings, search and filtering tools, and a contribution form for adding new resources. The version shown in this repository is an older snapshot and may have outdated links. The original motivation behind the project was straightforward. Companies regularly share how they test software at conferences, on engineering blogs, and in meetups, but those resources end up scattered. There was no single place where someone could go and see, for example, what Airbnb does for Android testing alongside what Amazon does for chaos testing. This repository was created to be that central index. The topics covered are broad. You will find material on functional testing (checking that features work), automated testing, how continuous integration and delivery pipelines affect quality, chaos engineering (deliberately breaking things to test resilience), site reliability engineering, monitoring in production, and even user research from a product and design angle. Quality here means more than catching bugs before a release. The company list in the repository spans a wide range of industries and sizes, from smaller startups to large platforms, each entry linking to that company's public blog posts or recorded talks. The project's codebase is TypeScript, which supports the website rather than any testing framework itself. The full README is longer than what was shown.

Copy-paste prompts

Prompt 1
I am building a QA strategy for my startup. Based on resources like those indexed in howtheytest, what testing approaches do large companies commonly use for backend services?
Prompt 2
Using the patterns documented in howtheytest, help me write a testing plan template for a new REST API that covers unit, integration, and end-to-end tests.
Prompt 3
What does howtheytest document about chaos engineering practices? Help me apply those ideas to make my own service more resilient.
Prompt 4
I want to learn how companies run continuous integration pipelines for quality. Help me summarize the key practices from engineering blogs like those indexed in howtheytest.
Open on GitHub → Explain another repo

← abhivaikar on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.