Nimblesite / Nimblesite/Basilisk

Test explorer child results never update + debug button does nothing (breakpoints not hit)

Open
#152 0 comments 0 reactions 1 assignee View on GitHub

@abdushakoor12 is already working on this.

Since Jul 15, 2026.

Dominant language
Rust
Stars
54
Forks
3
PR merge metrics
No merged PRs in 30d

Description

Summary

Two broken behaviours in the VS Code Test Explorer, observed in extension v0.15.1 (bundled basilisk 0.15.1).

Bug 1 — Child test results never update

Running a test class (e.g. TestBlackScholes) marks the parent green, but the child items (test_returns_float, test_atm_option_positive, test_deep_itm_approaches_intrinsic) stay unmarked. There is no way to tell whether the individual tests passed, failed, or even ran.

Image
Bug 2 — Debug button does nothing

Setting a breakpoint on test_returns_float and clicking Debug Test produces nothing — execution never stops at the breakpoint.

Evidence (extension log, window6, 2026-06-17)

Run path reports only a bulk pass with no per-test breakdown:

18:47:03.741 [info] Basilisk: execute_command 'basilisk.runTests' with 1 arg(s)
18:47:03.741 [info] Basilisk: tests passed (exit code 0)

The only signal back is "tests passed (exit code 0)" — the per-test results that would mark the children are absent, so the parent goes green and children are left blank.

Debug path attaches to debugpy and the session "starts", but the breakpoint is never hit:

18:49:37.603 [info] Basilisk: execute_command 'basilisk.debugTest' with 1 arg(s)
18:49:37.821 [info] Basilisk: debug session dbg-27b94020 for test '.../test_finance.py::TestBlackScholes::test_returns_float' on localhost:57363
18:49:37.866 [info] [Basilisk Debug] createDebugAdapterDescriptor called — type=basilisk-debug, request=attach, program=(none)
18:49:37.866 [info] [Basilisk Debug] Attach mode → localhost:57363
18:49:37.867 [info] [DAP Proxy] connected to debugpy at localhost:57363
18:49:37.867 [info] [Basilisk Debug] attach proxy listening on port 57367
18:49:38.876 [info] [Lifecycle] onDidChangeActiveDebugSession: id=143f4351 ...
18:49:38.902 [info] Debug session started: id=143f4351-... type=basilisk-debug

The DAP session is created and attached, but execution does not break.

Steps to reproduce

  1. Open examples/tests/test_finance.py.
  2. In Test Explorer, run TestBlackScholes. Observe parent goes green, children stay blank.
  3. Set a breakpoint on test_returns_float (line 22), click Debug Test. Observe nothing stops at the breakpoint.

Environment

  • Extension: nimblesite.basilisk 0.15.1 (darwin-arm64, bundled)
  • basilisk server: 0.15.1
  • OS: macOS (Darwin 25.5.0)
  • Workspace: Basilisk repo, examples/tests/

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.