News for hackers. Stuff that matters.
Re:Why frozen test fixtures are a problem on large projects ... by ozim on Tuesday December 09, 2025 @09:21AM (#46205190)
Inheritance everywhere leads to hell.

As much in applications code it is easy to curb, for test code it is just really hard to get people to understand all this duplication that should be there in tests is GOOD.

Re:Why frozen test fixtures are a problem on large projects ... by disgruntledphd2 on Tuesday December 09, 2025 @09:46AM (#46205450)
As always, there's a tradeoff. I used to go for doing all setup in each test for clarity, but one of my co-workers eventually convinced me that doing this in a fixture is better.

There'll always be some duplication, but too much makes it harder to see the important stuff in a test.

Re:Why frozen test fixtures are a problem on large projects ... by bluGill on Tuesday December 09, 2025 @09:59AM (#46205617)
It depends on how much setup is done, and where it is. 10 tests that share a setup fixture are good. 100,000 starts to get unmaintainable.

I have lots of test fixtures each responsible for about 10 tests. It is very common to have 10-20 tests that share a startup configuration and then adjust it in various ways.

Re:Why frozen test fixtures are a problem on large projects ... by ozim on Wednesday December 10, 2025 @02:13AM (#46214994)
I guess one level of inheritance is bearable, downside is once you start, there will be people coming in later adding more.