Set up Windows runner for unit tests CI job

[garyttierney]

NOTE: still WIP.

Check list

• [x] I have read through the README (especially F.A.Q section)
• [x] I have searched through the existing issues or pull requests
• [ ] I have verified all existing unit tests pass (See the README on how to run)
• [ ] I have added new tests if appropriate
• [x] I have performed a self-review of my code and commented hard-to-understand areas
• [ ] I have made corresponding changes to the documentation (when necessary)

Description

This is an attempt to get the unit tests running under Windows in CI to hopefully help with testing issues like #109. There's a few kinks to iron out, so I've opened this as a draft until I get it passing. Ideally it'll remain mostly the same, with just the code-minimap stub and paths to neovim plugins changing.

Type of change

• [ ] Bug fix
• [ ] New feature
• [ ] Improvement of existing features
• [ ] Refactor
• [ ] Breaking change
• [ ] Documentation change
• [x] CI / CD

Test environment

• OS
  • [ ] Linux
  • [ ] Mac OS X
  • [ ] Windows
  • [ ] Others:
• Vim
  • [ ] Neovim:
  • [ ] Vim:

[garyttierney]

Ah, appears that CI won't run if it's a draft PR. I've marked it ready for review but left a note indicating it's still WIP.

Hm, nevermind. I think I don't have permission to change and run the workflow like this in a pull request. I'll create a new repository on my own account and test there before re-opening this.

[garyttierney]

This is running correctly now, but an issue in vim-testify prevents me overriding g:testify#logger#type to get good test result output. I'll try get that fix upstream.

[ZNielsen]

Just to make sure I understand the scope - this is intended to run the unit tests on Windows, but it does not fix the unit tests, correct?

[garyttierney]

Just to make sure I understand the scope - this is intended to run the unit tests on Windows, but it does not fix the unit tests, correct?

That's right. I'd hoped to look at them after finishing this but went down the rabbit hole of fixing vim-testify to get test results from it in CI. Unless you get to them before I wrap this branch up I'll take a look once I've got this producing good output.