react-developer-roadmap VS WebdriverIO

Navigate your React journey like a pro with this comprehensive developer roadmap - a must for every React enthusiast.

I would suggest you start with a beginner friendly like Python to learn the basic with how it works and once you’re confortable doing if, else, loops, functions, classes then you could see what kind of things you what do develop so you’ll learn a specific language or set of languages with a roadmap (look for " roadmap github", an exemple would be this: https://github.com/adam-golab/react-developer-roadmap), and follow the roadmap with google search, YouTube tutorials, Udemy classes, etc

Discovered the concept of "developer roadmaps" on Github. Two good resources are the frontend roadmap(https://github.com/kamranahmedse/developer-roadmap) and this react roadmap(https://github.com/adam-golab/react-developer-roadmap).

So, my personal advice to learn react.js is to not stick to any one course or tutorial. The best way to learn react.js is to explore blogs which is written by developers but for that you need to get an index or kind of roadmap of react.js

There are many topics to learn in react further than some components and a couple hooks. For example, state management, styling, testing, webpack, even React Native if you want to get into mobile apps development. Here's a link to the most complete react roadmap I've seen, I think it can be very helpful for you to know what's next in your learning stack

React Developer Roadmap Roadmap to becoming a React developer

If you think the roadmap can be improved, please do open a PR with any updates and submit any issues on the original git repo, Adam Golab’s React-developer-roadmap.

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