From 2b9659cfcfde4b52764bf5889f497e28e583e1c4 Mon Sep 17 00:00:00 2001 From: James Nylen Date: Thu, 29 Jun 2017 20:55:52 +0200 Subject: [PATCH] Fixes to full-content tests readme --- blocks/test/fixtures/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/blocks/test/fixtures/README.md b/blocks/test/fixtures/README.md index 5321b7f4a037d..d6dec4e17163a 100644 --- a/blocks/test/fixtures/README.md +++ b/blocks/test/fixtures/README.md @@ -3,7 +3,7 @@ This directory contains sets of fixture files that are used to test the parsing and serialization logic. -Each test is made up of three fixture files: +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 @@ -20,7 +20,7 @@ Each test is made up of three fixture files: 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 three fixture files must exist: +`core/image` block, the following four fixture files must exist: 1. `core-image.html` (or `core-image-specific-test-name.html`). Must contain a `` block. @@ -35,7 +35,7 @@ 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) and (3): +there is a command you can run to generate (2) through (4): ```sh GENERATE_MISSING_FIXTURES=y npm run test-unit -- --grep 'full post content fixture'