summaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorpommicket <pommicket@gmail.com>2025-09-23 14:26:18 -0400
committerpommicket <pommicket@gmail.com>2025-09-23 14:26:18 -0400
commitee57036c9cfdff27a81a38a9c5abc3b631f3a83c (patch)
tree812ad4393c68b0575c4010d9b25d39e20ceefb1c /tests
parent6ae91130c7c2ff1c11ecfe5798d8037954a4d570 (diff)
POM website
Diffstat (limited to 'tests')
-rw-r--r--tests/README.md10
-rw-r--r--tests/errors/README.md8
-rw-r--r--tests/interpretation/README.md15
-rw-r--r--tests/location/README.md9
-rw-r--r--tests/parsing/README.md7
5 files changed, 4 insertions, 45 deletions
diff --git a/tests/README.md b/tests/README.md
index 82c3eb3..8646a0d 100644
--- a/tests/README.md
+++ b/tests/README.md
@@ -1,9 +1 @@
-# Tests for POM
-
-Each subdirectory of this directory contains a type of test for POM parsers.
-They are described below:
-
-- [`parsing/`](parsing/README.md) — for testing that key-value pairs are correct
-- [`location/`](location/README.md) — for testing that definition location of keys is correctly determined
-- [`errors/`](errors/README.md) — for testing that error conditions are detected and gracefully handled
-- [`interpretation/`](interpretation/README.md) — for testing that numbers, booleans, and lists are parsed correctly
+See <https://pom.computer/tests/index.html>.
diff --git a/tests/errors/README.md b/tests/errors/README.md
index 7351033..c89eded 100644
--- a/tests/errors/README.md
+++ b/tests/errors/README.md
@@ -1,7 +1 @@
-# Error tests
-
-These tests are for checking that error conditions are
-detected and gracefully handled.
-
-Each test in this file has an error,
-and should be rejected by a compliant parser.
+See <https://pom.computer/tests/errors.html>.
diff --git a/tests/interpretation/README.md b/tests/interpretation/README.md
index 1691757..b39988c 100644
--- a/tests/interpretation/README.md
+++ b/tests/interpretation/README.md
@@ -1,14 +1 @@
-# Interpretation tests
-
-These tests check that booleans, numbers, floats, and lists are interpreted correctly.
-
-`int.pom`, `uint.pom`, `float.pom`, `bool.pom` — These files contain two sections,
-`[good]` and `[bad]`. The keys in `good` are in pairs `k.a` and `k.b`. Their values must
-parse to the same int/uint/float/boolean as each other.
-The values in `bad` are all invalid int/uint/float/booleans, and parsing them should
-return an error.
-
-`list.pom` — The keys in this file are in pairs `k.list` and `k.sep`.
-`k.list` is a POM list, and `k.sep` is the concatenation of `x;` for each entry
-`x` in the list with no leading/trailing whitespace (none of the entries have `;` in them, so this representation is
-unambiguous).
+See <https://pom.computer/tests/interpretation.html>.
diff --git a/tests/location/README.md b/tests/location/README.md
index caa8b6a..da79a41 100644
--- a/tests/location/README.md
+++ b/tests/location/README.md
@@ -1,8 +1 @@
-# Location tests
-
-These tests are for checking that definition location information
-is correctly recorded.
-
-Each test consists of a file `x.pom` and a file `x.locations.pom`.
-For every key in `x.pom`, there’s a corresponding key in `x.locations.pom`
-which is set to the line number where the key was defined in `x.pom`.
+See <https://pom.computer/tests/location.html>.
diff --git a/tests/parsing/README.md b/tests/parsing/README.md
deleted file mode 100644
index 2279c04..0000000
--- a/tests/parsing/README.md
+++ /dev/null
@@ -1,7 +0,0 @@
-# Parsing tests
-
-These tests are for checking that key-value pairs are parsed correctly.
-
-Each test `x` consists of two files, `x.pom` and `x.flat.pom`. These
-files should produce the exact same schema, but `x.flat.pom` is formatted
-in a simple way without any section headers, and only using doubly-quoted single-line strings.