Skip to content

Clarify test data config for validator test data #483

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+5 −3
Open

Clarify test data config for validator test data #483

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions spec/2023-07-draft.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -666,10 +666,12 @@ Their goal is to ensure the integrity and quality of the test data and validatio

#### Invalid Input

The files under `invalid_input` are invalid inputs.
The files under `invalid_input` are invalid inputs.
Unlike in `sample` and `secret`, there are no `.ans` files.
Each `tc.in` under `invalid_input` must be rejected by at least one input validator.

The relevant settings from [Test Case Configuration](#test-case-configuration) (`input_validator_args`, and `description`) can be set in `tc.yaml` for one test case, or `test_group.yaml` for all test cases in the same directory.

#### Invalid Output

The test cases in `invalid_output` describe invalid outputs for non-interactive problems.
Expand All @@ -683,7 +685,7 @@ In particular, for any test case in `invalid_output/`, for example `invalid_outp
<output_validator_program> tc.in tc.ans dir [arguments] < tc.out # MUST FAIL
```

The directory `invalid_output` must be organized into a tree-like structure similar to `secret` and may contain arguments in `test_group.yaml` files that are passed to the validators.
The relevant settings from [Test Case Configuration](#test-case-configuration) (`input_validator_args`, `output_validator_args`, and `description`) can be set in `tc.yaml` for one test case, or `test_group.yaml` for all test cases in the same directory.

### Valid Output

Expand All @@ -700,7 +702,7 @@ In particular, for any test case in `valid_output/`, for example `valid_output/t
<output_validator_program> tc.in tc.ans dir [arguments] < tc.out # MUST PASS
```

The directory `valid_output` must be organized into a tree-like structure similar to `secret` and may contain arguments in `test_group.yaml` files that are passed to the validators.
The relevant settings from [Test Case Configuration](#test-case-configuration) (`input_validator_args`, `output_validator_args`, and `description`) can be set in `tc.yaml` for one test case, or `test_group.yaml` for all test cases in the same directory.

### Samples

Expand Down