POM error tests

From ee57036c9cfdff27a81a38a9c5abc3b631f3a83c Mon Sep 17 00:00:00 2001 From: pommicket Date: Tue, 23 Sep 2025 14:26:18 -0400 Subject: POM website --- site/tests/errors.html | 28 ++++++++++++++++++++++++++++ site/tests/index.html | 28 ++++++++++++++++++++++++++++ site/tests/interpretation.html | 35 +++++++++++++++++++++++++++++++++++ site/tests/location.html | 27 +++++++++++++++++++++++++++ site/tests/parsing.html | 27 +++++++++++++++++++++++++++ 5 files changed, 145 insertions(+) create mode 100644 site/tests/errors.html create mode 100644 site/tests/index.html create mode 100644 site/tests/interpretation.html create mode 100644 site/tests/location.html create mode 100644 site/tests/parsing.html (limited to 'site/tests') diff --git a/site/tests/errors.html b/site/tests/errors.html new file mode 100644 index 0000000..eeaacfa --- /dev/null +++ b/site/tests/errors.html @@ -0,0 +1,28 @@ + + + + + + POM error tests + + + +

+ POM homepage · POM tests +

Error tests for POM

+ +

+ These tests are found in the tests/errors directory of the main POM repository. +

+ These tests are for checking that error conditions are + detected and gracefully handled. +

+ Each test in this directory has an error, + and should be rejected by a compliant parser. +

+ + + diff --git a/site/tests/index.html b/site/tests/index.html new file mode 100644 index 0000000..40642b0 --- /dev/null +++ b/site/tests/index.html @@ -0,0 +1,28 @@ + + + + + + POM tests + + + +

+ POM homepage +

Tests for POM

+ The tests listed below are freely available for checking that POM configuration parsers are implemented correctly. +

+ There are currently four test suites for POM parsing: +

parsing — for testing that key-value pairs are correct
location — for testing that definition location of keys is correctly determined
errors — for testing that error conditions are detected and gracefully handled
interpretation — for testing that numbers, booleans, and lists are parsed correctly

+ + + diff --git a/site/tests/interpretation.html b/site/tests/interpretation.html new file mode 100644 index 0000000..0bc4a5c --- /dev/null +++ b/site/tests/interpretation.html @@ -0,0 +1,35 @@ + + + + + + POM interpretation tests + + + +

+ POM homepage · POM tests +

Interpretation tests for POM

+ These tests are found in the tests/location directory of the main POM repository. +

+ 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 (none of the entries have `;` in them, so this representation is + unambiguous). +

diff --git a/site/tests/location.html b/site/tests/location.html new file mode 100644 index 0000000..3a1ec39 --- /dev/null +++ b/site/tests/location.html @@ -0,0 +1,27 @@ + + + + + + POM location tests + + + +

+ POM homepage · POM tests +

Location tests for POM

+ These tests are found in the tests/location directory of the main POM repository. +

+ 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. +

+ + diff --git a/site/tests/parsing.html b/site/tests/parsing.html new file mode 100644 index 0000000..00058ed --- /dev/null +++ b/site/tests/parsing.html @@ -0,0 +1,27 @@ + + + + + + POM parsing tests + + + +

+ POM homepage · POM tests +

Parsing tests for POM

+ These tests are found in the tests/parsing directory of the main POM repository. +

+ 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. +

+ + + -- cgit v1.2.3