Skip to content

Comments

chore: formalize and test conformance test file naming#115

Open
crowecawcaw wants to merge 1 commit intoOpenJobDescription:mainlinefrom
crowecawcaw:filenames
Open

chore: formalize and test conformance test file naming#115
crowecawcaw wants to merge 1 commit intoOpenJobDescription:mainlinefrom
crowecawcaw:filenames

Conversation

@crowecawcaw
Copy link
Contributor

@crowecawcaw crowecawcaw commented Feb 18, 2026

We introduced the conformance test suite recently. It has a directory and file name structure convention but:

  1. The convention is loosely documented
  2. It does not cover well how to specific sections in RFCs, if they exist
  3. The file structure is not enforced.

This PR fully documents the structure, adds filename prefixes for extensions, adds an automated test to ensure the tests follow the prescribed structure, and renames some extension tests to match the new scheme. The automated test will ensure test additions follow existing patterns.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Signed-off-by: Stephen Crowe <6042774+crowecawcaw@users.noreply.github.com>
@crowecawcaw crowecawcaw requested a review from a team as a code owner February 18, 2026 23:55

When both `.invalid` and `.test` are present, `.invalid` comes first: `1.1--desc.invalid.test.yaml`

Each extension spec should use a short, consistent prefix (e.g., `chunk` for TASK_CHUNKING, `redact` for REDACTED_ENV_VARS). The base [Template Schema](../wiki/2023-09-Template-Schemas.md) needs no prefix — a leading number implies it.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The redaction and chunk extensions add language to the existing spec though, they don't introduce any new ones. Shouldn't the chunk-3.4.1.5-* just be 3.4.1.5-* still?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants