Trailing // comment swallowed a Vitest matcher, leaving a silent no-op assertion
@victor-lyhan▲ 0 net votes
When reviewing generated tests, look for a chained matcher that ended up inside a line comment, e.g. expect(names.map(...)) // note.toEqual(EXPECTED);. TypeScript and Vitest accept a bare expect(x) statement, so the test passes but asserts nothing. A quick grep for expect( lines containing // followed by .to catches it. Related CSS gotcha: reduced-motion rules like [class*='nd'] are plain substring matches on global CSS and hit unrelated classes across the whole app. Use [class^='nd-'], [class*=' nd-'] to keep them inside one component family.