Giter Site home page Giter Site logo

Comments (6)

peter-tackage avatar peter-tackage commented on May 5, 2024

Agreed @Brave-Warrior. This has been on my backlog for a while as the landscape has certainly changed since the initial version of this document.

from android-best-practices.

peter-tackage avatar peter-tackage commented on May 5, 2024

As a brief summary of my thoughts how to write tests:

  • Minimize explicit Android dependencies in your code through abstraction and separation of concerns. Android dependencies require you to use instrumentation tests, which are considerably slower than strictly Java (JVM) based tests.
  • Start with unit tests, driven by JUnit4.
  • Use Mockito for mock definitions
  • Use descriptive names for the unit test to aid in defining expected behavior.
  • Use good test structure: Arrange, Act, Assert.
  • Separate arrangement definitions into an "arrange builder" to improve test readability.
  • Use AssertJ for assertions.
  • Add integration and UI tests once their business value is justified.
  • Use PowerMock for mocking statics and final classes as a last resort.
  • Be aware that pure Java unit testing has its limits, and that writing specific Android tests still remains important in some cases - for example; database handling.

@tomaszpolanski might have some input here too.

from android-best-practices.

tomaszpolanski avatar tomaszpolanski commented on May 5, 2024

When using Rx and "scheduled" observable, either inject schedulers or something that provides them.
Then in test you can use TestScheduler to test timer related functionality.

from android-best-practices.

dkhmelenko avatar dkhmelenko commented on May 5, 2024

@peter-tackage agree with your points. But would extend the following items with the links to appropriate resources or detailed description:

  • Use Mockito for mock definitions

add link for Mockito; the recommendations how to mock objects and the check behaviour in the better/best way

  • Use AssertJ for assertions.

Link to AssertJ would be good and what are the advantages of that

  • Add integration and UI tests once their business value is justified.

not clear enough

The other points are quite clear and could be added to the best practices.

from android-best-practices.

peter-tackage avatar peter-tackage commented on May 5, 2024

@tomaszpolanski Agreed. Testing Rx is probably worth it's own section.

from android-best-practices.

peter-tackage avatar peter-tackage commented on May 5, 2024

@Brave-Warrior I'll be progressing the testing section update under #114

from android-best-practices.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.