Skip to content

437 — should check ${variant.name} report

Description

Verifies the Reports → Users tab (Simple reports view) summary and user list for each period variant (default week, last week, next week, whole year). For every variant the UI totals and per-user aggregates must match the data fetched from the API for that range.

Preconditions

  • Signed-in tenant owner Octavia Wolff plus one invited employee (2 users total) on a 1920×1080 viewport.
  • Seeded test data: 4 clients, 4 simple projects, 6 tasks and 11 time records split between the owner and the employee across the current/neighbouring weeks and wider year.
  • Reports page is open with the Users tab active.

Steps

  1. Switch the report's date range to the variant under test (default week / last week / next week / whole year via the arrows or year picker). Expected: the date range above the table updates accordingly.
  2. Re-fetch time records and the employee list from the API. Expected: the summary header on the Users tab matches the aggregate of API time records inside the variant's window, grouped by user.
  3. Expected: the Users table shows 2 rows — owner Octavia Wolff and the invited employee.
  4. Build the expected per-user summaries (name, hours, billable, cost) from the API and assert each table row matches. Expected: every user row matches its expected summary.
  • Spec: playwright/tests/integration/reports.spec.ts (line 363)
  • Spec: playwright/tests/integration/reports.spec.ts (line 363)