Skip to content

442 — should check ${variant.name} report

Description

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

Preconditions

  • Signed-in tenant owner Octavia Wolff on a 1920×1080 viewport.
  • Seeded test data: 4 clients, 4 simple projects, 6 tasks and 11 time records spread across all four projects, plus three TRs that have no project, covering the current/neighbouring weeks and wider year.
  • Reports page is open with the Projects tab active.

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 table updates accordingly.
  2. Re-fetch time records and projects from the API. Expected: the summary header matches the aggregate of API time records inside the variant's window, grouped by project.
  3. Expected: the Projects table shows 4 rows — every seeded project is listed.
  4. Build the expected per-project summaries (project title, client, hours, billable, cost) from the API. Expected: each project row matches its expected summary.
  • Spec: playwright/tests/integration/reports.spec.ts (line 464)
  • Spec: playwright/tests/integration/reports.spec.ts (line 464)