Fixed flaky comments test by pinning created_at

[EvanHahn]

no ref

This is a test-only change.

I think Claude Opus 4.7's explanation is reasonably good:

The test at comments.test.js:1362 uses dbFns.addCommentWithReplies to create a parent comment and a reply back-to-back without explicit created_at values. Both rows rely on the model's default timestamp (new Date() at save time).

The admin browseAll controller at comments-controller.js:166 sorts by created_at desc and the SQL has no secondary tiebreak. When the two inserts land in the same millisecond, MySQL happens to return rows in insertion order (parent first, reply second), which matches the stored snapshot [commentMatcher, commentMatcherWithParent]. When the reply spills into a newer millisecond, desc puts the reply first — the snapshot then sees parent (reply's parent object) missing from index 1 and the assertion fails exactly as in the CI log.

[coderabbitai]

Walkthrough

The test file for the comments API endpoint is updated to include explicit created_at timestamps for test comment data. The expected response snapshot is adjusted to reflect the resulting sort order, where the reply comment appears before the parent comment based on descending timestamp ordering. No public APIs or exported declarations are modified by these test-only changes.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: fixing a flaky test by pinning the created_at timestamps for deterministic test ordering.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The pull request description clearly explains the test-only changes, the root cause of the flakiness, and how the fix addresses it.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-flaky-test-with-comment-ordering

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud