Great work. AndroidX Test is as exciting as when I saw the beautiful espresso API. It makes very good sense. Regarding the criticism on presentation skills, I find no problem with the presentation, except for the accent. However, software development is truly global and we should probably get used to different accents. I appreciate the courage of this developer to give out a talk to global audience in spite of his difficulties in English. Pretty sure he is working very hard on his English and Presentation Skills.
Testing code should be simpler to write then coding the system under test. The aligning and streamlining of different testing apis is necessary to make TDD common practice in android development. I am excited to work with AndroidX and hope to see more code labs and samples on how to better use all the frameworks together. P.S. I'm sure his next talk will be even better.
Google has to give presentations to people that are good at presenting. I admire a lot the development work that all Google engineers do, but not all engineers are good to make public presentations, and the whole point of presentations are teaching. If someone is not good at presenting the teaching goal is not well achieved. I don't want to disrespect anyone, by no means, but I do think that Google should evaluate better who's prepared to go on stage and give a nice, understandable, engaging talk, and who's not. Different people have different skills and there's nothing wrong with that.
Great work. AndroidX Test is as exciting as when I saw the beautiful espresso API. It makes very good sense.
Regarding the criticism on presentation skills, I find no problem with the presentation, except for the accent. However, software development is truly global and we should probably get used to different accents. I appreciate the courage of this developer to give out a talk to global audience in spite of his difficulties in English. Pretty sure he is working very hard on his English and Presentation Skills.
Testing code should be simpler to write then coding the system under test. The aligning and streamlining of different testing apis is necessary to make TDD common practice in android development. I am excited to work with AndroidX and hope to see more code labs and samples on how to better use all the frameworks together.
P.S. I'm sure his next talk will be even better.
Should have watched this yesterday...
I guess I am still unsure about how to reuse the same test between instrumentation test and unit test. An example would be nice.
hi there I just want to say thank you guys and for all your comments
What should I use for mocking?
12:40 subtitles o:
How about Huawey testing
Google has to give presentations to people that are good at presenting. I admire a lot the development work that all Google engineers do, but not all engineers are good to make public presentations, and the whole point of presentations are teaching. If someone is not good at presenting the teaching goal is not well achieved.
I don't want to disrespect anyone, by no means, but I do think that Google should evaluate better who's prepared to go on stage and give a nice, understandable, engaging talk, and who's not. Different people have different skills and there's nothing wrong with that.
Those who are good at giving talks began somewhere. Another solution would be to review their talk and give them mentoring before their presentation.
that why they have a subtitle
MFeinsteinkshannmugavel
MFeinstein kshanmugavel
@@RainySeasonMemory and that is why they have 'inaudible' and question marks in subtitles as well 😂
sorry about that I'm just trying to
get to know better