2018-08-29 01:58:27 +08:00
---
title: "SpaceVim test layer"
description: "This layer allows to run tests directly on SpaceVim"
---
# [Available Layers](../) >> test
<!-- vim - markdown - toc GFM -->
- [Description ](#description )
- [Install ](#install )
- [Key bindings ](#key-bindings )
<!-- vim - markdown - toc -->
## Description
This layers allow to run tests directly on Vim.
## Install
To use this configuration layer, add following snippet to your custom configuration file.
```toml
[[layers]]
name = "test"
```
2019-04-02 21:07:25 +08:00
## Configuration
To set or override any configuration ([see supported settings here](https://github.com/janko/vim-test)) you may use the `override_config` :
```toml
[[layers]]
name = "test"
[layers.override_config]
java_runner = "gradletest"
java_gradletest_executable = "./gradlew test"
```
In the example above is equivalent to adding the following in viml:
```viml
let test#java#runner = "gradletest"
let test#java#gradletest#executable = "./gradlew test"
```
In essence, it replaces `_` with `#` and prepends `test#` to the keys inside `override_config` .
2018-08-29 01:58:27 +08:00
## Key bindings
| Key Binding | Description |
| ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `SPC k n` | Run nearest test |
| `SPC k f` | Run test file |
| `SPC k s` | Runs the whole test suite (if the current file is a test file, runs that framework's test suite, otherwise determines the test framework from the last run test). |
| `SPC k l` | Runs the last test |
| `SPC k v` | Visits the test file from which you last run your tests (useful when you're trying to make a test pass, and you dive deep into application code and close your test buffer to make more space, and once you've made it pass you want to go back to the test file to write more tests) |
