Skip to content

Job application tracker and AI-powered job search assistant. Helps job seekers manage their search journey with AI resume review, job matching, task logging, and application analytics, all while keeping your data private.

fix(dashboard): update Jobs heading and adjust activity count assertion in tests

Khuram Niaz0f5f812765cc
diff --git a/e2e/dashboard.spec.ts b/e2e/dashboard.spec.ts
index 3767fd6..136b089 100644
--- a/e2e/dashboard.spec.ts
+++ b/e2e/dashboard.spec.ts
@@ -138,16 +138,18 @@ test.describe("Dashboard page", () => {
).toBeVisible();
await expect(
- page.getByRole("heading", { name: "Jobs", exact: true }),
+ page.getByRole("heading", { name: "Jobs & Activity", exact: true }),
).toBeVisible();
- // exact: true — the weekly chart's Y-axis legend also renders
- // "JOBS APPLIED" (uppercase, via nivo axisLeftLegend), and getByText
- // matches case-insensitively by default, so it would otherwise resolve
- // to both elements.
- await expect(page.getByText("Jobs Applied", { exact: true })).toBeVisible();
-
+ // The merged donut's center reports the applied-job count for the active
+ // period. The job created above is applied today, so the default 7d tab
+ // must show at least one. Specs share a user, so don't assert an exact
+ // count. Match the count's own span: the center stacks hours, jobs and
+ // trend with no separators, so asserting on the container would match
+ // against a concatenation like "17h8 jobs14%".
await expect(
- page.getByRole("heading", { name: "Activities", exact: true }),
+ page
+ .getByTestId("jobs-activity-total")
+ .getByText(/^[1-9]\d* jobs?$/),
).toBeVisible();
await expect(