marco-core 1.1.0

nom-based Markdown parser, HTML renderer, and intelligence features (highlights, diagnostics, completions) for the Marco editor.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

# tools/tests

Extension spec conformance tests that run as `[[test]]` targets inside the
`tools/perf-lab` crate. These tests load fixture files from `tools/spec/` and
assert strict `parse → render → assert_eq!` equality.

## `extension_spec_it.rs`

| Test function | Fixture | Feature gate |
|---|---|---|
| `test_diagram_fixtures_match_expected_html` | `tools/spec/diagram.json` | `render-diagrams` |
| `test_gfm_fixtures_match_expected_html` | `tools/spec/gfm.json` | _(none)_ |
| `test_marco_fixtures_match_expected_html` | `tools/spec/marco.json` | _(none)_ |
| `test_math_fixtures_match_expected_html` | `tools/spec/math.json` | `render-math` |
| `test_combos_fixtures_match_expected_html` | `tools/spec/combos.json` | _(none)_ |

Run all five suites:

```bash
cargo test --manifest-path tools/perf-lab/Cargo.toml --test extension_spec_it
```

Run a single suite:

```bash
cargo test --manifest-path tools/perf-lab/Cargo.toml --test extension_spec_it \
  test_marco_fixtures_match_expected_html
```

Each failing case prints: fixture name, example number, section, line range,
input markdown, expected HTML, and actual HTML.

See [`tools/spec/README.md`](../spec/README.md) for fixture file descriptions
and [`Documentation/testing.md`](../../Documentation/testing.md) for the
broader test inventory.