[Experimental]: Documentation Testing with Playwright #923
+409
−2
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.
Description
This PR introduces a comprehensive testing framework with Playwright for our API documentation, allowing us to automatically verify that all API documentation pages load correctly across our product ecosystem.
Motivation and Context
How Has This Been Tested?
Note: Ensure local environment is running prior to the following steps
Step 1: Generate MDX Paths
First, run the collection script to scan all MDX files and generate the necessary paths:
node scripts/collect-mdx-paths.js
This will:
tests/products/
directoryStep 2: Run Playwright Tests
Once the test files are generated, run the Playwright tests:
yarn playwright test
or
yarn playwright test --ui
(provides an intuitive testing experience)Screenshots (if appropriate)
Playwright UI Testing Environment
Types of changes
Checklist