Нюансы автоматизированного тестирования расширений для VS Code с помощью WebdriverIO

Привет! Я инженер по контролю качества продукта Amplicode в компании Haulmont . Одним из направлений деятельности нашей компании является разработка плагинов для IntelliJ IDEA и расширений для VSCode. Передо мной встала задача протестировать расширение Amplicode Frontend для VS Code. Задача оказалась не самой тривиальной и в процессе мы столкнулись с немалым количеством проблем и нюансов, о которых я и хочу рассказать в этой статье.

https://habr.com/ru/companies/haulmont/articles/879002/

#webdriverio #qa_automation #vscode_extension #typescript #webdriver

first RC is out for #WebdriverIO v9 support!
https://www.npmjs.com/package/wdio-ui5-service/v/3.0.0-rc.0
go ahead, test test test!

look who I got to hang with over breakfast in the Big Apple 🍏 🗽😁
#WebdriverIO

What's better than a #wdi5 community event? A combined #WebdriverIO & #wdi5 event ✌️
On Apr 11, @bromann. @pmuessig and @vobu will be on-site at Cloud44 in WDF (https://maps.app.goo.gl/Ce2PjttCgPQ19umk6?g_st=ic) hosting talks, drinks and friendly chatter all around your favorite Testing Tools 😀

waaaah, pleeease, how cool 😎 is #webdriverio ?!
they're awarding 💸 for PRs! incentive level 🆙
let's do some thinking around @_wdi5_ on this...

#WebDriverIO already has #WebDriver in its name, so since I already listed that as an advantages for #Nightwatch I would probably enjoy that too. Never tried it though, so I have no idea how enjoyable it is in practice.

🔎 I am currently searching for an #E2ETesting library. The most important thing for me to test, which I probably cannot test in a different way, is native browser notifications after receiving a push notification from a #JavaScript #ServiceWorker.

Solutions I know of include #Selenium, #WebDriverIO, #Playwright, #NightWatch and #Cypress.

❓ Do you have any other ideas or opinions on those testing libraries?

Going to add a few thoughts for some of them in separate toots.

@josep Personally I'm partial to #WebDriverIO since it actually uses the #WebDriver specification and is a little more future-proof as a result IMHO. Also comes with #Angular integration!

```
$ ng add @wdio/schematics
```

https://webdriver.io/

Note to self: when writing E2E tests with WebDriverIO, start with #Firefox first.

The gecko driver is much more finicky than the chrome driver. Things like buttons always need a waitForClickable before clicking, something you don't really need to do in #Chrome.

#softwaretesting #webdriverio #wdio #webdriver #selenium

I am currently struggling with a legacy #WebdriverIO #TestAutomation repo that has literally hundreds of specfiles all in one directory just called "tests". What do they test? Lord knows. A directory structure is all I want for Christmas right now