Skip to content
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

Use online-judge-verify-helper to test our library #6

Open
GaurangTandon opened this issue Mar 18, 2020 · 2 comments
Open

Use online-judge-verify-helper to test our library #6

GaurangTandon opened this issue Mar 18, 2020 · 2 comments
Assignees
Labels
testing Automated or Manual tasks to check that there are no bugs in the code.

Comments

@GaurangTandon
Copy link
Collaborator

It is as good as our current approach and also generates cool looking documentation.

Example: https://beet-aizu.github.io/library/library/combinatorics/partition.cpp.html

It only supports two judges though, however, we can use this guys (beet-aizu's) problem links to find relevant judge problems for testing our own codes.

@GaurangTandon GaurangTandon added the enhancement Improving the quality of code and testing on the notebook label Mar 18, 2020
@AnimeshSinha1309 AnimeshSinha1309 added testing Automated or Manual tasks to check that there are no bugs in the code. and removed enhancement Improving the quality of code and testing on the notebook labels Mar 18, 2020
@AnimeshSinha1309
Copy link
Owner

Are we not already using this to test our code? The documentation sure, but how is this different from our current approach? And what judges does our current approach allow?

@AnimeshSinha1309 AnimeshSinha1309 self-assigned this Mar 22, 2020
@AnimeshSinha1309 AnimeshSinha1309 added this to the Notebook Release milestone Mar 22, 2020
@GaurangTandon
Copy link
Collaborator Author

I think our approach allows the same two judges only. However, I really dig the generated documentation. I believe the migration to online-judge-verify-helper should be painless, since both are very similar. Can we please do it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing Automated or Manual tasks to check that there are no bugs in the code.
Projects
None yet
Development

No branches or pull requests

2 participants