Parsoid/Parser Unification/Confidence Framework/Reports
For all wikis where Parsoid readviews is being rolled out, some common considerations apply:
- Extension support: All critical extensions are known to be functional on the wiki.
- Testing considerations: Visual diff testing only identifies rendering issues and may not uncover dynamic behavior like javascript functionality - in some scenarios, we may discover regressions post-deploy and aim to quickly fix them as we discover them or rollback Parsoid if appropriate.
- Rollback Strategy: A full rollback is planned if any significant issues are observed post-deployment.
Deployment Readiness for Wiktionary
editFor more information about the VisualDiff tests, please access the following page: Parsoid/Parser Unification/Confidence Framework/Reports/Wiktionary.
Deployment Readiness for Wikivoyages
edit- Functionality Concerns:
- Kartographer: The wikivoyage projects use Kartographer heavily, so we are paying close attention to interactions Parsoid may have with Kartographer
- Localization/RTL issues: For non-English wikis, localization of messages will be a key issue (localization of messages from Kartographer in particular). hewikivoyage was our first Right-To-Left reading order wiki.
- Vertical whitespace issues: A relatively large number of pages display minor vertical whitespace issues. This is primarily due to newline combining cross template boundaries which introduce paragraphs with <br>s in them which Parsoid will not introduce. In most cases, the Parsoid output is actually better than the output of the legacy parser, and in other cases, it might be better to have had the extra whitespace. There is no "always-correct" solution here and we believe Parsoid's output is reasonable. This issue is tracked in T355099.
For more information about the VisualDiff tests, please access the following page: Parsoid/Parser Unification/Confidence Framework/Reports/Wikivoyage.
Deployment Readiness for Wikitech DiscussionTools
editVisual Difference Score Assessment
editCurrent Status:
edit- Pixel Perfect Rendering: Achieved for 95.7% of approximately 6250 talk pages tested.
- Minor Issues: 99.9% of pages show pixel perfect or only minor vertical whitespace shifts.
- Known Differences: 0.1% of pages have known differences (not planned for fixing).
- Critical Differences: None.
Considerations for Deployment:
edit- Reliability: The high percentage of pixel-perfect rendering (98.55%) is a strong indicator of the system’s reliability.
- Pending Reassessment: None
- Blocker Evaluation: None
Extension and Functionality Support
editCritical Extensions:
edit- Assumption: Extensions critical for Wikitech DiscussionTools are presumed to be identified in the visual diff process.
Functionality Concerns:
edit- Login vs. Logout Issue: None
- Legacy Parser Compatibility: A strategy is needed to ensure that deployment of the new system does not disrupt the recording of metadata by the legacy parser.
Rollback Strategy
edit- Procedure: A full rollback is planned if any significant issues are observed post-deployment.
Main Concerns and Potential Delay
edit- Current Stance: As of now, there are no major concerns that would necessitate postponing the deployment.
- Dependent Factors: None.
Proposed Confidence Score for Deployment
edit- Score: Confidence in the rollout is extremely high.