Test report — dujap-1320-job-boost-level-parity on local

Date: 2026-09-25 07:35 (UTC+7)
Environment: local — API http://localhost:3000/api, admin http://localhost:3001, app dev flavor on emulator emulator-5554 (Android 16), shared dev-postgres DB japp + dev-redis DB 0 + MinIO
Code under test (all on feat/DUJAP-1320-job-boost-level-parity, which includes the DUJAP-1320 assign change):
- backend 776c646 (running npm run start:dev started by the user)
- admin 2604902 (dev server started by the user); admin re-run on 77a3afc (fix commit, hot-reloaded)
- app 29db707 (APK rebuilt during this run, see "Environment actions")
Driver: Claude in Chrome no. The extension was not connected (0 browsers), so the admin scenarios ran in headless Chrome driven over CDP, which is the same approach as the DUJAP-1320 assign report. Backend: Node fetch (curl-equivalent). App: adb taps + screenshots, plus the app's own unit/widget tests.
Result: 72 PASS · 0 FAIL · 1 SKIP · 0 BLOCKED · 0 n/a (73 scenarios). After the first run: 71 PASS · 1 FAIL; the failure was fixed and the admin suite re-run (see "Admin re-run")

Environment actions performed / things to know next time

These are the missing pieces found while preparing the run. Each one is either already fixed (✔) or still needs you (➜).

