Skip to content

Commit d6f3bdf

Browse files
Remove custom cli support (#48)
1 parent 802d63a commit d6f3bdf

File tree

6 files changed

+2
-262
lines changed

6 files changed

+2
-262
lines changed

.busted.example

Lines changed: 0 additions & 14 deletions
This file was deleted.

.github/workflows/style.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,4 @@ jobs:
1616
with:
1717
token: ${{ secrets.GITHUB_TOKEN }}
1818
version: 0.16.1
19-
args: --check lua/ tests/ scripts/
19+
args: --check lua/ tests/ test_files/

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,6 @@
44
2. Make changes.
55
3. Make sure tests and styling checks are passing.
66
* Run tests by running `./tests/run_tests.sh` in the project directory. Running the tests requires [`plenary.nvim`](https://github.com/nvim-lua/plenary.nvim), [`neotest`](https://github.com/nvim-neotest/neotest), [`nvim-nio`](https://github.com/nvim-neotest/nvim-nio), and [`nvim-treesitter`](https://github.com/nvim-treesitter/nvim-treesitter). You may need to update the paths in `./tests/minimal_init.lua` to match those of your local installations to be able to run the tests. A `busted` executable is also needed to run the tests so set it up as per the instructions in the [README](/README.md).
7-
* Install [stylua](https://github.com/JohnnyMorganz/StyLua) and check styling using `stylua --check lua/ scripts/ tests/ test_files/`. Omit `--check` in order to fix styling.
7+
* Install [stylua](https://github.com/JohnnyMorganz/StyLua) and check styling using `stylua --check lua/ tests/ test_files/`. Omit `--check` in order to fix styling.
88
4. Submit a pull request.
99
5. Get it approved.

README.md

Lines changed: 0 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,6 @@ neovim as the lua interpreter.
4141
- [Parametric tests](#parametric-tests)
4242
- [Debugging tests](#debugging-tests)
4343
- [Luarocks and Busted](#luarocks-and-busted)
44-
- [Running from the command line](#running-from-the-command-line)
4544
- [Contributing](#contributing)
4645
- [FAQ](#faq)
4746

@@ -210,34 +209,6 @@ The following command will install busted in your home directory.
210209
> luarocks install busted
211210
```
212211

213-
## Running from the command line
214-
215-
A `test-runner.lua` script is provided in the `scripts/` folder for running
216-
tests via the command line. This is useful for running all tests during CI for
217-
example.
218-
219-
If you do not provide a `minimal_init.lua` to set up your test environment, the
220-
script will look for one and source it. If you don't specify any tests to run,
221-
the command will automatically try to find your tests in a `spec/`, `test/`, or
222-
`tests/` directory.
223-
224-
```shell
225-
$ nvim -l <path-to-neotest-busted>/scripts/test-runner.lua tests/my_spec.lua
226-
```
227-
228-
### Using busted directly
229-
230-
You can also provide a `.busted` config file and run your tests using busted.
231-
Learn more about busted configuration files from the [official
232-
docs](https://lunarmodules.github.io/busted/#usage) or take a look at the example [here](/.busted.example).
233-
234-
Pass extra arguments to `neotest` to run a specific task. For example, to run
235-
the `"integration"` task in a test file:
236-
237-
```lua
238-
require("neotest").run.run({ vim.fn.expand("%"), extra_args = { "--run", "integration" } })
239-
```
240-
241212
## Contributing
242213

243214
Thanks for considering to contribute. Please see the instructions [here](/CONTRIBUTING.md).

neotest-busted-scm-1.rockspec

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,6 @@ build = {
3333
type = "builtin",
3434
copy_directories = {
3535
"doc",
36-
"scripts",
3736
},
3837
}
3938

scripts/test-runner.lua

Lines changed: 0 additions & 216 deletions
This file was deleted.

0 commit comments

Comments
 (0)