@@ -9,7 +9,6 @@ Table of Contents *neotest-busted-table-of-contents*
9
9
- Parametric tests | neotest-busted-parametric-tests |
10
10
- Debugging tests | neotest-busted-debugging-tests |
11
11
- Luarocks and Busted | neotest-busted-luarocks-and-busted |
12
- - Running from the command line| neotest-busted-running-from-the-command-line |
13
12
- Contributing | neotest-busted-contributing |
14
13
- FAQ | neotest-busted-faq |
15
14
- Inspiration | neotest-busted-inspiration |
@@ -193,37 +192,6 @@ GLOBAL INSTALL ~
193
192
<
194
193
195
194
196
- RUNNING FROM THE COMMAND LINE *neotest-busted-running-from-the-command-line*
197
-
198
- A `test- runner.lua ` script is provided in the `scripts/` folder for running
199
- tests via the command line. This is useful for running all tests during CI for
200
- example.
201
-
202
- If you do not provide a `minimal_init.lua ` to set up your test environment, the
203
- script will look for one and source it. If you don’t specify any tests to
204
- run, the command will automatically try to find your tests in a `spec/` ,
205
- `test/` , or `tests/` directory.
206
-
207
- >shell
208
- $ nvim -l <path-to-neotest-busted> /scripts/test-runner.lua tests/my_spec.lua
209
- <
210
-
211
-
212
- USING BUSTED DIRECTLY ~
213
-
214
- You can also provide a `.busted` config file and run your tests using busted.
215
- Learn more about busted configuration files from the official docs
216
- <https://lunarmodules.github.io/busted/#usage > or take a look at the example
217
- here </.busted.example>.
218
-
219
- Pass extra arguments to `neotest` to run a specific task. For example, to run
220
- the `" integration" ` task in a test file:
221
-
222
- >lua
223
- require("neotest").run.run({ vim.fn.expand("%"), extra_args = { "--run", "integration" } })
224
- <
225
-
226
-
227
195
CONTRIBUTING *neotest-busted-contributing*
228
196
229
197
Thanks for considering to contribute. Please see the instructions here
0 commit comments