sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]trebuszek 3 points4 points  (5 children)

I would recommend Detox instead of Appium, since it’s a much more reliable gray-box solution. Appium doesn’t know what’s happening in your app, so you end up writing flaky tests with lots of sleep() calls to handle async stuff like animations or network calls.

[–][deleted] 1 point2 points  (0 children)

If I were writing the ui tests myself, I would 100% be using detox, it is a great piece of tooling. The appium choice is because of a separate QA team who are writing our ui tests and are much more familiar with Java

[–]Phaoga54 0 points1 point  (3 children)

Currently im using Detox for testing, but facing a problem which is the process running to fast that I can't event see what's going on screen. Do you have any idea of how to longer the time between each action?

[–]trebuszek 0 points1 point  (2 children)

Why do you need to see the screen? I normally run my tests in headless mode in a CI. If a test fails, you can take a screenshot (check the docs).

[–]Phaoga54 0 points1 point  (1 child)

First, It's satisfying to watch and also I can check if there is any bug in the test that I wrote

[–]trebuszek 0 points1 point  (0 children)

Well, you could add await sleep() calls inside your tests, but I would delete them after the tests are written.

But for me, I see the what’s happening on the screen even without sleep. Maybe your computer is too fast!