Commit Graph
3 Commits
Author SHA1 Message Date
DongHyeonka ed49973652 test(upload): resumable upload spec이 페이지 origin을 설정의 baseURL에서 읽는다
문제
tests/browser-capabilities/resumable-upload.spec.ts가 CORS 응답의 origin을
"http://127.0.0.1:4174"로 따로 적는다. playwright.capabilities.config.ts의
baseURL과 지금은 같아서 동작하지만, 설정의 포트를 바꾸면 이 spec만 CORS로
조용히 깨진다.

고른 방법
- 설정 파일을 import해 use.baseURL의 origin을 쓴다. test.info()는 route
  처리기 안에서 부를 수 있는지가 Playwright 내부 맥락에 달려 고르지 않았다.

검증
- check:types(tsconfig.test.json) 통과, eslint 통과. 브라우저 실행 결과는
  이 커밋 메시지에 적지 않았다(공유 잠금 대기).

Refs: docs/reviews/2026-11-03-maturity-review/11-tests-browser-release-scale.md (2절 FOLLOW-UP resumable-upload 포트)
2026-11-04 21:24:06 +09:00
DongHyeonkaandClaude Opus 5 7485cd86e4 fix: let the browser, visual and performance evidence describe the product again
Four browser-capability specs never reached the code they were named for. The
`PRESIGNED_TRANSFER_V1` envelope gained a top-level `protocol` field, and the
fixtures kept answering without it, so every capability was refused before any
object request was made: the download and part-upload success paths were
asserting against an empty transcript rather than exercising a real GET or PUT.
The fixtures now speak the protocol they claim to, and the part-deletion
expectation carries the physical effect the adapter reports.

A refused capability document also answered `recovery: NONE`, telling the
caller there was nothing to be done. The design record fixes this class of
refusal as re-issuable and the vault already answers `REISSUE_CAPABILITY` for
it, so the HTTP decoder disagreed with both. It now agrees.

Lab performance produced no evidence at all. Playwright matches accessible
names by substring, so the navigation entry "플랫폼 구성" also matched the home
page's "플랫폼 구성 보기" call to action; the locator resolved to two links and
the run died on a strict-mode violation before the first measurement. With an
exact match the metrics are collected, and they show the named-interaction
budget is missed on this machine — a real signal that was previously invisible.

The platform overview baseline was captured before the reference routes moved
from `integration-defined` to `session-required` and was never regenerated, so
the only visual gate that could catch a regression on that page was failing for
its own staleness. Regenerated after confirming the diff is exactly that label.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-15 16:49:48 +09:00
donghyeon-ka 6c52cdb916 feat: 기능 추가 과정중 2026-07-30 15:58:20 +09:00