Test case input is not displayed when tests fail

Open
#60 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
frontend, testing

Research direction

No file is named in the issue; start by locating the UI entry point that renders failed-test output diffs and inspect how test arguments are carried into that result. Show the failed case's input alongside the expected and actual output, then verify the failure view in the local web app.

Written by the indexing model from the issue text.

Description

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/)

Dominant language
Rust
Stars
54
Forks
8
Avg merge
11h 57m
Merged PRs (30d)
44

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sysprog21/codetrial

All issues in sysprog21/codetrial

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.