Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Candidate test cases persist across interviews for the same problem in the same tab

Closed
  • Is something wrong?
#336 3 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@MZGamer is already working on this.

Since Oct 17, 2026.

  • #337 by @MZGamer — open

Assessment

This issue has not been assessed yet.

Description

Observed behavior

When a candidate adds custom test cases during an interview and ends the interview, entering the same problem again within the same browser tab restores the custom test cases from the previous session. Because custom cases are persisted under codetrial.candidateCases.${problem.page} in sessionStorage and are never removed upon concluding an interview, previous test cases unexpectedly bleed into subsequent interview sessions.

Expected behavior

Custom test cases should be scoped to a single interview session. When an interview ends or when the candidate leaves the room, any persisted custom test cases for that problem should be cleared from sessionStorage so that a new interview starts with an empty test case list. Active in-session reloads should continue to preserve candidate test cases.

Reproduction
  1. From the lobby, select any coding problem (e.g., chargeback-pair-match or Two Sum) and enter the interview.
  2. Expand the "Add a cases" panel, enter valid inputs (e.g., Input: [[-3,4,3,90],0], Excepted:[[0,2]]), and click "Add case".
  3. Click "End interview" to conclude the interview.
  4. Navigate back to the lobby and start another interview on the same problem without closing the tab or restarting the browser.
  5. Expand "Add a cases" and observe that the case added in step 2 is still displayed.
CodeTrial version

Automated build of https://github.com/sysprog21/codetrial/commit/b491026dd2d779c4e8d82adcfb01ce49c6421a98.

Environment

OS: Windows 10
Broswer: Chrome

Sanitized evidence

Inspecting sessionStorage via the browser developer console after clicking "End interview" reveals that the key is retained:

// In browser console after clicking End interview:
window.sessionStorage.getItem("codetrial.candidateCases.chargeback-pair-match");
// Output: "[{"input":[[-3,4,3,90],0],"expected":[[0,2]]}]"
Public data confirmation
  • I removed credentials, session tokens, candidate recordings, and personal interview content from this public report.
Dominant language
Rust
Stars
160
Forks
64
Avg merge
1d 11h
Merged PRs (30d)
132

Getting set up

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.