|
All checks were successful
CI Trade-In / changes (pull_request) Successful in 17s
CI / changes (pull_request) Successful in 16s
CI Trade-In / frontend-checks (pull_request) Has been skipped
CI / backend-tests (pull_request) Has been skipped
CI / frontend-tests (pull_request) Has been skipped
CI / openapi-codegen-check (pull_request) Has been skipped
CI Trade-In / backend-tests (pull_request) Successful in 1m50s
Group E3 recon confirmed `scraper_kit.providers.yandex.valuation` is already a strangler-copy (#2133) and already used via admin.py's debug route (#2305, Group A) with the established config=RealScraperConfig()/delay_provider= get_scraper_delay convention. estimator.py (the real caller, #2337's scope) still imports the legacy module directly with no arguments -- not touched here. Adds regression coverage for the two confirmed footguns before #2337 switches that call site: - mandatory `config: ScraperConfig` raises TypeError when omitted (same discipline as the cian_valuation footgun, #2335) - optional `delay_provider` silently falls back to hardcoded 5.0s when not wired, discarding admin-tuned anti-ban throttling (scraper_settings. get_scraper_delay) Also extends the existing `.parse()` golden-parity test (test_scraper_kit_ yandex_golden_parity.py, SimpleNamespace config) with an assert_parity-based proof over the REAL production construction path (RealScraperConfig() + get_scraper_delay), plus a harness-catches-divergence sanity check. No production code changed -- app/services/scrapers/yandex_valuation.py and scraper_kit/providers/yandex/valuation.py are both pre-existing. |
||
|---|---|---|
| .. | ||
| app | ||
| data/sql | ||
| scripts | ||
| tests | ||
| .dockerignore | ||
| Dockerfile | ||
| pyproject.toml | ||