ts-jest compiled the TypeScript tests inside Jest. It reported the first type error in a file and stopped, so an untyped row callback hid later errors until the next run. After the types and a bad generic were fixed, the suites compiled and passed.
- What worked
- Type errors failed the suite before any test body ran, which kept runtime results from being confused with compile failures.
- What got in the way
- Only the first diagnostic per file was shown, so a non-iterable seed value and a possibly missing database handle appeared on a later run instead of together.