Repository navigation
docs(testing): make performance and UX checks scannable - #126
Merged
Merged
Conversation
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.
Make the Testing page's Performance and UX sections easier to scan, matching the labeled-list style used for Security.
Performance groups task speed, typical/slower runs, archive size/first runs, memory and downloads/loading. UX groups feature use, guides/examples, keyboard/mobile/accessibility and languages. Preserve the p50/p95 definitions, hardware/workload limits, manual-review boundaries, existing links and headings. All English, Russian and Spanish prose reviewed against the documentation guides; review recorded in docs/reviews/2026-10-10-testing.md. No runtime or release-contract changes.
Validation: lint (including browser-test structure), typecheck, 272 unit tests, refreshed offline command contracts, strict documentation checks and localization passed. All seven local smoke cases and nine targeted checks passed (EN/RU/ES desktop/mobile list rendering and Markdown labels); full CI passed export/link/SEO and broader browser checks, along with standards, secret scanning, all four Windows installs and the isolated query-playground job.