Repository navigation
docs: explain functionality performance security and UX testing - #114
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.
Add a Testing page under Technical details so technical readers can distinguish correctness, ranking quality, resource cost, security evidence and usability, and find the right reproducible check.
The English, Russian and Spanish pages define candidates/scoring/reranking, Success/Recall/Precision@k, MRR/nDCG, p50/p95 and memory/download measurements. They explain repository ownership, implementation versus published-binary checks, synthetic versus authorized live data, local smoke versus full CI, manual review and the limits of coverage/scanners/development fixtures. A 43.8% Success@10 example explicitly means at least one labelled relevant result for that share of queries. No runtime capabilities change.
Navigation includes a decorative testing icon and contextual inbound links from search architecture. All changed locale prose, openings, examples and ownership paths were reviewed; evidence is recorded in docs/reviews/2026-10-10-testing.md. The new standalone released-package check is merged in cli-testing PR12, verified against both published binaries offline.
Validation: lint, typecheck, 257 unit tests, refreshed release command contracts, strict docs checks and source-matched localization passed. Targeted rendered-page checks passed for all three locales, including desktop navigation, mobile width and Markdown exports. The local smoke suite passed all ten cases; the new page also passed keyboard focus, mobile menu/Escape and decorative icon checks in all three locales. Full CI export/link/SEO/browser checks, all four Windows installation jobs and the isolated search-playground job passed before merge.