Add automated tests to the VSCode extension

[calebkiage]

Problem

The Visual Studio extension currently lacks automated tests, which is risky in the following ways:

• Manual Testing: All changes need to be manually verified, which is time-consuming and prone to human error.
• Risk of Regressions: Without automated tests, it's easy to miss regressions when refactoring, fixing bugs or adding features.
• Missed Scenarios: Manual testing makes it difficult to cover all possible scenarios, increasing the risk of undetected bugs.

Proposal

I propose adding automated tests for the extension to improve its reliability and maintainability. This will reduce the need for manual testing and help ensure new changes don’t introduce regressions.

To start, we could follow the official Visual Studio Code testing documentation, which outlines how to set up and run tests for extensions.

Benefits

• Improved Reliability: Automated tests will help catch issues early and ensure consistent behavior.
• Easier Maintenance: Tests will reduce the effort needed for manual verification, speeding up the development process.
• Better Coverage: We can write tests to cover a broader range of scenarios, improving overall confidence in the extension.

Next Steps

1. Set up a basic test framework following the Visual Studio Code extension testing guide.
2. Add unit tests for critical parts of the extension.
3. Expand coverage over time to include integration tests and more complex scenarios.

Feedback

I’d love to hear the team's thoughts on this proposal and any suggestions for specific areas we should focus on for testing first. Feel free to share any relevant experiences or resources that could help improve this plan.

[maisarissi]

@thewahome @petrhollayms would you mind sharing what is still pending on this PR and whether there is any work still needed? Otherwise, we should ship it. Thanks

[thewahome]

It was pending review of the work that @fey101 was doing which it got today. So right now it should be shipping 😀

[fey101]

We would either need someone with project repo rights to override request for changes by @baywet since they have been succintly addressed and tested and Vincent is OOO, or wait for him to resume work for the PR to be merged.