Closed vkavitha closed 1 year ago
Post above tasks, when I started looking for ways to access the views/sections in the extension to get access to the UI objects, there was not much information available on the same. So moved on to vscode-extenstion-tester which had the paging objects, makes it easier to work with extension UI.
Observations
Comparatively easier than the default test suite approach w.r.to the access to UI objects. There are some inconsistencies when we run the tests repeatedly. need to check why is that.
Project -
log generated in the debug console- log.txt
reference (steps) - https://developers.redhat.com/blog/2019/11/18/new-tools-for-automating-end-to-end-tests-for-vs-code-extensions
For Mac as well, Basic vscode-extension-tester setup, test trial is done one minor issue <specific to my Mac setup , documenting here for any future reference >
1.vcode tester gets the manifest.json from ” https://raw.githubusercontent.com/Microsoft/vscode/1.75.1/cgmanifest.json” to get the compatible chromium driver to install
Closing as test automation has been implemented using vscode-extension-tester
framework.
Exploring framework options for liberty-tools-vscode integration testing
1. vscode-extension-tester
2. webdriverio
3. Basic extension suite that comes with vscode