Skip to content

439 — should check ${variant.name} report

Description

Verifies the per-user detail report (Reports → Users → Octavia Wolff, the Individual reports view) for each period variant (default week, last week, next week, whole year). For every variant the individual summary and the four breakdown tables (by client, project, task, tag) must match the user-specific time records returned by the API.

Preconditions

  • Signed-in tenant owner Octavia Wolff plus one invited employee on a 1920×1080 viewport.
  • Seeded test data: 4 clients, 4 simple projects, 6 tasks, 3 tags and 11 time records covering the current/neighbouring weeks and wider year.
  • Reports page is open at the Users tab, owner row clicked, with the individual user-report page asserted to be visible.

Steps

  1. Switch the report's date range to the variant under test (default week / last week / next week / whole year). Expected: the date range above the report updates accordingly.
  2. Re-fetch this user's time-record and profile data from the API. Expected: the individual-user summary header matches the API aggregate for Octavia inside the variant's window.
  3. Expected: the "By client" breakdown lists every client Octavia logged time against in the window with matching hours and money values.
  4. Expected: the "By project" breakdown lists every project Octavia logged time against with matching totals.
  5. Expected: the "By task" breakdown lists every task Octavia logged time against with matching totals.
  6. Expected: the "By tag" breakdown lists every tag attached to Octavia's time records in the window with matching totals.
  • Spec: playwright/tests/integration/reports.spec.ts (line 407)
  • Spec: playwright/tests/integration/reports.spec.ts (line 407)