Re: [lsp4e-dev] Adding Test support in Debug Adapter Protocol

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

+1 on testing support - this has been on my mind too. For me the real
challenge is what level do we do the testing at, do we use SWT bot
tests at the UI level, or do we attempt to implement tests at the
debug element level. My initial feeling is to do most of them at the
debug element level.

I have found the mock debug
(https://github.com/Microsoft/vscode-mock-debug) useful for some of
the basic dev of the debug client. It could easily be extended to
support other special cases to test other areas. But what I really
want is a mock adapter written in Java that connects in the same
process to lsp4e.debug (as the test lsp does).

Jonah



~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On 23 January 2018 at 12:03, Mickael Istria <mistria@xxxxxxxxxx> wrote:
> Hi all,
>
> Testing is an important part of a development work. It's important that
> newer workflows based on such LSP or DAP can cover it properly.
> I've opened https://github.com/Microsoft/vscode-debugadapter-node/issues/154
> to suggest a way to include support for tests in the DAP. Feel free to
> comment if you agree, disagree, and to feed the discussions to drive to a
> good support for testing in this new era of tools.
>
> Cheers,
> --
> Mickael Istria
> Eclipse IDE developer, at Red Hat Developers community
> Elected Committer Representative at the Eclipse Foundation board of
> directors
>
> _______________________________________________
> lsp4e-dev mailing list
> lsp4e-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/lsp4e-dev
>