numros

Hi there,

I work in a big project with about 10 teams who focus on different parts of an app. There is a rotation problem and people who come in usually don't have experience with Tests and they take some time to catch up and write them well.

So, the managing team had a meeting and came up with the idea of not requiring Instrumented Tests to validate UI anymore, only JVM tests. The idea behind it is that they have QAs who will write these automated tests (with Calabash and such).

Has anyone been in this situation? How did you show the value of Instrumented Tests written in Espresso on the same codebase to management?

Hey there,

I found this bug in Spotlight calculator running on MacOS Sierra that I consider really dangerous since there is no way of knowing the result is wrong unless you check it. If you use comma instead of dot to separate decimals or vice versa depending on your OS language, the result will be wrong.

Steps to reproduce:

1. Type 1 + 1.5 and check the result
2. Type 1 + 1,5 and check the result

The spotlight give different results (2.5 and 16). This is a dangerous behavior since it might lead the person to use the wrong result and cause all sorts of problem. I speak both Portuguese and English, I use both formats everyday. Next time you use the calculator on Spotlight keep that in mind

Even on high end devices with the latest processors and GPUs lack behind iOS when it comes to UI performance, specially animations and UI smoothness.

This is not a iOS vs Android rant. I feel like the UI thread has low priority, if anything else is happening on the phone frames are skipped. As a developer, I wanna bring in the discussion on what's the problem, limitations and how can I work around them to make my apps smoother/60 fps.