-
Notifications
You must be signed in to change notification settings - Fork 141
Open
Description
We have some Ruby scripts in the repo that can perform some testing for us, but there's not a ton of things that it covers. Let's discuss the hurdles to be leaped in this issue and design an approach:
- What's the state-of-the-art for testing these sort of plugins for Vim?
- Can we automate the testing of the syntax rendering?
- Is there a particular service / GitHub action that works "the best"?
- Is there a way for it to be run locally as well? (Creating a PR just to run the tests is annoying)
- Will the errors be clear to the developer so they can easily understand what needs fixing?
- What's the appropriate minimum to test? We should avoid testing "too much" and venture into the world of flakey tests.
Anything else?
Metadata
Metadata
Assignees
Labels
No labels