✔ Migration AddJobPublishedAtArchivedAt1782700000000 had not been run on the local DB. GET /public/jobs/explore answered 500 INTERNAL_ERROR (column archived_at missing). The start-up archive sweep had also failed. It is in BullMQ bull:job:failed with column "archived_at" of relation "jobs" does not exist. Fixed with cd backend && npm run migration:run (or npm run db:migrate from the root).
- ➜ After any branch switch that adds migrations, run npm run db:migrate before starting the backend.
- ➜ Restart the backend once, so that the start-up sweep runs against the migrated schema. The hourly repeatable sweep is scheduled either way.
✔ The app on the emulator was an old build. It was installed on 2026-09-24 11:29, before app commit 29db707 (17:17), so it had no job level icon. It was rebuilt and reinstalled with adb install -r, which keeps the app data.
- ➜ A plain flutter build first failed because of stale generated code: di.config.dart had an ExploreBloc arity mismatch and _$JobBoostLevelModelFromJson was missing. The fix was dart run build_runner build --delete-conflicting-outputs (about 15 s; it did not bump file_picker). Run it after every checkout of an app branch that touches @injectable/json_serializable classes.
✔ app/.env has API_BASE_URL=http://localhost:3100/api, but only adb reverse tcp:3000 existed. adb reverse tcp:3100 tcp:3000 was added.
- ➜ Re-run it after every emulator restart. Alternatively, set .env to port 3000 and rebuild.
- adb reverse tcp:9000 (MinIO) is needed for the level icons (iconUrl = http://127.0.0.1:9000/...). It was already present.
➜ Claude in Chrome was not connected. Start the session with claude --chrome or run /chrome (with Chrome open) if you want the browser scenarios to run in your real Chrome.
➜ Time zone on this machine. The backend runs with Node TZ Asia/Bangkok (UTC+7) and writes timestamp without time zone columns in local time. Jobs created through the API therefore store published_at/created_at 7 h ahead of UTC. The archive sweep compares with Postgres now() (UTC), so on this box it archives those jobs about 7 h late. The API values round-trip correctly, and the containers run in UTC, so dev/prod are not affected. Consider TZ=UTC for the local backend (the same applies to items).
➜ The login in the app changed: the emulator app was a guest and is now logged in as the review-test worker +221222222222 ("Compte Revue").

Results

#	Repo	Requirement	Scenario	Method	Result	Evidence
1	backend	Public job payloads expose the level	Levelled and un-levelled jobs in the feed	http	PASS	Gold job → `{"id":"1000…003","name":"Gold","iconUrl":"http://127.0.0.1:9000/…png"}`; un-levelled → `null`; `meta={"nextCursor":null,"hasMore":false}`
2	backend	Public job payloads expose the level	Level without icon	http	PASS	`PATCH /admin/boost-levels/Gold {iconMediaId:null}` → 200; feed → `iconUrl: null` (icon restored after)
3	backend	Public job payloads expose the level	Detail, recruiter and saved payloads	http	PASS	feed, `GET /public/jobs/:id`, `GET /recruiter/jobs`, `GET /worker/jobs/saved` all return the identical Gold object
4	backend	Every boost level carries a listing lifetime	Existing levels after migration	http	PASS	all 5 levels carry an integer `lifetimeDays` (Platinum 91 was edited before this run; the 90 default applies on a fresh DB)
5	backend	Every boost level carries a listing lifetime	Level created without a lifetime	http	PASS	`POST {name}` → 201 `lifetimeDays: 90` (temp level deleted)
6	backend	Every boost level carries a listing lifetime	The same lifetime applies to a job and a listing	http	PASS	job side: Gold 30 d, job 31 d old → archived. The listing side is the DUJAP-1259/1260 sweep, not re-seeded here
7	backend	Jobs carry a publish date and an archived status	Existing jobs after the migration	http	PASS	migration run in this session: `UPDATE jobs SET published_at = created_at WHERE published_at IS NULL`, NOT NULL + default, `archived_at` added; statuses unchanged (8 published / 2 closed)
8	backend	Jobs carry a publish date and an archived status	New job	http	PASS	`POST /recruiter/jobs` → 201; DB `status=published`, `published_at=created_at`, `archived_at` null, no level
9	backend	Expired jobs are archived automatically	Job past its level's lifetime	http	PASS	sweep enqueued on BullMQ `job`; Gold=30, J 31 d → `archived`, `archived_at` set; `published_at`/level/category unchanged
10	backend	Expired jobs are archived automatically	Job still within its lifetime	http	PASS	M 29 d → `published`, `archived_at` null
11	backend	Expired jobs are archived automatically	Un-levelled job uses the system level's lifetime	http	PASS	None 90 d, N 91 d → `archived`
12	backend	Expired jobs are archived automatically	Level lifetime changed in the admin applies at the next sweep	http	PASS	J 40 d: Gold 60 → stays published; Gold 30 + sweep → archived
13	backend	Expired jobs are archived automatically	Closed jobs are not archived	http	PASS	closed Gold job 100 d old → stays `closed`, `archived_at` null
14	backend	Expired jobs are archived automatically	Sweep at startup and every hour	http	PASS	Redis `bull:job:repeat:*` → `job-archive-expired`, `every 3600000`, `attempts 3`; the start-up run exists (failed only because of the missing migration, see above)
15	backend	Expired jobs are archived automatically	Failing sweep is logged	http	SKIP	needs a DB outage. The failed start-up job shows the retry/failedReason path in Redis, but the backend console (log line) was not visible to this run. Covered by `job.processor.spec.ts`
16	backend	Archived jobs are hidden from the app	Archived job detail is not found	http	PASS	anonymous and worker → `404 ENTITY_NOT_FOUND`
17	backend	Archived jobs are hidden from the app	Recruiter's list without the archived job	http	PASS	P + C listed, A absent; `statusCounts={"published":1,"closed":1,"archived":0}`; `status=archived` → 200 `jobs: []`. Note: the response has no `total` field (see Spec notes)
18	backend	Archived jobs are hidden from the app	Worker's saved jobs without the archived job	http	PASS	saved → archived by admin → gone from `jobs`; `statusCounts.published` 2 → 1; other saved job still listed. Same `total` note
19	backend	Archived jobs are hidden from the app	Actions on an archived job are refused	http	PASS	save 404, chat `POST /threads/jobs` 404, recruiter update 403, close 404 — all `ENTITY_NOT_FOUND`/`HTTP_ERROR`; status still `archived`
20	backend	Archived jobs remain visible to admins	Archived job in the Employment statistics	http	PASS	row `status: archived`, `publishedAt` = job's publish date (DB value differs by +7 h only because of the TZ note above)
21	backend	Archived jobs remain visible to admins	Admin changes the level of an archived job	http	PASS	boost-level 200, category 200, still `archived`
22	backend	Employment statistics rows expose the job status	Live, closed and archived jobs	http	PASS	P `published`, C `closed`, A `archived`; rows keep `boostLevel`, `publishedAt`, `views`, `shares`
23	backend	Admin switches a job between Active and Archived	Admin archives a live job	http	PASS	200 `{status:"archived", publishedAt:T0, archivedAt:<now>}`; detail 404, absent from recruiter list, stats `archived`
24	backend	Admin switches a job between Active and Archived	Same status is a no-op	http	PASS	`{status:"published"}` on a published job → 200, unchanged
25	backend	Admin switches a job between Active and Archived	Value outside Active/Archived is rejected	http	PASS	`closed`, `active`, `{}`, extra `reason` → all `400 VALIDATION_ERROR`
26	backend	Admin switches a job between Active and Archived	Closed jobs cannot be switched	http	PASS	`422 JOB_NOT_PUBLISHED`, then `422 JOB_NOT_ARCHIVED`; stays closed
27	backend	Admin switches a job between Active and Archived	Unknown job or non-admin caller	http	PASS	unknown → `404 ENTITY_NOT_FOUND`; recruiter JWT → 403; no JWT → 401
28	backend	Reactivating an archived job resets its publish date	Reactivation restarts the lifetime	http	PASS	job archived with `publishedAt` 100 d ago → 200 `published`, `publishedAt≈now`, `archivedAt null`; `created_at` unchanged; next sweep keeps it published; detail 200
29	backend	Reactivating an archived job resets its publish date	Reactivated job is archived again only after a full lifetime	http	PASS	`published_at` shifted in DB: 29 d → published, 31 d → archived
30	backend	Feed ordered by boost level first	Levelled jobs first, None last	http	PASS	`[C, D, A, B]`
31	backend	Feed ordered by boost level first	Coordinates order by day then distance inside a level	http	PASS	`[C, P2, P1, P3, N]`
32	backend	Feed ordered by boost level first	Radius keeps the level-first order	http	PASS	`radiusKm=5` → `[P2, P3, N]` (6.7 km excluded); `radiusKm=10` → `[C, P2, P1, P3, N]`
33	backend	Feed ordered by boost level first	Admin reorders the catalogue	http	PASS	`PUT /admin/boost-levels/order` Gold above Diamond → `[D, A, C, B]`; order restored
34	backend	Explicit nearest-first job sort	Nearest first, level breaks ties	http	PASS	`[P2, G3, N2, G1, P1, G2]`
35	backend	Explicit nearest-first job sort	Distance sort without coordinates is ignored	http	PASS	200, default level → newest order
36	backend	Archived jobs are excluded from the public job feed	Archived job disappears from the feed	http	PASS	archived jobs absent; `total` = visible count
37	backend	Distance radius filter	Jobs within the radius are returned, sorted by distance	http	PASS	level-first by default; with `sortByDistance=true` → 0 m jobs, then 6.7 km
38	backend	Distance radius filter	Jobs beyond the radius are excluded from paging and counts	http	PASS	`radiusKm=5` over the 3/12/25 km set: 5 jobs over 3 pages, `total` 5 on each
39	backend	Distance radius filter	Radius without coordinates is ignored	http	PASS	200, unfiltered (10 jobs)
40	backend	Distance radius filter	Any positive radius is accepted	http	PASS	1 / 2.5 / 30 / 150 accepted (0 / 0 / 10 / 10 jobs)
41	backend	Distance radius filter	Non-positive or non-numeric radius is rejected	http	PASS	`0`, `-5`, `abc` → `400 VALIDATION_ERROR` naming `radiusKm`
42	backend	The job feed's total count may be briefly stale	Paging does not change the total	http	PASS	9 / 9
43	backend	The job feed's total count may be briefly stale	A different filter gets its own count	http	PASS	9 vs 10
44	backend	The job feed's total count may be briefly stale	A newly published job appears within the TTL	http	PASS	new job listed immediately
45	backend	Paging returns every job exactly once	Page boundary inside a level and across levels	http	PASS	`limit=2`: 5 pages, 9 distinct jobs in level → newest order, last `nextCursor: null`, `total` 9 on each page
46	backend	Paging returns every job exactly once	Page boundary with coordinates	http	PASS	9 jobs in level → day → distance → newest order, un-located last within level/day
47	backend	Paging returns every job exactly once	Page boundary under the explicit distance sort	http	PASS	0 m → 6.7 km → no address, level then id inside each
48	backend	Paging returns every job exactly once	Paging with a radius	http	PASS	`radiusKm=30`, `limit=5`: 10 distinct jobs
49	backend	Paging returns every job exactly once	A cursor from another ordering restarts at the first page	http	PASS	bare id, pre-level distance cursor, coords cursor without coords, distance cursor without the flag, `not-a-cursor` → all 200 + page 1
50	backend	Paging returns every job exactly once	Farther but newer jobs are not skipped	http	PASS	3 km ×5 → 12 km ×4 → 25 km, `hasMore:false`, `total` 10
51	backend	Paging returns every job exactly once	Jobs whose recruiter has no address come last	http	PASS	both orderings place them as specified
52	backend	Paging returns every job exactly once	Newest-first paging without coordinates is unchanged	http	PASS	newest-first within a level; `nextCursor` is opaque base64
53	backend	Marketplace statistics rows expose the listing status	Job rows	http	PASS	every job row status ∈ {published, closed, archived}
54	backend	Marketplace statistics rows expose the listing status	Live, sold and archived listings	http	PASS	item rows status ∈ {published, sold, archived}
55	admin	Status column in the Employment statistics tab	Column position and values	browser	PASS	EN `MEDIA \| LEVEL \| STATUS \| PUBLISHED \| CATEGORY \| AUTHOR \| VIEWS \| SHARES`, Active / Archived selects + text "Closed"; FR `STATUT`, Actif / Archivé / Fermée
56	admin	Switching a job's status asks for confirmation	Archive a live job	browser	PASS	dialog "Archive this job post?"; 1 `PATCH /admin/jobs/…602/status {"status":"archived"}`; Archived, Published cell unchanged, toast "Status updated"; still Archived after reload
57	admin	Switching a job's status asks for confirmation	Reactivate an archived job	browser	PASS	row published Jun 17 (100 d) → 1 PATCH `{"status":"published"}` → Active, Published "Sep 25, 2026, 07:20"
58	admin	Switching a job's status asks for confirmation	Cancelled or failed switch	browser	PASS	cancel: no request, no toast, select back to Active. Fail: the response was forced to `422 JOB_NOT_PUBLISHED` (CDP Fetch interception) → error toast with the API message, select reverted
59	admin	Switching a job's status asks for confirmation	Closed job has no switch	browser	PASS	the closed row renders text only; every select offers exactly Active/Archived
60	admin	Status column in the Marketplace statistics tab	Column position and values	browser	PASS	EN `… LEVEL \| STATUS \| PUBLISHED \| CATEGORY \| PRICE …`; FR Statut / Actif / Archivé (no sold listing in the local data, so "Vendu" not shown)
61	admin	Status column in the Marketplace statistics tab	Employment tab unchanged	browser	PASS	Status column present, no "Sold"
62	admin	Create and edit a level	Create a level with an icon	browser	PASS	lifetime pre-filled 90, PNG preview shown, "Silver" created with icon, 90 d, just above None (deleted after)
63	admin	Create and edit a level	Change the icon of an existing level	browser	PASS	Gold icon replaced; new URL shown after reload (PNG used instead of JPEG; original icon restored)
64	admin	Create and edit a level	Change the lifetime of a level	browser	PASS	`PATCH {"lifetimeDays":10000}`; Gold row shows 10000 after reload (reset to 90)
65	admin	Create and edit a level	Invalid lifetime is rejected in the form	browser	PASS (re-run)	first run FAIL (empty / `abc` disabled Save silently); after `77a3afc`: `0`, `-3`, `2.5`, `abc`, `""`, `10001` → no request, modal open, "Lifetime must be a whole number between 1 and 10,000 days"
66	admin	Create and edit a level	Duplicate name	browser	PASS	"A level with this name already exists", modal stays open
67	admin	Create and edit a level	Editing the system level	browser	PASS	Name/Lifetime editable, no file input + "The system level has no icon.", hint "Applies to listings and job posts without a level."
68	admin	Create and edit a level	Page wording covers jobs	browser	PASS	EN "…a listing or job post can have…"; FR hub "…annonces de la marketplace et des offres d’emploi…"
69	app	Level icon on the job card thumbnail	Gold job in the worker explore	manual (adb)	PASS	Explore + search: Platinum/Gold icons drawn over the top-left of the thumbnail (screens app-04/05/06)
70	app	Level icon on the job card thumbnail	Job without a level or without an icon	manual (adb)	PASS	a job with `boostLevel` whose `iconUrl` is null (temp level) and an un-levelled job show no icon, and the card size matches (app-07/08); the category page "Plombier" is also clean (app-09)
71	app	Level icon on the job card thumbnail	Recruiter's own published Gold job	manual (adb)	PASS	recruiter home: Gold icon top-left + "Active" badge top-right; the un-levelled job only has the badge (app-17). Saved jobs: Gold icons, archived saved jobs hidden, "Actifs (2)" (app-15)
72	app	Level icon on the job card thumbnail	Payload without the field	unit test	PASS	`flutter test job_item_model_boost_level_test.dart job_card_boost_level_test.dart` → 13/13 passed
73	app	Job lists show the server order	The list mirrors the response order	manual (adb)	PASS	the search "OPSXT-DIST" list equals the API nearest order `[P2, P1, G(0 m), G1, G2, NoIcon]` 6/6; the explore head matches the API with the emulator GPS 14.69,-17.44. Load-more append not checked screen by screen

Admin re-run (2026-09-25 07:40, admin `77a3afc`)

OpenSpec update: tasks 8.1–8.4, proposal admin bullets, admin/boost-levels (lifetime submit stays enabled; MODIFIED "Delete a level" wording covers job posts), backend/job-lifecycle (no total on recruiter/saved lists), backend/job-search (feed position uses createdAt, also after reactivation). Main specs under openspec/specs/ updated identically (sync). openspec validate: change valid, 28/28 specs pass.

Admin fix 77a3afc fix(settings): lifetime message on empty input and job-aware delete warning (DUJAP-1320): Save stays enabled so empty / non-numeric lifetime shows the localised message; errors.linkedItems EN/FR mention job posts. npx eslint (touched) clean, npx tsc --noEmit clean.
All 14 admin scenarios re-run in headless Chrome (CDP): 14/14 PASS (#55–#68, incl. #65 now PASS).
Extra check for the new delete wording: a temp level assigned only to job …602 → Delete is blocked with "This level is assigned to 1 listing(s) or job post(s) and cannot be deleted. Move them to another level first." / FR "… 1 annonce(s) ou offre(s) d’emploi …", no DELETE request sent (screens 10-delete-blocked-{en,fr}). Temp level deleted.
Confirmed afterwards in your real Chrome through Claude in Chrome, once you had logged in yourself:
- Levels → Delete on a level assigned only to one job → "Cannot delete this level — This level is assigned to 1 listing(s) or job post(s) and cannot be deleted. Move them to another level first."
- Edit Gold with an empty Lifetime → Save → "Lifetime must be a whole number between 1 and 10000 days", modal stays open (cancelled, nothing saved).
- /statistics/employment shows Level | Status (Active / Archived / Closed) | Published.
- The temp level was deleted afterwards.

Failures (first run)

#65 admin — Invalid lifetime is rejected in the form

Expected: for empty or "abc", "no request is sent, the modal stays open and a localised message explains that the lifetime must be a whole number between 1 and 10 000".
Observed: no request is sent and the modal stays open, but no message appears. canSubmit (admin/src/app/(admin)/settings/boost-levels/page.tsx:445) disables Save while the field is empty. A number input holding abc reports "", so the same thing happens.
This behaviour comes from DUJAP-1259 (1faf748), not from this change. This change only reworded the hints.
Fixed in 77a3afc (see Admin re-run).

Spec notes / open questions (not failures)

Icon position — decided: keep top-left (confirmed by the user 2026-09-25). Original note: Icon position (question raised during the run): the job card icon is top-left, while listings are top-right. This is intended by this change. See proposal.md → Assumptions ("The job icon goes top-left, not top-right as on listings") and spec app/job-boost-level. The reason is that the top-right of the job thumbnail holds the recruiter "Active/Published" badge and the Closed ribbon. On worker screens (explore/search/saved/category) that corner is empty, because the bookmark sits under the thumbnail. If the product wants top-right as on listings, the options are:
- a) top-right everywhere, and move the recruiter badge/ribbon;
- b) top-right on worker screens, top-left on recruiter screens.
Either one needs /opsx:update + /opsx:apply.
✔ Resolved in the spec (no code change). backend/job-lifecycle → "Recruiter's list …" and "Worker's saved jobs …" mention total, but GET /recruiter/jobs and GET /worker/jobs/saved return only data.jobs, data.statusCounts and meta.{nextCursor,hasMore}. The service computes total, but the envelope does not expose it. This behaviour existed before this change. The spec wording should drop total or the API should add it.
✔ Resolved in the spec (no code change). The "nearest" ordering buckets by created_at day (PUBLISH_DAY_EXPRESSION), not published_at. A reactivated job keeps its old day inside its level when coordinates are sent. This matches the marketplace feed, but the spec says "publish day".
✔ Fixed in 77a3afc. The admin text settings.boostLevels.errors.linkedItems still says "…assigned to {count} listing(s)…", although the count now includes jobs.
During the run, jobs …508 (OPSXT-FAR a3) and one OPSXT-FAR a12 job got Diamond/Bronze at about 07:23 from outside the test scripts. Maybe you were testing in parallel. They were left as they are.

