* feat(test): add test.describe.fail and the fail option on describe A test now reads fail from its groups as well as itself. Any truthy layer marks it, the innermost reason wins, and fail: false does not unmark. Refused on, inside, or around a serial group. Part of #1855. * test(collect): check an inner group's fail reason wins over an outer one * fix(test): type describe without a cast and point the test.fail error at describe.fail The collection error for test.fail(condition) outside a body now names describe.fail and the describe option, since a migrating Playwright user hits it first. The Playwright migrate row gains the conditional form, and the ja/zh rows take cubic's translations. * fix(test): validate describe.fail options before adding the mark describe.fail copied its options with a spread before validation, so an array or a non-enumerable bad key passed where describe() rejects it. The caller's options are now validated first, then again with fail: true for the serial rules. The fail docs now say true or any string marks, since a blank string marks too. * docs(test): say fail is refused around a serial group too * refactor(test): validate describe options in one pass describe.fail no longer validates twice: the serial check takes the mark into account, and registerDescribe takes api and markFail without defaults.
Japanese docs
The Japanese translation of the e2e docs. The site serves each page here at
/docs/ja/<path>; a page without a translation shows the English page with a
notice. English stays the source of truth.
This translation is best effort. English changes don't wait for it, so a page
here can lag behind its English page until someone who reads Japanese updates
it. pnpm docs:check lists every page and label that is behind as a warning.
Layout
docs/ja/<path>.mdxtranslatesdocs/<path>.mdx: same path, same file name.navigation.jsonholds the Japanese labels for every tab and group indocs/docs.json(tabs,groups), keyed by the English label. The navigation order and pages come fromdocs/docs.json; there is no second navigation to keep in sync.- Images, snippets, and
docs/examples/are shared with the English pages.
Updating a translation
- Translate the text: prose, frontmatter
title,description, andsidebarTitle, and the human-readable attributes of components (titleon<Card>,<Accordion>,<Tab>,<Step>, the text of<Note>,<Warning>,<Tip>). - Keep the outline: the same headings at the same levels in the same order,
the same
<Tab>and<Accordion>elements in the same order, and everyid="...". The site gives a translated heading the English heading's id by position, so links and the language switcher land on the same section.pnpm docs:check(scripts/check-docs-translations.ts) warns when the outline drifts. - Leave code alone: code blocks, inline code, fence titles, URLs, link
targets and their
#anchorsstay exactly as on the English page.pnpm docs:checkwarns when a code block differs. Links stay docs-root relative (/quickstart#install); the site points them at the Japanese pages. - Snippet imports sit one folder deeper:
./snippets/x.jsxbecomes../snippets/x.jsx.
When you update a page, bring its outline, code, and labels in line with the English page, including changes English made since. An English placeholder heading is fine until someone translates it; deleting the translated page falls back to English. When an English page moves or is deleted, its translation moves or goes with it in the same change.
Style
- Polite form (です・ます調), plain technical Japanese.
- Wrap lines anywhere: the site drops a line break between two Japanese characters, so it never shows as a space.
- A half-width space between Japanese and Latin words or inline code:
e2e の設定,`test()` を呼び出します. - Keep product, package, and API names in English: e2e, Playwright,
@e2e-dev/web, MCP, CI, GitHub Actions. - Katakana loanwords keep the long vowel mark (サーバー, ユーザー, プロバイダー), except ブラウザ.
| English | Japanese |
|---|---|
| test, test suite | テスト, テストスイート |
| agent, agentic | エージェント, エージェント型 |
| deterministic | 決定論的 |
| engine | エンジン |
| runner | ランナー |
| fixture | フィクスチャ |
| locator | ロケーター |
| step | ステップ |
| goal | ゴール |
| entry | エントリー |
| assertion | アサーション |
| target | ターゲット |
| replay cache | リプレイキャッシュ |
| executor, custom executor | エグゼキューター, カスタムエグゼキューター |
| tool, project tool | ツール, プロジェクトツール |
| custom tool (an executor's own) | カスタムツール |
| custom (adjective in a sentence) | 独自の(独自の cache.store)。カスタム〜は上の名詞の用語だけ |
| provider | プロバイダー |
| hosted browser | ホスト型ブラウザ |
| device | デバイス |
| worker | ワーカー |
| retry | リトライ |
| report, reporter | レポート, レポーター |
| secret | シークレット |
| session | セッション |
| judge | ジャッジ |
| decision model | デシジョンモデル |
| coding agent | コーディングエージェント |
| skill | スキル |
| bug bash | バグバッシュ |
| visual testing | ビジュアルテスト |
| self-healing | セルフヒーリング |
| pull request | プルリクエスト |
| config, configuration | 設定 |
| screenshot | スクリーンショット |
| semantic tree | セマンティックツリー |
| redact, redaction | 秘匿 |
| mask, masking (pixels) | マスキング |
| secure field | 機密フィールド |
| location (current URL or screen) | ロケーション |
| budget | 予算 |
| planned, not planned | 実装予定, 実装予定なし |