Frictionless Android testing: Write once, run everywhere (Google I/O '18)

preview_player
Показать описание
There are many testing tools available for Android, and selecting the right tool can be confusing. This session will showcase the Android Testing Support Library (ATSL) — a new set of testing APIs that allow developers to write tests of all sizes across different execution environments. These new APIs will make testing easy, reducing the cognitive load for developers and keeping them in the zone while rapidly iterating.

#io18 event: Google I/O 2018; re_ty: Publish; product: Android - Jetpack; fullname: Jonathan Gerrish; event: Google I/O 2018;
Рекомендации по теме
Комментарии
Автор

Using such a generic name "Android Test" for a chronic problem's supposed solution does not help to locate it through Google . Could some one please put a direct link to this "Android Test" library /presence !

PronabPal
Автор

Where's the Documentation for this? The documentation provided in the slide doesn't contain these new information.

SaravanaThiyagarajs
Автор

Hi Google, today is 6th Feb 2019 and i'm extremaly waiting for io19. But i stil can't find nitrogen project docs and samples or smth like that :( please help me

alekseitiurin
Автор

Where is the "Android Test" library /dependencies / documentation /sample ?

PronabPal
Автор

where is Nitrogen? What should i use framework for unit, ui test? Google make me confuse again.. It is enough

mjstudio
Автор

I am devastated...where is the documentation. What's the status of this project?

nachokerupe
Автор

really surprised there wasn't more cheering around the 14:00 mark

wuziq
Автор

The nitrogen framework looks like Appium. Am I right? I'm very curious to use it on my android code.

thiagolopessilva
Автор

Can we get an update post on Project Nitrogen?

pnogas
Автор

I stared to like Google io more and more, off device tests, hell yeah

mootazltaief
Автор

Are there any Google samples on GitHub which showcase Robolectric?

igorg.
Автор

Hi Google Developers, Why confusing developers again with lot of frameworks? Espresso, AndroidX, RoboElectric, Mockito..keep on going...Why cant Google developers move all these things under a single framework and write testing simple? There is no proper documentation for how to test Views, how to write test for ViewModel, how to write test for LiveData? Saying AndroidX test, but still that also doing same...No use...

ramprasad