Skip to content

433 — should check ${variant.name} report

Description

Verifies the Reports → Time records tab summary and row list for each period variant (default week, last week, next week, whole year). For every variant the UI totals (hours, billable, cost, profit) and each visible row must match the time-record data fetched from the API for that date range.

Preconditions

  • Signed-in tenant owner Octavia Wolff on a 1920×1080 viewport.
  • Seeded test data: 4 clients, 4 simple projects, 6 tasks (across projects 1–3), and 11 time records (TR0–TR10) spread across yesterday, today, tomorrow and the next several days — covering current week, neighbouring weeks and the wider year.
  • Reports page is open with the Time records tab active.

Steps

  1. Switch the report's date range to the variant under test — leave on the default current week, click the left arrow for last week, click the right arrow for next week, or open the date picker and click the year row for the whole year. Expected: the date range above the table updates to that period.
  2. Re-fetch all time records from the API for the active tenant. Expected: the summary header (total hours, billable amount, cost, profit) on the Time records page matches the aggregate of all API time records whose start falls inside the variant's from–to window.
  3. Build the expected per-row summaries (TR title, project, client, user, duration, billable, cost) for every API record inside the window. Expected: each row visible in the Time records table matches the expected row built from the API (titles, owners, durations and money values are all equal).
  • Spec: playwright/tests/integration/reports.spec.ts (line 297)
  • Spec: playwright/tests/integration/reports.spec.ts (line 297)