Testing anti-pattern: merged setup data - Code with Jason

Link: Testing anti-pattern: merged setup data - Code with Jason: "In a single test file, there’s often overlap among the setup data needed for the tests in the file. For whatever reasons, perhaps in an effort to improve performance or avoid duplication, test writers often merge the setup code and bring it to the top of the file so it’s available to all test cases. […]"

Interesting. But I think it goes a little far in calling this an "anti pattern". I mean I see the point, but it's not so terrible that I would label it as anti.