hello, Ivano!

how can I help you today?

HI Mark, do not have any precise question

I am improving a lot, now that I have been working as developer

let me think

please

yeah. I am moving my first steps in TDD, and found your tutorial on adding a shot of Espresso nice.(after all I am Italian). But I had on Thursday a discussion about how important is TDD and how is difficult to test android components, if one does not have a port/adapter/solid/onion/super architecture(that my team does not want to implement). Roboelectric is not the right solution because it tests things via "shadows" and not mocking the real SUT thing. A guy told me that I should look into the "new Espresso" ???

I am not certain what the "new Espresso" would be referring to

is a kind of androidX last version of espresso

that could allow TDD

but I do not get it, nor I asked him for silly proud

personally, I find GUI testing in Android to be frustrating, with or without Espresso

me too, the delays and the things

I tend to focus on getting as much code out of the activities and fragments as possible, then testing from the viewmodel layer back into deeper layers of the app

but for TDD could be useful

the problem is that my team put even area 51 in the viewModel

so they do not like onion approach nor the inversion dependency via interfaces, or modules

ah

then, yes, testing will be a problem

ahah

never mind, I am learning a lot, if you run bad then you can walk good

I am gonna study more the topic

i just saw you have nice tutorials on delegates and by

going back to your Robolectric comment, I agree and try to minimize my use of it -- I would rather have a slower-running instrumented test that really tests on Android

wow

I see

after all was made by google engineers

but, the projects I tend to work on are not huge

I know that

I think Google hired the developers somewhere along the line -- if I recall correctly, it started as an independent project

everyone is more CI oriented, and I found this TDD growing object book fantastic

eheh this justifies the lenght of View.java :troll

overall, we are trying to do a better job with testing and testability in Android app development, but it is a slow process

and, to paraphrase William Gibson, "the future is here; it is not evenly distributed"

so there are some teams that are way out in front with sophisticated architectures designed for testability

so true

and there is a "long tail" of projects that are just trying to survive and be effective

you becoming robin martin/fowler

:)

eh, I am just trying to help the people in that long tail

techinical debt is killing millions

ahah

I am afraid that with the exponential need for developers, that will be junior per definition the long tail is far to go away

wish you a nice evening, and would stop here so that can benefit from your help when I am in really specific situations

ops sorry for the evening

was forgetting

it is almost evening here :-)

have a nice day

you too!

:thumb up