This directory contains sets of fixture files that are used to test the parsing and serialization logic.

Each test is made up of four fixture files:

1. fixture-name.html: The initial post content.
2. fixture-name.parsed.json: The expected output of the PEG parser for this content (checked against the actual output of both the JS and PHP versions of the parser).
3. fixture-name.json: The expected representation of the block(s) inside the post content, along with their attributes and any nested content. The contents of this file are compared against the actual block object(s).
4. fixture-name.serialized.html: The expected result of calling serialize on the parsed block object(s). The contents of this file are compared against the actual re-serialized post content. This final step simulates opening and re-saving a post.

Every block is required to have at least one such set of fixture files to test the parsing and serialization of that block. These fixtures must be named like core__blockname{__*,}.{html,json,serialized.html}. For example, for the core/image block, the following four fixture files must exist:

1. core__image.html (or core__image__specific-test-name.html). Must contain a <!-- wp:core/image --> block.
2. core__image.parsed.json (or core__image__specific-test-name.parsed.json).
3. core__image.json (or core__image__specific-test-name.json).
4. core__image.serialized.html (or core__image__specific-test-name.serialized.html).

Ideally all important attributes and features of the block should be tested this way. New contributions in the form of additional test cases are always welcome - this is a great way for us to identify bugs and prevent them from recurring in the future.

When adding a new test, it's only necessary to create file (1) above, then there is a command you can run to generate (2) through (4):

GENERATE_MISSING_FIXTURES=y npm run test-unit test/integration/full-content/full-content.spec.js

However, when using this command, please be sure to manually verify that the contents of the .json and .serialized.html files are as expected.

See the full-content.spec.js test file for the code that runs these tests.