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

Testing UI in Lua? #72

Open
ggandor opened this issue Nov 3, 2021 · 2 comments
Open

Testing UI in Lua? #72

ggandor opened this issue Nov 3, 2021 · 2 comments
Labels
help wanted Extra attention is needed less NIH Leverage 3rd parties & try not to reinvent the wheel

Comments

@ggandor
Copy link
Owner

ggandor commented Nov 3, 2021

No description provided.

@ggandor ggandor added help wanted Extra attention is needed less NIH Leverage 3rd parties & try not to reinvent the wheel labels Nov 3, 2021
@ggandor ggandor pinned this issue Nov 3, 2021
@rktjmp
Copy link
Contributor

rktjmp commented Nov 5, 2021

The Neovim source has a pretty extensive "screen checking" tool in their test suite.

Test checking screen highlights: https://github.com/neovim/neovim/blob/master/test/functional/ui/hlstate_spec.lua and you can check the cursor location too which probably covers most of what you need (+ selections, deletions which are just screen content).

I am not sure how practical it is to use without the nvim source tree though, at least without a maintenance headache. I would maybe run the tests in a docker instance that clones and sets up the env, hooking your code with a bind mount.

@ggandor
Copy link
Owner Author

ggandor commented Nov 8, 2021

Well, that's better than nothing, thanks for bringing it to my attention! I will definitely study that.

@ggandor ggandor unpinned this issue Nov 23, 2021
@ggandor ggandor pinned this issue Jun 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed less NIH Leverage 3rd parties & try not to reinvent the wheel
Projects
None yet
Development

No branches or pull requests

2 participants