Skip to content

Fix the five failing web unit tests and the ranking pages card overflow - #27

Merged
jadhavgaurav merged 4 commits into
mainfrom
develop
Nov 5, 2026
Merged

jadhavgaurav merged 4 commits into
mainfrom
develop

Conversation

@jadhavgaurav

Copy link
Copy Markdown
Contributor

Why

PR 26 merged but nothing deployed: the web checks on main fail on five old unit tests, and the deploy workflow skips a release whose checks fail. This PR fixes them, plus one popup bug.

Changes

  • Ranking pages card: a fixed table layout keeps a long page path inside the card (it truncates, the full path is in the title). The card has one Rank column, for the device shown.
  • Unit tests that failed CI on main:
    • the rank strip test follows the mock's current counts
    • the rank bucket test counts the desktop rows the table shows (one device at a time)
    • the invite test uses a refusal the mock still gives (a password may contain the email name now)
    • the mock's budget month follows Date.now, so a month change does not move it
  • Comments in the rank strip now say its count is of the device shown.

Checks

Lint, typecheck, format check and the full unit suite pass locally. The one local failure is the dash check on an untracked, generated apps/web/AGENTS.md that CI does not have.

Deploy

Unchanged: backend first, then web. The backend run on main was cancelled during its tests last time, so watch that one.

… card

The page column truncates with the full path in its title, and the rank column
has a fixed width. Also correct the strip's comments: its count is of the
device shown.
The strip test follows the mock's current counts, the bucket test counts the
desktop rows the table shows, the invite test uses a refusal the mock still
gives (a password may contain the email name now), and the mock's budget month
follows Date.now so a month change does not move it.
@vercel

vercel Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
idraft-preview Ready Ready Preview Nov 5, 2026 10:38am UTC
1 Skipped Deployment
Project Deployment Actions Updated
idraft-site Ignored Ignored Preview Nov 5, 2026 10:38am UTC

Request Review

… timeout

The backend job ran 4,120 tests one at a time and needed about 45 minutes, so it hit
its 15 minute limit on every run and no image was ever pushed. With pytest-xdist on
4 workers (each with its own PostgreSQL, Redis and object store containers) the full
suite with coverage takes 7.5 minutes on a 4-CPU machine. The job limit goes to 30
minutes for a slower runner.

The workflow also runs when infra/compose/postgres/initdb changes, because the tests
build their database from those role scripts.
CI: backend tests on 4 workers, so the job finishes inside its timeout
@jadhavgaurav
jadhavgaurav merged commit 717f1f0 into main Nov 5, 2026
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant