Have a look first into WebdriverIOs configuration options. First the Config File Īfter we have installed the codemod we can start transforming the first file. Given your time budget you can then start migrating the important test cases first and work your way down to tests you might even can delete. You can have Protractor and WebdriverIO tests running at the same time and start writing new tests in WebdriverIO. Given that Protractor will continued to be maintained until Angular version 15 (end of 2022) you still have enough time. Depending on the size of your team, amount of test files and the urgency to migrate you can try to transform all tests at once or file by file. The Protractor and WebdriverIO API is actually very similar, to a point where the majority of commands can be rewritten in an automted way through a codemod.

If you have issues with the migration, don't hesitate to contact us. Every step should be seen as guidance and less like a step by step instruction. Everyone has a different setup and uses Protractor in different ways. While we would love to have a fully automated process for this the reality looks different. The WebdriverIO team appreciates the work of every single Protractor contributor and hopes that this tutorial makes the transition to WebdriverIO easy and straightforward.

WebdriverIO has been influenced by a lot of Protractors design decisions which is why it is probably the closest framework to migrate over. It was initiated after the Angular team has announced that Protractor won't be longer supported. This tutorial is for people who are using Protractor and want to migrate their framework to WebdriverIO.