https://bugzilla.wikimedia.org/show_bug.cgi?id=45440
Web browser: ---
Bug ID: 45440
Summary: Add testing setup for Parsoid's extension handling
Product: Parsoid
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: Unprioritized
Component: JS/tests
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected],
[email protected]
Classification: Unclassified
Mobile Platform: ---
Parsoid uses the PHP parser to expand extensions and incorporate them into the
token stream. However, there are no tests for this functionality since
parserTests does not use the API.
So, we need another way of testing this functionality -- possibly something
that might require a wiki with installed extensions. This might be a spinoff
of parsertests that either stubs the wiki/api (ideal since it doesn't rely on
Net access) or calls an existing wiki.
What we are interested here is not so much on extension output itself but that
Parsoid does handle extension tags and incorporate that into the token stream
for it to RT correctly. So, stubbed API that returns dummy content is not
necessarily a bad thing. Something that is achievable either by adding
additional options to the parserTests.js script or by writing a new script that
uses/inherits from it.
This testing framework would have to be accompanied with an initial set of
tests for one or two extensions.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are watching all bug changes.
_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
