Search

You can now search through our archive !
Please specify a keyword

  • Issue #455

    Jetpack Compose Testing cheatsheet

    The Compose testing cheat sheet is a quick reference of some of the most useful Compose test APIs. The cheat sheet is also downloadable in PDF format.
  • Issue #455

    Unit Testing Kotlin Flow

    Nick Skelton has struggled unit testing Kotlin Flows attempting to apply LiveData or RxJava approaches. In this article, he then goes on to experiment with the Google recommended method and finally, showcases the best solution so far.
  • Issue #455

    turbine

    Turbine is a small testing library for kotlinx.coroutines Flow
  • Issue #455

    Friends App Android Client Ep4

    In this video, Jovche Mitrejchevski sets up the UI testing dependency and writes the first Compose UI test for this series.
  • Issue #454

    Android Engineer

    Help Fundrise bring the future of real estate investing to everyone! We're looking for talented Android Engineers to join our small but growing team to help us get to the next level. Do you have a passion for Kotlin, CI/CD, testing, and clean architecture? Send us your resume, we'd like to talk!
  • Issue #454

    Staff Android Engineer

    Join the team that delivers the member-facing experience for our core products - the bike & tread. This team works heavily with Kotlin - all within our custom fork of AOSP. We care about architecture, testing, and “together we go far” mentality. Staff engineers at Peloton are technical leaders
  • Issue #454

    First preview of Android 12

    Google has released the first Developer Preview of Android 12, the next version of Android, for your testing and feedback.
  • Issue #454

    Unit Testing as a 1st-class Citizen

    Testing can sometimes be seen as not adding value, or being too complicated. Rob Holmes tries to change those perceptions, to help you see why tests are just as important as the code itself!
  • Issue #453

    Staff Android Engineer

    Join the team that delivers the member-facing experience for our core products - the bike & tread. This team works heavily with Kotlin - all within our custom fork of AOSP. We care about architecture, testing, and “together we go far” mentality. Staff engineers at Peloton are technical leaders
  • Issue #451

    Migrating Your Design System to Jetpack Compose Part 3: Interop & Testing

    In this third article, Adam Bennett talks about how you actually integrate Jetpack Compose into an existing View-based app and how to test your freshly minted Composables.
  • Issue #451

    Expanding the reach of your Android Auto apps

    You can now reach more drivers by publishing navigation, parking, and charging apps to open testing tracks in the Google Play Store
  • Issue #451

    UI Testing with Kakao & Testing REST APIs Using MockWebServer

    UI tests are normally written using Android native testing framework which is Espresso but in this post, Caner Gulgec shows you how to write UI tests with Kakao and mock REST API responses.
  • Issue #449

    Senior React Native Engineer (Mobile)

    You will architect and grow new and existing codebases, give technical input and feedback to Axios’ product and design teams for new features, and help develop the skills of your teammates with industry best practices around testing, accessibility, and documentation.
  • Issue #448

    Senior React Native Engineer (Mobile)

    You will architect and grow new and existing codebases, give technical input and feedback to Axios’ product and design teams for new features, and help develop the skills of your teammates with industry best practices around testing, accessibility, and documentation.
  • Issue #448

    Using and testing Room Kotlin APIs

    Florina Muntenescu shows how to use and test Room Kotlin APIs and also how things work under the hood.
  • Issue #448

    Unit Tests and Concurrency

    Stojan Anastasov shows that when testing RxJava code, you do NOT have to replace all schedulers with Trampoline, which may make you miss possible concurrency issues.
  • Issue #447

    Practical network for Android Developers (part 5)

    In this final part of this series, Dinorah Tovar discusses mocking and testing and the way we can handle specific integrations of details with an HttpClient.
  • Issue #446

    New Year’s 20% OFF - Android App Perfection

    After a year like 2020, the last thing your end users want is a horrible app experience. Improve your Play Store ratings and innovate faster in 2021 with AI-powered visual, functional, and performance testing from Kobiton. Get 20% OFF any plan when you use code: ANDROIDWEEKLY before 12/31/2020.
  • Issue #445

    20% OFF on Android Testing - Improve UX for Less

    Quickly debug cloud and local devices without ever leaving your favorite IDE. Optimize code quality for Android 11 and previous OS versions with the flexibility and efficiency of the Kobiton cloud. Get 20% OFF any plan when you use code: ANDROIDWEEKLY before 12/31/2020.
  • Issue #445

    Opening the Google Play Store for more car apps

    Today, you can publish your apps to closed testing tracks in the Google Play Store. Google is also preparing the Play Store for open testing tracks soon.
  • Issue #443

    20% OFF on Android Testing - Tons of Real Devices

    Quickly scale real device testing in the cloud with full support for manual gestures, Espresso automation, ADB debugging, and more. Test on the latest Android and iOS devices, all in a highly responsive environment. Get 20% OFF any plan when you use code: ANDROIDWEEKLY before 12/31/2020.
  • Issue #443

    Testing Android Fragment in isolation

    Alex Zhukovich writes about testing fragments with local and instrumentation tests.
  • Issue #443

    Testing Never-Ending Flows

    Dan Lew shares a quick tip on unit testing never-ending Flows.
  • Issue #442

    Testing App Startup Performance

    Chet Haase wrote this article to explain more about performance, startup testing, and the reasons behind the pieces he used for testing startup.
  • Issue #442

    Integration testing with Dagger

    Using DI in our applications forces us to decouple the whole system into single-purpose components. Lukáš Sztefek shows how this approach leads to great testability.