Reduce number of tests that are now covered by the analysis server/SDK DAPs #6009
Description
There are a lot of tests that verify very specific details that used to exist here in the legacy-protocol -> VS Code mappings, that are now just part of LSP.
For example, there are a large number of completion tests:
Most of these are verifying things where the logic now exists in (and is tested in) the LSP server. Having all of these tests is somewhat redundant and makes the test runs slower.
We should instead just keep a few basic tests that ensure the general interaction with completion is working, and not all of the specifics about how the server maps things (these kinds of tests just fail if we do make changes to how we map things in the server).
The same is likely true for a lot of language features, and probably many debug features as a result of DAP moving to the SDKs too.
Activity
[-]Reduce number of tests that are now covered by the analysis server[/-][+]Reduce number of tests that are now covered by the analysis server/SDK DAPs[/+]DanTup commentedon May 14, 2026
I've merged some of the Flutter debugger tests together to speed things up a bit, but in general each bot is < 10mins which I think is acceptable (and there is value in some of these tests because it ensures the interaction with VS Code/DAPs is working).
So, I'm leaving this as-is for now. If tests break due to changes in server/DAP, I will consider whether we should fix or just remove them on a case-by-case basis (reducing the maintenance is a more worthwhile goal than speeding up the bots now IMO).