Skip to content

Conversation

@ejgallego
Copy link

We add LSP tests for Verso documents; we reuse the core LSP testing infrastructure from lean4 upstream. See doc/dev/testing.md there for more details.

This is a draft PR, some comments:

  • maybe we should make the effort and use the lake test runner instead of the ad-hoc test runner here
  • location of files / entry point to be debated
  • we need to ship more tests

CHANGELOG.md Outdated
unreleased
----------

(Changes that can break existing programs are marked with a "*")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might be confusing with Markdown already using * for bulleted lists and boldface. Maybe we should have two headers?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We agree to follow what the ref manual does and just write "breaking change" in the changes entry.

@ejgallego
Copy link
Author

Summary of PR review discussion with David:

  • run test-runner via lake, maybe update test runner upstream to support -d
  • make tests run from lake test
  • note which files are copied from lean upstream
  • test all Verso LSP extensions
  • move changelog to manual, à la reference manual

@david-christiansen
Copy link
Collaborator

test all Verso LSP extensions

I think this one isn't really necessary for a merge here. It's important, but so is avoiding bitrot and getting value from the test that's already here. One or two more should suffice to validate the approach.

@ejgallego
Copy link
Author

update test runner upstream to support -d option

Upstream is happy with this so I'll proceed with that plan.

We add LSP tests for Verso documents; we reuse the core LSP testing
infrastructure from lean4 upstream. See `doc/dev/testing.md` there for
more details.

This is a draft PR, some comments:

- maybe we should make the effort and use the lake test runner instead
  of the ad-hoc test runner here
- location of files / entry point to be debated
- we need to ship more tests
@ejgallego ejgallego force-pushed the test_lsp branch 2 times, most recently from 9e3f79d to 70158ef Compare January 15, 2026 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants