Files
multica/packages/views/runtimes/components/usage-section.test.tsx
YYClaw 614dfae884 MUL-2488 feat(timezone): Scheduling / Viewing two-layer timezone architecture (#2968)
* docs(timezone): add scheduling/viewing timezone architecture RFC

* feat(db): replace daily rollups with task_usage_hourly, add user.timezone

Migrations 100-104: add "user".timezone (Viewing tz), build the UTC
hourly task_usage_hourly rollup with its pipeline, drop the legacy
task_usage_daily / task_usage_dashboard_daily pipelines, and drop the
agent_runtime.timezone column. Report queries now slice day boundaries
at read time by the caller-supplied @tz instead of materialising in a
fixed tz. Regenerate sqlc.

* feat(server): add task_usage_hourly backfill command

Replace the two legacy backfill commands (daily / dashboard_daily) with
a single backfill_task_usage_hourly that loads historical task_usage
into the new UTC hourly rollup, sliced per workspace.

* refactor(server): resolve viewing timezone in report handlers

Report handlers resolve the Viewing tz per request (?tz query param,
then user.timezone, then UTC) and pass it to the hourly-rollup queries.
Drop the UseDailyRollup feature flags and the old raw-scan/daily-rollup
dual paths, remove the /api/usage endpoints, and stop the daemon from
reporting and the runtime handler from accepting host timezone.

* refactor(core): switch report queries to viewing timezone

API client and dashboard/runtime queries send ?tz with each report
request, the user schema/types carry the new timezone field, and the
runtime timezone field/mutation is removed.

* feat(views): add viewing timezone preference and UI

Add the useViewingTimezone hook and a Timezone setting in Preferences;
report charts and the dashboard week boundary follow the viewer tz.
Remove the runtime detail timezone editor and its locale strings.

* fix(test): update fixtures and stabilize tests for timezone refactor

The timezone architecture refactor changed several types without
updating dependent test code:

- RuntimeDevice no longer has a timezone field — drop it from the
  create-agent-dialog runtime fixture.
- User now requires a timezone field — add it to the apps/web mockUser
  fixture.
- The PreferencesTab timezone tests asserted on the async save handler
  (PATCH then store update) with a bare expect, racing the mutation's
  settle callback, and timed out querying the Select's ~600-option IANA
  list on a loaded CI runner. Wrap the assertions in waitFor and extend
  the timeout for those three tests.

* docs(timezone): document self-host migration order and trigger invariant

Add a SELF-HOST UPGRADE ORDER runbook to the backfill command's package
comment: applying migrations 100-104 in a single migrate-up drops the
legacy daily rollups before the hourly backfill runs, leaving dashboards
empty until cron catches up.

Add an INVARIANT comment on trg_atq_dirty_hourly noting that agent_id
must be added to the trigger's OF list if it ever becomes mutable,
otherwise dirty buckets for the old agent_id are silently missed.

* style(runtimes): drop trailing blank line in runtime-detail
2026-05-21 15:33:47 +08:00

150 lines
4.6 KiB
TypeScript

// @vitest-environment jsdom
import type { ReactNode } from "react";
import { describe, it, expect, vi, beforeEach } from "vitest";
import { render, screen, fireEvent } from "@testing-library/react";
import type { AgentRuntime } from "@multica/core/types";
import { I18nProvider } from "@multica/core/i18n/react";
import enCommon from "../../locales/en/common.json";
import enRuntimes from "../../locales/en/runtimes.json";
const TEST_RESOURCES = { en: { common: enCommon, runtimes: enRuntimes } };
// The viewer's tz (Viewing layer) drives both the trend and the heatmap.
const VIEWER_TZ = "Asia/Tokyo";
// runtimeUsageOptions is the trend-fetch query. Capture its args so the
// test can assert which tz the trend was wired with.
const runtimeUsageOptions = vi.hoisted(() =>
vi.fn((..._args: unknown[]) => ({ kind: "usage" as const })),
);
const runtimeUsageByAgentOptions = vi.hoisted(() =>
vi.fn((..._args: unknown[]) => ({ kind: "by-agent" as const })),
);
vi.mock("../../common/use-viewing-timezone", () => ({
useViewingTimezone: () => VIEWER_TZ,
}));
vi.mock("@multica/core/runtimes/queries", () => ({
runtimeUsageOptions,
runtimeUsageByAgentOptions,
}));
vi.mock("@multica/core/workspace/queries", () => ({
agentListOptions: () => ({ kind: "agents" as const }),
}));
vi.mock("@multica/core/hooks", () => ({
useWorkspaceId: () => "ws-1",
}));
// custom-pricing-store is consumed two ways: usage-section reads the store
// hook, and runtimes/utils reads getCustomPricing(). The hook must be both
// callable and expose getState(), mirroring a real Zustand store.
vi.mock("@multica/core/runtimes/custom-pricing-store", () => {
const state = { pricings: {} as Record<string, unknown> };
const useCustomPricingStore = Object.assign(
(sel?: (s: typeof state) => unknown) => (sel ? sel(state) : state),
{ getState: () => state },
);
return { useCustomPricingStore, getCustomPricing: () => undefined };
});
// useQuery is mocked so the component renders synchronously with canned
// data — the `kind` tag on each query-options object routes the response.
vi.mock("@tanstack/react-query", async () => {
const actual =
await vi.importActual<typeof import("@tanstack/react-query")>(
"@tanstack/react-query",
);
const usageRows = [
{
runtime_id: "r-1",
date: "2026-05-19",
provider: "anthropic",
model: "claude-sonnet-4-6",
input_tokens: 1_000,
output_tokens: 0,
cache_read_tokens: 0,
cache_write_tokens: 0,
},
];
return {
...actual,
useQuery: (opts: { kind?: string }) => ({
data: opts?.kind === "usage" ? usageRows : [],
isLoading: false,
}),
};
});
// Charts are recharts-heavy; stub them. ActivityHeatmap echoes its `tz`
// prop so the test can read which tz the heatmap was wired with.
vi.mock("./charts", () => ({
DailyCostChart: () => <div data-testid="daily-cost-chart" />,
DailyTokensChart: () => <div data-testid="daily-tokens-chart" />,
WeeklyCostChart: () => <div data-testid="weekly-cost-chart" />,
WeeklyTokensChart: () => <div data-testid="weekly-tokens-chart" />,
ActivityHeatmap: ({ tz }: { tz: string }) => (
<div data-testid="heatmap-tz">{tz}</div>
),
}));
vi.mock("./custom-pricing-dialog", () => ({
CustomPricingDialog: () => null,
}));
import { UsageSection } from "./usage-section";
const RUNTIME: AgentRuntime = {
id: "r-1",
workspace_id: "ws-1",
daemon_id: null,
name: "test-runtime",
runtime_mode: "cloud",
provider: "claude",
launch_header: "",
status: "online",
device_info: "",
metadata: {},
owner_id: null,
visibility: "private",
last_seen_at: null,
created_at: "2026-05-01T00:00:00Z",
updated_at: "2026-05-01T00:00:00Z",
};
function Wrapper({ children }: { children: ReactNode }) {
return (
<I18nProvider locale="en" resources={TEST_RESOURCES}>
{children}
</I18nProvider>
);
}
describe("UsageSection — Viewing timezone wiring", () => {
beforeEach(() => {
runtimeUsageOptions.mockClear();
runtimeUsageByAgentOptions.mockClear();
});
it("fetches the trend in the viewer's tz", () => {
render(<UsageSection runtime={RUNTIME} />, { wrapper: Wrapper });
expect(runtimeUsageOptions).toHaveBeenCalled();
const [, days, tz] = runtimeUsageOptions.mock.calls[0]!;
expect(days).toBe(180);
expect(tz).toBe(VIEWER_TZ);
});
it("renders the heatmap in the viewer's tz", () => {
render(<UsageSection runtime={RUNTIME} />, { wrapper: Wrapper });
// The heatmap is an opt-in toggle inside the "When" card.
fireEvent.click(screen.getByRole("button", { name: "Heatmap" }));
expect(screen.getByTestId("heatmap-tz").textContent).toBe(VIEWER_TZ);
});
});