Files
OmniRoute/tests/unit/radar-supporter-gamification.test.ts
Diego Rodrigues de Sa e Souza 93265eede3 test(infra): retry recursive temp-dir removal on main (main twin of #11968) (#12246)
* test(infra): retry recursive temp-dir removal on main (main twin of #11968)

`main` has been red since b342c1a361 on the vitest and integration gates:

  ✖ tests/unit/autoCombo/provider-family-combos.test.ts > auto/<family>
  ✖ chat pipeline applies Codex OAuth fingerprint and priority tier inside combos

Both call resetStorage() from beforeEach, which does an fs.rmSync(TEST_DATA_DIR,
{recursive: true, force: true}) with no retry, and intermittently loses the race
with a not-yet-released SQLite handle (ENOTEMPTY).

release/v3.8.51 fixed this in #11968 with a mechanical codemod adding
maxRetries/retryDelay to every recursive rm/rmSync/rmdirSync under tests/, but
that PR landed only on the release branch. Because main only receives work at
the release squash, it stayed broken for the whole cycle — and repo-wide gates
then turn every open PR into main red on checks unrelated to their diff.

This is the --base main twin: re-runs the same codemod that already shipped on
the release branch (scripts/ad-hoc/codemod-rm-maxretries.mjs), so the two
branches converge on identical test-teardown semantics. Test-only; no product
logic is touched.

The remaining three failures reported on #12133 (unit full suite exceeding its
4800s ceiling, package-artifact exceeding 1200s, and the boot-smoke that is
skipped as a consequence) are runner-contention timeouts, not code defects —
validate-release-green.mjs runs those heavy gates concurrently on one shared
hosted runner. There is no fix to port for those.

* chore(scripts): carry the rm-maxretries codemod onto main alongside its output

The codemod that generated the previous commit lives in the repo on
release/v3.8.51 (added by #11968) but was never on main. Bringing it over keeps
the tool next to the change it produced, so the transformation stays
reproducible and auditable from either branch.
2026-09-01 01:48:00 -03:00

43 lines
1.7 KiB
TypeScript

import assert from "node:assert/strict";
import fs from "node:fs";
import os from "node:os";
import path from "node:path";
import test from "node:test";
const TEST_DATA_DIR = fs.mkdtempSync(path.join(os.tmpdir(), "omniroute-radar-supporter-"));
process.env.DATA_DIR = TEST_DATA_DIR;
const { getDbInstance, resetDbInstance } = await import("../../src/lib/db/core.ts");
const { BUILTIN_BADGES } = await import("../../src/lib/gamification/badges.ts");
const { emitGamificationEvent } = await import("../../src/lib/gamification/events.ts");
test.after(() => {
resetDbInstance();
fs.rmSync(TEST_DATA_DIR, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
});
test("Radar supporter has a dedicated badge and zero-XP idempotent action", async () => {
const identity = `radar:${"a".repeat(64)}`;
const badge = BUILTIN_BADGES.find((item) => item.id === "radar-supporter");
assert.ok(badge);
assert.equal(JSON.parse(badge.criteria).action, "radar_supporter");
await emitGamificationEvent({ apiKeyId: identity, action: "radar_supporter" });
await emitGamificationEvent({ apiKeyId: identity, action: "radar_supporter" });
const db = getDbInstance();
const userBadges = db
.prepare("SELECT badge_id AS badgeId FROM user_badges WHERE api_key_id = ?")
.all(identity) as Array<{ badgeId: string }>;
const xpRows = db
.prepare("SELECT action FROM xp_audit_log WHERE api_key_id = ?")
.all(identity) as Array<{ action: string }>;
const scoreRows = db
.prepare("SELECT score FROM leaderboard WHERE api_key_id = ?")
.all(identity) as Array<{ score: number }>;
assert.deepEqual(userBadges, [{ badgeId: "radar-supporter" }]);
assert.deepEqual(xpRows, []);
assert.deepEqual(scoreRows, []);
});