Conversation
Convert the monolithic extended_features_doc.rst into a thin landing page that points to ten cluster docs: - architecture - backends - reports - observability - orchestration - quality_security - browser_internals - data_auth_api - integrations - tooling - cookbook Same content, restructured for navigation; sphinx-build -W passes in a selenium-less venv that mirrors the RTD environment.
Up to standards ✅🟢 Issues
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The extended_features doc had grown to 670 lines with 47 sections in one
file, all sharing a single page. This PR splits it into ten cluster docs
(Eng + Zh symmetric) and turns
extended_features_doc.rstinto a thinlanding page with a toctree.
New folders under both
docs/source/Eng/doc/anddocs/source/Zh/doc/:architecture— System overview · Action lifecyclebackends— Selenium · Playwright · Cloud Grid · Appium (incl. mobile gestures)reports— Reports · Reporting & CI · CI reproducibility & long-term observabilityobservability— Observability · tooling · triage / productionorchestration— Test orchestration · DX · fan-out · CLI polishquality_security— Q&S · probes · PII / visual review · form auto-fill / a11y diffbrowser_internals— internals · locale · storybook / shadow DOM · CDP tap / cross-browser / state diffdata_auth_api— Test data (+ determinism) · auth/API/database · contract testingintegrations— Recorder · CI/integrations · AI assistance · MCP · Action JSON LSPtooling— reliability · browser pool/BiDi · HAR replay · impact · bootstrapper · sel→pw · formatter · POM codegen · WR_sleepcookbook— examples · test tiers · thematic façadeContent is verbatim copy of the corresponding sections from the old file
— no rewriting, just regrouping. The old
extended_features_doc.rstkeeps the introduction and now consists of a toctree pointing at the new
cluster docs, so the existing RTD URL continues to resolve.
Verification
sphinx-build -W --keep-goingsucceeds with zero warnings in aclean venv that mirrors the RTD environment (no project deps installed,
only sphinx + sphinx-rtd-theme + sphinxcontrib-mermaid).
Test plan