Automated testing strategy
Problem to solve
There are no automated tests for the extension (with exception of unit test for parseGitRemote function). We need to increase our automated test coverage to be able to make changes to the extension without introducing regressions.
Proposal
Create a testing strategy for the extension.
Personal opinion: At the beginning, we should focus on the highest level tests (integration/e2e). There is a lot of suggested work that is taking out major parts of the codebase (!53 (closed) !54 (closed) ). Unit tests written for these soon-to-be-replaced parts might not be the best use of our efforts
Acceptance criteria
- Testing pyramid for our VS Code Extension is described (i.e. what kind of tests we'll implement)
- Implement at least one example test for each level of testing (e.g. If we'll have unit tests, functional tests, and E2E tests, then at least one unit test, functional test, and E2E test).
- Example tests are reliably running in our CI
Links / references
- My personal extension having integration and unit tests
- Testing guide in the official documentation https://code.visualstudio.com/api/working-with-extensions/testing-extension