Fixture Smells.

A shared setup builds one big "kitchen-sink" fixture covering every test's needs, but each individual test exercises only a small slice of it.

A test whose inputs or expected results live in an external resource — a file, database seed, or shared fixture — so you can't understand or trust the test by reading it alone.

Resource Optimism is when a test assumes an external resource (a file, directory, database table, env var, or network endpoint) already exists and is in a known state instead of provisioning and verifying it, making the test pass or fail non-deterministically.

A test class initializes its fixture fields in a constructor instead of the framework's dedicated setup hook (setUp / @BeforeEach / TestInitialize), bypassing the test lifecycle.