J B Rainsberger Integrated Tests Are A Scam HD
Channel:Christopher Cabanne · Length:1:04:35 · Published:2015-08-07 · Views:49199
Summary
J. B. Rainsberger argues that large integrated tests are a scam: they are slow, fail opaquely, and give a false sense of coverage. He advocates focused collaboration and contract tests at boundaries instead.
Why HN recommends it
HN recommends it in testing-strategy debates as the classic case for fewer integration tests and more small, well-contracted unit tests.
JBRainsberger has an nice talk on them [1]. — HN, 2022
Software architecture & design · Testing, debugging & developer tools
Subtitles (excerpt)
Integrated tests are a scam. A self-replicating virus that invades your projects. It threatens to destroy your code base, to destroy your sanity, to destroy your life. Good evening. My name is Joe Rainsberger, also known as JBrains. Uh here's how you can Well, no, that's not how you can find me. Here is how you can find me. And I want to talk to you a little bit about a deep technical problem with uh perhaps some surprising solutions. Now, before I get started, I would really like to take an opportunity uh to recognize James Grenning. Uh I haven't seen James in a while. I went to his XP for a day tutorial at XP Universe Conference 2001 in Raleigh, North Carolina, USA. It was the first time that I got to meet many of the people who are pioneers in extreme programming and what now today we call Agile software development methods. And I feel very privileged to have had the chance to learn directly from the pioneers in this area. And one of the things that I want to share with you, um I've been doing a lot of keynotes about bigger issues and about people issues and about organizational issues and about where I think the Agile software development industry should go in the next 10 years.
On Hacker News
I've tried FitNesse professionally. I think it comes short in many regards. To be clear, I think integrated/integration tests in their own only add value if you have a couple of them (meaning <5). Otherwise, they're red and no one knows why. And they take a whole lot of time to execute. JBRainsberger has an nice talk on them [1]. Pactflow have implemented a Contract/Collaboration framework called… — mihaigalos, 2022-09
Sure. I'd venture to say that integration tests should be fewer than unit tests, see hexagonal etc. Hopefully those external interfaces are also more stable, so they don't need to be run as often. I tend to use my integration tests also as characterization tests that verify the simulator/test-double I use for any external systems within my unit tests. See also: the testing pyramid[1] and "integra… — mpweiher, 2018-07
I have adopted the same philosophy. A few resources on this, part of the so-called London school TDD: - [LINK] (and the rest of the Wiki) - [LINK] - Most of the screencasts and articles at [LINK] (especially this brilliant talk [LINK] ) - Integration Tests Are A Scam: [VIDEO] All of these basically go the opposite way of the article's philosophy: Not too many integration tests, mostly unit tests.… — 1_player, 2017-10
Trying to cover your state space with coarse-grained tests in database-backed applications can lead to slow tests suites that are laborious to set up/tear down, which is a barrier to fast build times in CI. This harms productivity both while writing tests and in deployment. J.B Rainsberger says it best: [VIDEO] — pooktrain, 2017-03
I think the big issue is. Are you writing a lib or an app? In library you don't need to mock. Library is supposed to be agnostic. In app there are many layers. You kinda need to mock them all, otherwise your app can't be tested. And then you have the problem that minor changes turn your tests red. So mocking is most useful in the place it has almost no impact. [VIDEO] — Ygg2, 2023-01
Related videos
- Ross's Game Dungeon: Deus Ex · Accursed Farms · 39:52
- The Vanishing of Flight 370 · LEMMiNO · 24:54
- How Does SHA-256 Work? · learnmeabitcoin · 22:59
- Writing a Wayland Compositor in Zig - Isaac Freund · Zig SHOWTIME · 42:19
- Ruby Midwest 2011 - Keynote: Architecture the Lost Years by Robert Martin · Confreaks · 1:06:38
- Economics of Nuclear Reactor · Illinois EnergyProf · 23:10
- Donald B. Gillies Lecture: Dr. Michael Stonebraker · Siebel School of Computing and Data Science · 1:05:45
- Alan Kay at OOPSLA 1997 - The computer revolution hasnt happened yet · Jeff Gonis · 1:04:33
- 2017/08/08: James Damore and his Google Memo on Diversity (complete) · Jordan B Peterson · 51:10
- RailsConf 2014 - All the Little Things by Sandi Metz · Confreaks · 38:47
- "Simple Made Easy" - Rich Hickey (2011) · Strange Loop Conference · 1:01:38
- "Making Impossible States Impossible" by Richard Feldman · elm-conf · 25:06
- "Testing Distributed Systems w/ Deterministic Simulation" by Will Wilson · Strange Loop Conference · 40:20
- 🚀 TDD, Where Did It All Go Wrong (Ian Cooper) · DevTernity Conference · 1:03:55
- Bret Victor - Inventing on Principle · Rui Oliveira · 54:20
- How To Design A Good API and Why it Matters · Google TechTalks · 1:00:19