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

[Feature request] Need ability to see expected output for a custom test case #77

Open
nvmav opened this issue May 26, 2020 · 1 comment

Comments

@nvmav
Copy link

nvmav commented May 26, 2020

Provide a button "see expected output" before compile and test button (OR) when we compile and test, provide output for user's code and correct/expected output.

Given a test case, the judge should run that test case on the correct/official solution and give the results. This will help us get more clarity on problem statement and expected solution.

Example problem statement:
Give an integer, reverse it.
Sample input:
789
Sample output:
987

But, if integer 100 is input, when we reverse it, the expected output could be 001 or just 1.
If expected output option is there, it will help user understand what kind of output is expected in all possible scenarios far better. Else, user will have to do multiple submissions doing trail and error for all possible cases.

@boss-contributions-bot
Copy link

Thanks @nvmav, for raising the issue! 🙌

One of our mentors will revert on this soon. ✅

Star ⭐ this project and tweet 🐦 about BOSS 2020.

@nvmav nvmav changed the title [Feature request] ability to see expected output for a custom test case [Feature request] Need ability to see expected output for a custom test case May 26, 2020
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

No branches or pull requests

1 participant