Skip to content

Support 'wrong' as test data category #51

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.

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
meisterT opened this issue Oct 14, 2016 · 5 comments
Open

Support 'wrong' as test data category #51

meisterT opened this issue Oct 14, 2016 · 5 comments

Comments

@meisterT
Copy link
Contributor

It would be nice if we could add test data to verify that the input checker fails on them but they should not be used for real judging.

@meisterT
Copy link
Contributor Author

It would be also nice to have a category for output validator checking.

@austrin
Copy link
Contributor

austrin commented Oct 17, 2016

Agree that this would be nice. Do you have concrete suggestions/preferences for how to extend the problem format to include this?

For input files, one could consider adding something like input_format_validators/bad_inputs containing .in files, or data/bad_inputs.

For output files, maybe one wants to be able to add incorrect outputs to some of the actual test cases, rather than adding new cases? If so, maybe allowing adding data files with suffix .out.wrong-<id>?

@niemela do you want to weigh in on this?

@meisterT
Copy link
Contributor Author

For separation of concerns input_format_validators/bad_inputs is probably nicer. Your suggestion for output files sounds good to me.

@Alicipy
Copy link

Alicipy commented Jul 26, 2018

Hey,

I implemented this feature based on your ideas. See pull request #86 for details.

@RagnarGrootKoerkamp
Copy link
Contributor

I've just implemented some version of this for BAPCtools: RagnarGrootKoerkamp/BAPCtools#35.

Happy to change that to whatever structure is decided upon eventually.

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

No branches or pull requests

4 participants