Language server for real-time testing diagnostics
Find a file
2024-10-30 23:45:39 +09:00
.github/workflows ci: update release procedure 2024-10-10 00:35:52 +09:00
.vim chore(demo): update editor config according to previous schema change 2024-10-25 00:42:11 +09:00
crates/adapter chore: update version 2024-10-19 17:13:34 +09:00
demo Merge pull request #43 from kbwo/fix/data-structure 2024-10-30 23:43:36 +09:00
doc docs: add documentation for adapter 2024-09-29 00:53:43 +09:00
src fix: change data structure of initialization params 2024-10-25 00:40:19 +09:00
.gitignore mvp 2024-05-07 00:08:27 +09:00
Cargo.lock chore: update version 2024-10-19 17:13:34 +09:00
Cargo.toml chore: update version 2024-10-19 17:13:34 +09:00
CONTRIBUTING.md feat: implement phpunit adapter 2024-09-23 17:56:13 +09:00
justfile mvp 2024-05-07 00:08:27 +09:00
LICENSE add license 2024-06-30 22:39:44 +09:00
README.md doc: update README 2024-10-30 23:45:39 +09:00

testing-language-server

General purpose LSP server that integrate with testing. The language server is characterized by portability and extensibility.

Motivation

This LSP server is heavily influenced by the following tools

These tools are very useful and powerful. However, they depend on the execution environment, such as VSCode and Neovim, and the portability aspect was inconvenient for me. So, I designed this testing-language-server and its dedicated adapters for each test tool to be the middle layer to the parts that depend on each editor.

This design makes it easy to view diagnostics from tests in any editor. Environment-dependent features like neotest and VSCode's built-in testing tools can also be achieved with minimal code using testing-language-server.

Instllation

cargo install testing-language-server
cargo install testing-ls-adapter

Features

Configuration

VSCode

Install from VSCode Marketplace. You should set adapterCommand in initializationOptions for each project. You can see the example in settings.json.

coc.nvim

Install from :CocInstall coc-testing-ls. You should set adapterCommand in initializationOptions for each project. You can see the example in See more example

Neovim (nvim-lspconfig)

local lspconfig = require('lspconfig')
local configs = require('lspconfig.configs')
local util = require "lspconfig/util"

configs.testing_ls = {
  default_config = {
    cmd = { "testing-language-server" },
    filetypes = { "rust" },
    root_dir = util.root_pattern(".git", "Cargo.toml"),
      init_options = {
        enable = true,
        fileTypes = {"rust"},
        adapterCommand = {
        -- See test execution settings for each project
        -- This configuration assumes a Rust project
          rust = {
            path = "testing-ls-adapter",
            extra_arg = { "--test-kind=cargo-test", "--workspace" },
            include = { "/demo/**/src/**/*.rs"},
            exclude = { "/**/target/**"},
          }
        },
        enableWorkspaceDiagnostics = true,
        trace = {
          server = "verbose"
        }
      }
  },
  docs = {
    description = [[
      https://github.com/kbwo/testing-language-server

      Language Server for real-time testing.
    ]],
  },
}

lspconfig.testing_ls.setup{}

Helix

See language.toml.

⚠️ Breaking Changes (2024-10-25)

The configuration structure for adapter commands has been changed:

Before:

"adapterCommand": {
  "rust": [
    {
      "path": "testing-ls-adapter",
      "extra_arg": ["--test-kind=cargo-test"]
      // ...
    }
  ]
}

After:

"adapterCommand": {
  "rust": {
    "path": "testing-ls-adapter",
    "extra_arg": ["--test-kind=cargo-test"]
    // ...
  }
}

The array wrapper has been removed to simplify the configuration structure. Please update your settings accordingly.

Adapter

  • cargo test
  • cargo nextest
  • jest
  • deno test
  • go test
  • phpunit
  • vitest
  • node --test (Node Test Runner)

Writing custom adapter

⚠ The specification of adapter CLI is not stabilized yet.

See ADAPTER_SPEC.md and spec.rs.