Migrating to native testing about vscode-ceedling-test-adapter

[AlexandreMarkus]

Removing one deprecated dependency will also help to load the extension faster. Both Ceedling Test Explorer and Test Explorer UI are quite slow to activate when opening VS Code, so it will improve the booting time if you remove the dependency.
Thank you for your great work!

[mundodisco8]

I just discovered the native testing API and came here for the same reason, to see if the Ceedling adapter had moved to it. I see that you might not have much motivation to work on this if you don't use it that often and you might have moved on to other tools, but here's my vote if it helps 😄 The VS Code team had put an example here although I don't know TS and can't understand how challenging that would be.
Thanks for the tool in any case!

[numaru]

I think the Test Explorer UI also added for us a translation layer. And testExplorer.useNativeTesting: true in the settings.json should enable the native experience.

I didn't use vscode testing in a year, is there any reason other than the deprecation to switch to the native API and remove the Test Explorer UI dep? (any missing feature or Quality of Life improvement?)

[AlmazShai]

Ceedling Test Explorer depends on the Test Explorer UI extension, which depends on the Test Adapter Converter. Thus, the need to install all of these extensions is not as clear to the user, and for testing and debugging common projects, a manual for installing all three extensions should be described. Does migrating to the native API make this task easier?