You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing this project is severely lacking is test cases. This primarily stems from the fact that the structure to build test cases is not simple, creating a barrier to entry to writing these cases.
We should invest some time into improving the test fixtures for testing, so that it is easier to write tests. And then, write some common test cases we are missing (Maybe go back and find bugs to add regression tests for?).
It would be nice to research what other language servers are doing to support testing.
Some particular areas we really should be testing:
File resolution (we need a way to create a directory structure for testing)
Which leads to, cross-file tests. This is pretty important, as many LSP actions are due to cross-file references!
The whole language server lifecycle (Nothing in LanguageServer.cpp is tested, we only use the workspace functions as entry points)
We could also write a few E2E integration tests with JSON input and output. Probably better to minimise these if possible.
The text was updated successfully, but these errors were encountered:
The main thing that is missing is scaffolding to perform tests that rely on multiple files, required files, or sourcemaps. Once we get something sorted for that, we are golden
One thing this project is severely lacking is test cases. This primarily stems from the fact that the structure to build test cases is not simple, creating a barrier to entry to writing these cases.
We should invest some time into improving the test fixtures for testing, so that it is easier to write tests. And then, write some common test cases we are missing (Maybe go back and find bugs to add regression tests for?).
It would be nice to research what other language servers are doing to support testing.
Some particular areas we really should be testing:
We could also write a few E2E integration tests with JSON input and output. Probably better to minimise these if possible.
The text was updated successfully, but these errors were encountered: