You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DEVELOPMENT.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -183,6 +183,22 @@ make test-basic
183
183
make test-config
184
184
```
185
185
186
+
### Running Tests from Within Neovim/Claude Code
187
+
188
+
When running tests from within a Neovim instance (such as when using Claude Code via claude-code.nvim), the test script automatically handles the `$NVIM` environment variable which normally points to a socket file instead of the nvim executable.
189
+
190
+
The test script will:
191
+
192
+
- Use the `$NVIM` variable if it points to a valid executable file
193
+
- Fall back to finding `nvim` in `$PATH` if `$NVIM` points to a socket or invalid path
194
+
- Display which nvim binary is being used for transparency
195
+
196
+
To verify the NVIM detection logic works correctly, you can run:
197
+
198
+
```bash
199
+
./scripts/test_nvim_detection.sh
200
+
```
201
+
186
202
### Writing Tests
187
203
188
204
Tests are written in Lua using a simple BDD-style API:
0 commit comments