No catch-all try/catch blocks that swallow errors

A try/catch block in a test that has no assertion, no throw, and no console.error converts every runtime error into a silent pass. When the production function throws — due to a network failure, a missing DB record, an uncaught null — the test catches it, discards it, and reports success. This pattern is common in AI-generated tests that wrap async calls defensively without understanding that swallowing errors in tests defeats the entire purpose of having tests. ISO-25010:2011 fault-tolerance requires that faults be detectable, not hidden.

Replace bare catch {} or catch { /* ignore */ } blocks in tests with either an expect(...).rejects.toThrow() assertion or a re-throw. Never discard an error inside a test:

// Before: fetchUser throwing is treated as success
it('fetches user', async () => {
  try {
    await fetchUser('123')
  } catch {
    // ignore
  }
})

// After: error path is explicitly asserted
it('throws for unknown user', async () => {
  await expect(fetchUser('does-not-exist')).rejects.toThrow('User not found')
})

// Or: surface real failures immediately
it('fetches user', async () => {
  const user = await fetchUser('123')
  expect(user.id).toBe('123')
})