Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add testing #77

Open
1 of 3 tasks
cseickel opened this issue Jan 18, 2022 · 1 comment
Open
1 of 3 tasks

Add testing #77

cseickel opened this issue Jan 18, 2022 · 1 comment
Labels
build Used for CI, linting, testing, and other dev tools.

Comments

@cseickel
Copy link
Contributor

cseickel commented Jan 18, 2022

We really need to add a full suite of tests to this project, which can be run both locally and as a merge check. A handful of tests were created in #61 using plenary, which looks pretty good.

What needs to be tested?

  • Every documented config option should do what it says
  • Every bug fix should include a regression test (maybe just for future fixes?)
  • All variations of vim commands (:NeoTree...) should do what the documentation says.
@cseickel cseickel added the build Used for CI, linting, testing, and other dev tools. label Jan 18, 2022
@levouh
Copy link
Contributor

levouh commented Jan 29, 2022

I'll be working on #61 this weekend, and with the new source design it should be pretty trivial. Right now that one focuses on unit tests, however you can do functional tests with plenary's version of busted as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Used for CI, linting, testing, and other dev tools.
Projects
None yet
Development

No branches or pull requests

2 participants