Skip to content

Conversation

thorehusfeldt
Copy link
Collaborator

This branch aims to establish expected invalidation of test data, in particular, handling purposefully invalid test cases in invalid_input, invalid_answer and invalid_output.

@thorehusfeldt thorehusfeldt marked this pull request as draft January 28, 2024 14:10
thorehusfeldt and others added 23 commits January 28, 2024 15:43
This gets rid of ["answer", "input", "output"] or
[validate.Class.INPUT, validate.Class.ANSWER, validate.Class.OUTPUT]
in favour of just passing the class itself, i.e.,
[validate.InputValidator, validate.OutputValidator, validate.AnswerValidator].
Makes some code more type-safe, and class constructor dispatch becomes trivial.
sanity_check operates on a file, and figures out the desired
mode from the file suffix (.in, .ans, .out). Whitespace strictness
is an explicit parameter (rather than inferred from validation mode.)
Reduce parameters to one.
Reduce return types from four (!) to "only" three
@thorehusfeldt thorehusfeldt marked this pull request as ready for review February 4, 2024 11:29
@RagnarGrootKoerkamp RagnarGrootKoerkamp force-pushed the feat/invalidation branch 3 times, most recently from c45e8f3 to 4007322 Compare February 8, 2024 23:41
@RagnarGrootKoerkamp RagnarGrootKoerkamp merged commit 3496c58 into master Feb 10, 2024
@RagnarGrootKoerkamp RagnarGrootKoerkamp deleted the feat/invalidation branch February 10, 2024 13:56
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.

3 participants