-
Notifications
You must be signed in to change notification settings - Fork 5
Add a realistic Gutenberg blocks fixture for VisualBrief regression tests #24
Copy link
Copy link
Open
Labels
area: wordpress-gutenbergWordPress REST API, Gutenberg input, and block placementWordPress REST API, Gutenberg input, and block placementcontribution: no-claimIndependent first contribution; open a PR without claimingIndependent first contribution; open a PR without claimingexamplesExample profiles and articlesExample profiles and articlesgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is needed
Description
Activity
Metadata
Metadata
Assignees
Labels
area: wordpress-gutenbergWordPress REST API, Gutenberg input, and block placementWordPress REST API, Gutenberg input, and block placementcontribution: no-claimIndependent first contribution; open a PR without claimingIndependent first contribution; open a PR without claimingexamplesExample profiles and articlesExample profiles and articlesgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is needed
Why
The Gutenberg input is a real editor surface. Its parser needs a representative fixture, not only a minimal string embedded in a test.
Scope
Add one fixture under
tests/fixtures/containing ordinary Gutenberg comments, paragraphs, two H2 headings, inline formatting, and a list or quote block. Add a focused test provingVisualBrief.from_html()extracts the title, H2 targets, and section excerpts.Reference
tests/unit/test_wordpress_input.pysrc/pictovap/core/primitives.py(VisualBrief.from_html)Done when
pytest tests/unit/test_wordpress_input.py -q --no-covpasses.No claim is needed. Fork and open a PR directly.