Closed mickaelistria closed 5 years ago
It is more important to set up automatic test cases to cover its debugging protocol behaviors in VSCode mode (MI has been covered by Samsung's own test cases).
As I am working on the MonoDevelop extension for .NET Core debugging, I feel that such protocol related test cases can be shared between this project and https://github.com/lextudio/monodevelop.netcoredbg. It will be tricky which language should be used to write the protocol test cases, C# or Java.
Note that I raised two issues of the debugger,
https://github.com/Samsung/netcoredbg/issues/20 https://github.com/Samsung/netcoredbg/issues/19
which might lead to breaking changes. You should be aware of them in case you need to change accordingly.
Test for protocol support itself support should go into Eclipse LSP4E project. There is a Mock Debug Adapter that's existing for that purpose. If you're willing to contribute to this effort more generically for Eclipse IDE support of Debug Adapter Protocol, please join the lsp4e-dev@eclipse.org mailing-list and ask there any question you face.
Sure. I will check that.
It seems like netcoredbg sometimes has severe glitches, and aCute has nothing to detect them and would ship a totally failing debugging story without noticing. We need aCute to include automated tests for debug story before next release.