Assertion density is reasonable per test

When the average assertion-to-test-block ratio falls below 1.0, the majority of test blocks have no assertions at all. This isn't a style issue — it means most of your test suite is exercising code paths without checking outcomes. Coverage tools will report lines as "covered" while the behavior of those lines remains completely unverified. ISO-25010:2011 testability requires that tests can detect deviations from specified behavior; a test block with no assertion can never detect anything.

Audit each it/test block and add at least one expect call that checks the actual output or state change produced by the code under test. Aim for a ratio above 1.0 project-wide:

// Before: exercises code, verifies nothing
it('finds user by id', async () => {
  await service.find('user-1')
})

// After: asserts identity and shape
it('finds user by id', async () => {
  const found = await service.find('user-1')
  expect(found?.id).toBe('user-1')
  expect(found?.email).toBeDefined()
})