feat(busted): Compact test output format #488
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello maintainers :)
Thank you for making plenary.nvim! When writing my own plugins I use the test suite of plenary so that I can run tests locally and on CI. This PR is another attempt at reducing the output of the busted implementation in plenary.nvim.
Related:
Unfortunately #86 was abandoned and even though some interest is shown in #237 this hasn't materialized.
The idea is that only pending and failing test messages are shown. I also reduced and formatted the output of fatal errors. Additionally, I noticed that when multiple instances of plenary.nvim are installed, the
busted.lua
file gets sourced from the first plenary.nvim found inruntimepath
. To fix this I tweaked the command which launches Neovim instances so that the plenary.nvim which is used to start the tests always uses thebusted.lua
file from the same repository. This is done by prepending the plenary.nvim repo path toruntimepath
at launch of each individual job.Finally there are some other modifications which basically make
PlenaryBustedFile
andPlenaryBustedDirectory
equivalent in that both commands now allow specifying a path as well as an optional options table. Both commands now follow the same code path so testing a single file basically works the same as testing a directory.Please let me know what you think, I'm not sure if the code I wrote is necessarily up to par with what is expected.