backtrace-ls 0.0.2

See failed assertions as diagnostic messages next to your test code.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62

# Backtrace-LS

LSP server that shows test failures as diagnostics. Backtraces are parsed to show additional info diagnostics at different stack frames. Supports jumping forwards and backwards between stack frames with code actions.

Works out of the box in Helix (or any editor with an LSP client):

![Helix code action screenshot](./helix-action.png)

## Supported Test Runners

- Rust: `cargo test`, `cargo nextest`
- JavaScript: `Jest`, `Vitest`, Node Test Runner, `deno test`
- Go: `go test`
- PHP: `PHPUnit`

## Installation

```sh
cargo install backtrace-ls
```

## Editor Setup

Try out without installing by opening the demo project with Helix:

```bash
cd demo/rust
hx -v src/lib.rs
```

You should see the failing assertions inline next to test code.

Helix (`~/.config/helix/languages.toml`):

```toml
[language-server.backtrace-ls]
command = "backtrace-ls"

[[language]]
name = "rust"
language-servers = ["backtrace-ls", "rust-analyzer"]
```

Neovim:

```lua
vim.lsp.start({ name = "backtrace-ls", cmd = { "backtrace-ls" }, root_dir = vim.fn.getcwd() })
```

## Configuration

Optional `.backtrace-ls.toml` in project root:

```toml
[adapters.rust]
test_kind = "cargo-test"
extra_arg = ["--workspace"]
```

## License

MIT