metro VS appium

For details on the implementation you can see Evan's PR to metro here.

Some development tools for the web are similar (Chrome debugger, mostly) to those for React Native, but other aspects are very different (working with the metro bundler, using Flipper, AsyncStorage debugging, more). Some techniques developers will use are the same (breakpoints and console logging), but others are different (knowing when to restart the packager vs reinstall the app on device).

We’re almost done with setting up the project. The last thing in the React Native app is to add watchFolders so metro knows where the linked node_modules are. The shared modules are symlinked by yarn, and since metro doesn’t follow symlinks we need to explicitly say it where the linked node_modules are.

Unfortunately it is what it is... I use intellij instead of webstorm since they're the same thing basically. I spent a shitton of time figuring out how to link a local package i was creating for my app only to discover about this issue that is almost as old as react native itself. (luckily there's rnx-kit that solves the problem). Not to talk about the impossibility to have one goddamn IDE to write both typescript, java and c++. Currently i have to write ts/js in intellij, then i have to switch to android studio to write java/c++.

React Native packager. Override instructions here.

React Native doesn't play nicely with most monorepo tools out of the box as Metro doesn't support symlinking.

Because React Native for Web is a React website, you can use front-end tools to build and run it. For example, you can build it with Webpack or Rollup instead of Metro bundler.

Before we can run the app, we still need do one more thing: make metro bundler compatible with Yarn workspaces' hoisting.

Second, sharing code with other projects (e.g., backend code, web apps) may get complicated. Out-of-the-box, React Native's metro bundler cannot reference code outside of the project's root directory. You can configure it to do so (and we'll do it as well later on). Still, once you do it, you'll also need to ensure dependencies resolution works correctly (to avoid loading two different versions of the same library, for example); which might not be as easy as it may sound.

appium plugin install --source=npm images Know more about images plugin, visit https://github.com/appium/appium/tree/master/packages/images-plugin

TestUI combines 2 different paradigm test automation frameworks, i.e., mobile (Appium) and desktop (Selenide), into one neat framework. In our opinion, it’s a great framework that offers vast functionality with easy-to-learn syntax, not to mention full access to Selenide methods in case something tricky needs to be done.

Feel free to look at the lerna/npm config: https://github.com/appium/appium

espresso is Google's general recommendation, but there are other tools out there that exist like appium or kaspresso. Sure there are more, just goigle it to see what else there is.

Appium exists from that Selenium family. That will do the job. https://appium.io/

End-to-end testing is completely different on React Native, however. None of the Selenium-based E2E testing tools will work; neither will newer tools like Cypress or Playwright. You may have expected this - these are all DOM-based, and there’s no DOM in React Native. So instead developers will have to learn Detox or Appium.

With iOS app testing, we test our iOS application on mobile devices (emulators or real devices, depending on the use case). Here, we pass it through various testing phases to ensure that the final version has minimum or no bugs. These can include manually inspecting the application like an end-user or running an automation framework like Appium or Testsigma.

Check More about Appium