CodeceptJS VS WebdriverIO

But honestly, it may be preferable for you to use a single framework that does support both technologies (Web and Mobile) out of the box like webdriver.io or codecept.

Extending my screenshot tests, I discovered the useful configuration option to set fullPageScreenshots: true. When I wanted to set different window sizes, I was not the first one struggling to resize the browser window in CodeceptJS programmatically.

CodeceptJS – A wrapper for different tools in one interface. Language: JavaScript/TypeScript. Frameworks that are wrapped: Playwright, Webdriver.io, Puppeteer, Protractor, etc. The service also comes with a large community and is easy to install and use for e2e testing.

I'm saddened codeceptJS wasn't even mentioned. It's easily better than most of the ones listed except Cypress.

back when I was doing FE, I found https://codecept.io, which is the same concept as Cypress but with a Playwright driver. Have not used but thought it's worth a mention

There are enough blog posts about Jest or Cypress already, so let me introduce Codecept. It comes in two flavors. There is Codeception for PHP, and there is CodeceptJS for JavaScript which we will be using here.

No mention of Codecept.js?

This is where https://testomat.io comes in. I discovered this TCM whilst working with https://codecept.io/ and part of their Slack group. Testomatio is built by the team behind codeceptjs, bringing in vast experience in test automation behind the scenes.

I think you should add codeceptjs which does API testing on top of selenium / puppeteer tests.

Maybe take a look at https://codecept.io/

3.WebdriverIO: WebdriverIO is another popular open-source test automation framework. Key Features: Integrates well with popular testing frameworks (e.g., Mocha, Jasmine). Supports both synchronous and asynchronous commands. Works with various browsers and platforms

Webdriver.io

There is a tool called webdriver.io which purports to handle mobile automation. I haven't had a chance to play with it yet but it's on my radar.

We recently hired an engineer to write us integration tests with webdriver.io. All of our other tests run fine in Github actions - rspec, javascript jest, etc.

Your automated tests will act on behalf of a real user, open a real web browser (typically Chromium, Chrome, Firefox) using one an existing technology like Webdriver and add some syntactical sugar on top.

WebdriverIO (abbreviated as WDIO) is an E2E testing framework for Node.js. It allows you to automate all kinds of web and mobile applications using the Webdriver or Chrome DevTools protocols.

i recall having to deal with elements inside iframes and shadow roots when using webdriver.io for testing. you can always inspect an element and copy the selector. if it is unique to the page it should work