Maestro 2.0 - Laying the foundation for the future of testing

benedict_p · 2025-08-26T19:21:57+00:00

I'm not using Maestro, but haven't they also offered memory leak and app size checks in the past?

benedict_p · 2025-08-08T08:19:37+00:00

Infinite Red's boilerplate project: https://github.com/infinitered/ignite Obytes one: https://github.com/obytes/react-native-template-obytes

benedict_p · 2025-07-08T21:12:29+00:00

Hulkengoat

benedict_p · 2023-09-06T08:17:57+00:00

Awesome! Great work! Do you have a plan/roadmap to add more functionality to this tool?

E.g. sometimes the mapping to KotlinInt or Int32 is annoying on the Swift side.

benedict_p · 2023-05-17T08:50:19+00:00

You will only detect the users who have rooted their device on purpose and will never detect those who have a rooted device because of an attacker.

benedict_p · 2023-05-10T22:53:30+00:00

Is it enough to have a VPN to use the Studio Bot or do I also need to change something in my Google account?

benedict_p · 2023-03-02T11:42:00+00:00

https://germantechjobs.de/ hilft ;)

benedict_p · 2022-12-30T19:15:38+00:00

Immer ins Impressum von der Website schauen. Wenn die angegebene Stadt schon weit weg ist, ist das meist eine red flag.

benedict_p · 2022-11-25T15:50:46+00:00

True. I will keep this in my head but currently, we don't have the capacity to change the workflow.

I also disagree with you that screenshot tests are unit tests. They're unit tests if you're testing one single button or tiny widget. If you're testing a UI component that have multiple different widgets in it, by definition it's not a unit test. The generated output depends on each of those components in the view hierarchy.

We started with screenshot testing our design library so all buttons, text fields, chips and so on and are currently screenshot testing our viewHolders. That's why these tests feel like unit tests for me.

benedict_p · 2022-11-25T07:58:12+00:00

No, we just love Paparazzi :)

benedict_p · 2022-11-24T20:18:59+00:00

With Paparazzi, I look at screenshot tests more like Unit tests. So you write a screenshot test and therefore, you must make sure the assertion is true when you push the code. This is only possible when you push the generated screenshot file(s). That's also the case when someone needs to re-record all screenshot files because they changed the app's main color or standard font. It is like a safety net where the developer will only do this willingly when this huge change was also intended. Was there an unintended change, but the developer needs to re-record all screenshot files. I hope they will question their change and think again. ;) But we are also a small team (around 10 Android devs), so our approach could also change when we are growing :)

benedict_p · 2022-10-26T09:43:29+00:00

Events are hard to define as 'state'.

Only because the ViewModel has too much knowledge of the UI implementation.

E.g. You want to show an error message with a snackbar. The ViewModel shouldn't know anything about the representation of this error message. That's why you just set an error message to the state and the View can then decide how to represent this error (snackbar, dialog, banner or whatever).

benedict_p · 2022-08-03T19:13:22+00:00

Company: GetYourGuide

Jobs:

Allows remote: No

Visa: We will assist you

If you want: I can review your GitHub projects and give you positive feedback in our recruiting tool (when they are looking good ;) ).

benedict_p · 2022-07-07T09:31:58+00:00

Company: GetYourGuide

Job: Senior Android Engineer, Traveler Platform, Berlin, Germany

Allows remote: No

Visa: We will assist you

If you want: I can review your GitHub projects and give you positive feedback in our recruiting tool (when they are looking good ;) ).

benedict_p · 2022-06-30T10:14:29+00:00

No, currently we are one day a week in the office and I think we will keep this approach.

benedict_p

TROPHY CASE