coding-blocks / coding-blocks/hackerblocks.projectx
[Feature request] Need ability to see expected output for a custom test case
- Lingua principale
- JavaScript
- Stelle
- 7
- Fork
- 27
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
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.
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
The issue names no files, tests, or entry points; begin by locating the custom test compile-and-test flow and the judge's handling of official solutions. Define how the expected-output action runs a selected case and presents both outputs, including cases such as reversing 100, then verify the behavior through the relevant UI and judge tests.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- javascript
- Ambito
- full-stack, testing-qa
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 25/100