RDBTC-221 Migrate Technical Guides: Writing unit tests with RavenDB Python Test Driver

[Netzach-Nyss]

Issue link

RDBTC-221 Migrate technical guides and how-tos from ravend.net/articles to docs.ravendb.net/guides

Additional description

Migrating article Writing unit tests with RavenDB Python Test Driver to guides.

Content Quality Score: 82/100 (up from 78)

E-E-A-T Breakdown

Factor	Score	Key Signals
Experience	16/20	Screenshot is a strong first-hand signal; dotnet gotcha buried in FAQ instead of surfaced at install step
Expertise	20/25	Accurate throughout; orphan H4 in Step 4 not removed; H5 heading skip in FAQ
Authoritativeness	18/25	Named author, PyPI links, see_also cross-links; no author bio/role
Trustworthiness	26/30	Specific and honest; body links hard-code /7.2/ prefix (matches site convention per memory)

AI Citation Readiness: 68/100

---

Remaining Issues (priority order)

#	Issue	Impact
1	H5 heading skip in FAQ — Q/A use #####, skipping H4 entirely from surrounding H3 context; should be bold paragraph labels or H4	Medium
2	Dotnet prerequisite not surfaced at Step 1 — failure only discoverable via FAQ; a single sentence callout at install step would help beginners	Moderate
3	No teardown/disposal note — guide shows setUp but never explains whether in-memory instances clean up automatically between tests	Moderate
4	Introduction repeats the same argument twice — paragraphs 2 and 3 both say "mocks bad, real DB good" with no new information	Low

Type of change

• Content - docs
• Content - cloud
• Content - guides
• Content - start pages/other
• New docs feature (consider updating /templates or readme)
• Bug fix
• Optimization
• Other

Changes in docs URLs

• No changes in docs URLs
• Articles are restructured, URLs will change, mapping is required (update /scripts/redirects.json file, set Documents Moved PR label)

Changes in UX/UI

• No changes in UX/UI
• Changes in UX/UI (include screenshots and description)