Background & Context
During an interactive interview session with the Jim, my code failed the first test case. The interviewer asked me to explain why my solution failed on that particular case.
While the UI displays the output diff (expected vs. actual output), it does not provide the input data (test arguments) for the failed test case.
Without the input, it is difficult to trace the execution path or analyze the root cause of the logic failure.
Expected Behavior
Display the test case input alongside the existing output diff to provide sufficient context for debugging.
Environment
OS: macOS 26.2
Access Method: Web browser via local server (http://127.0.0.1:3000/)
Background & Context
During an interactive interview session with the Jim, my code failed the first test case. The interviewer asked me to explain why my solution failed on that particular case.
While the UI displays the output diff (expected vs. actual output), it does not provide the input data (test arguments) for the failed test case.
Without the input, it is difficult to trace the execution path or analyze the root cause of the logic failure.
Expected Behavior
Display the test case input alongside the existing output diff to provide sufficient context for debugging.
Environment
OS: macOS 26.2
Access Method: Web browser via local server (http://127.0.0.1:3000/)