Testing Complex VSCode Extensions With the Power of Web Standards
summary
A WebDriver-based test service called WDIO VS Code service automates Electron and browser VS Code flavors, mapping each VS Code release to the correct Chromedriver, working around Electron camelCase args with a fake-binary shim, and injecting VS Code APIs into webviews. Tests use page objects per VS Code version with locator maps and TypeScript decorators to keep selectors maintainable. The service runs end-to-end checks — it boots VS Code, starts Live Server, visits the served page, and exercises the marquee webview successfully.
AI-written summary · about
chapters (7)
- 0:00Introduction to VS Code
- 3:01IDEs and Extensions
- 5:20Complex Extension Workflows
- 9:28Testing VS Code Extensions
- 13:59Building a Testing Service
- 18:46Implementing Page Objects
- 23:56Practical Examples and Demo
related talks
24mTesting extensions for Visual Studio Code
28mWrap WebdriverIO to Build your Test Framework
55mModern Web Testing: Going Beyond Selenium
29mNext level of Front end testing with Devtools and WebDriver
48mThe Nuts and Bolts of WebdriverIO
44mWebdriverIO: The next-gen automation test framework you should know about
20mComponent Testing with Playwright
25mAutomated Performance Testing With WebDriver