test(portal-clis): isolate valid flag controls from live services (#581)

* test(portal-clis): isolate valid flag controls from live services

The LinkedIn and Freehire positive controls spawned live search CLIs and only checked for the absence of BAD_ARG, so attempted portal requests still left a green suite. Use loopback responses and assert successful output plus the constructed freshness, pagination and result-limit contract.

LinkedIn cards are verbatim excerpts from portapulito's actual captured response in PR #153; fixture provenance and original hashes are retained. Four Danish validation suites already stop at required-argument guards and need no change. This isolates these controls rather than claiming a whole-CI egress policy.

* docs(changelog): record fix for #581
This commit is contained in:
Rudy Mizrahi Celekli authored and GitHub committed 2026-10-18 06:57:43 +02:00
1 parent 23876bfa95
commit 2017521d2e
6 files changed
+104 -16

No files matched your search

+2
View File
@@ -324,6 +324,8 @@ per-file diff commands.
unchanged, an absent one stays `""`. The JSON-LD test that pinned the raw `<p>...</p>` now
expects the text, plus two new cases; the HTML case fails on master.
- **Valid portal flag tests stay offline** (#581) - success controls use local fixtures instead of depending on live job portals or their credentials.
- **`job_key.py` no longer gives two postings one key when a title or company is partly
non-Latin** (`tools/job_key.py`, `tests/test_job_key.py`) - the hash fallbacks from #487
and #502 fired only when the slug was completely empty, so a mixed-script name kept its