lsp: support detecting test built on top of Deno.test() like std/testing/bdd

[glebbash]

Is your feature request related to a problem? Please describe.

Testing UI integration does not show tests defined written in BDD style (https://deno.land/[email protected]/testing/bdd.ts).

Describe the solution you'd like

Would be nice to have them displayed. For now the only workaround is to just use default Deno.test

[kitsonk]

This is currently a design limitation, as it would require a reliable way to statically analyze a module for tests without actually running the module. Currently the static analysis is limited to a single module and identifying the Deno.test symbol and tracking tests that are registered.

Things like dynamically generated tests (or test steps) as well as other libraries that build on Deno.test cannot currently be analyzed and I personally currently can envision a good way to accomplish this at the moment. @dsherret I don't know if you have any thoughts on the topic.

[glebbash]

Definitely not an easy feature to implement but maybe it makes sense to implement it for bdd library only for now as it is part of std.

[KnorpelSenf]

I agree that static analysis for this would be very hard to do, and it is even harder to do it right. Doing it for /std only is the much more practical solution, albeit not as friendly towards third-party testing frameworks. However, I would argue that those frameworks are not equal to the standard library testing because, well, they're not in the standard library, and hence it is fine to only support /std here.

[nayeemrmn]

Ref denoland/vscode_deno#572, denoland/vscode_deno#793

[anion155]

Any update here?