Test data

All of this is on the local DB and was left in place so you can look at it in the admin/app. The catalogue itself was restored: Gold lifetime 90, Gold icon, level order, and the temporary levels Silver / [opsx-test] 1320p / OpsxNoIcon deleted.

Recruiters 91000000000000xxxx named OPSXT-* with addresses 93000000000000xxxx, and jobs 92000000000000xxxx (40): sets LVL / COORD / DIST / PAGE / FAR / LIFE.
Jobs …701 (Gold) and …702 owned by the review-test worker "Compte Revue" (377310282013347840).
4–5 jobs created through the API by the review-test recruiter +221548548548 (user 378724935595593728), some archived or closed.
The worker saved jobs: rows in saved_jobs for 377310282013347840.

Cleanup:

DELETE FROM saved_jobs WHERE job_id LIKE '92000000000000%' OR job_id IN (SELECT id FROM jobs WHERE recruiter_id='378724935595593728');
DELETE FROM jobs WHERE id LIKE '92000000000000%' OR recruiter_id='378724935595593728';
UPDATE users SET address_id=NULL WHERE id LIKE '91000000000000%';
DELETE FROM users WHERE id LIKE '91000000000000%';
DELETE FROM addresses WHERE id LIKE '93000000000000%';

Run it with docker exec -i dev-postgres psql -U postgres -d japp.

Unchecked tasks in tasks.md

none (32/32)