- We are here to practice UI Testing.
- We are going to use Espresso to interact with the Application UI.
- We are going to use Dagger2 to replace production code with Test Doubles.
- We are going to practice pair programming.
This repository contains an Android application to show Super Heroes information:
This Application is based on two Activities:
MainActivity
showing a list of super heroes with name, photo and a special badge if is part of the Avengers Team.
SuperHeroDetailActivity
showing detailed information for a super hero like the name, photo and description.
The application architecture, dependencies and configuration is ready to just start writing tests. In this project you'll find Dagger2
configured to be able to replace production code with test doubles easily and Espresso to be able to interact with the application user interface.
Your task as Android Developer is to write all the UI tests needed to check if the Application UI is working as it should.
This repository is ready to build the application, pass the checkstyle and your tests in Travis-CI environments.
Our recommendation for this exercise is:
-
Before starting
- Fork this repository.
- Checkout
kata-super-heroes
branch. - Execute the application, explore it manually and make yourself familiar with the code.
- Execute
MainActivityTest
and watch the only test it contains pass.
-
To help you get started, these are some test cases for
MainActivity
:- Setup mocked
SuperHeroesRepository
inMainActivityTest
to return a list of some Super Heroes. - Test that RecyclerView is listing the correct number of elements when
SuperHeroesRepository
returns a list of some Super Heroes. - Test that each of this elements contains the correct Super Hero name.
- Setup mocked
-
If you get stuck,
Master
branch contains already solved tests forMainActivity
andSuperHeroDetailActivity
-
A DaggerMockRule is an utility to let you create Dagger 2 modules dynamically. In this case we are using it to create a new
MainModule
in this testing scope. Instead of returning real objects, this newMainModule
will returns the mock forSuperHeroesRepository
defined in this test. -
You will find some utilities to help you test RecyclerViews and Toolbars easily in:
app/src/androidTest/java/com/karumi/katasuperheroes/matchers
andapp/src/androidTest/java/com/karumi/katasuperheroes/recyclerview
.-
RecyclerViewInteraction
: provides an easy way to apply an Espresso matcher to all of the RecyclerView elementsRecyclerViewInteraction.onRecyclerView(withId(R.id.recycler_view)) .withItems(A_LIST_OF_ITEMS) .check(new RecyclerViewInteraction.ItemViewAssertion() { @Override public void check(SuperHero item, View view, NoMatchingViewException e) { matches(A_MATCHER).check(view, e); } });
-
RecyclerViewItemsCountMatcher
: a matcher that returns true if RecyclerView contains the expected number of elements. -
ToolbarMatcher
: a matcher that returns true if a Toolbar with expected title is found.
-
If you've covered all the application functionality using UI tests try to continue with the following tasks:
- Add a pull to refresh mechanism to
MainActivity
and test it. - Modify
SuperHeroDetailActivity
to handle an error case where the name of the super hero used to start this activity does not exist and show a message if this happens. - Modify the project to handle connection errors and show a
SnackBar
to indicate something went wrong. - Modify
SuperHeroesRepository
test double to perform aThread.sleep
and use the custom idling resources you'll find in this repository to get your tests working.
There are some links which can be useful to finish these tasks:
- Android Testing Support Library official documentation
- Espresso Cheat Sheet
- Espresso Idling Resources
- Espresso Custom Matchers
- Finding UI views
- Espresso Test Toolbar Title
Data provided by Marvel. © 2016 MARVEL
#License
Copyright 2016 Karumi
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.