Screenshot Kata for Android Developers with Kotlin. The main goal is to practice UI Screenshot Testing.
You can compare this testing approach with a different testing strategy where the application UI is tested using just Espresso.
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 it is part of the Avengers Team.SuperHeroDetailActivity
showing detailed information about a super hero like his or her name, photo and description.The application architecture, dependencies and configuration is ready to just start writing tests. In this project you'll find Kodein
configured to be able to replace production code with test doubles easily and Espresso to be able to interact with the application user interface and a screenshot testing framework ready to compare your application changes.
Remember that after any production code change you can record your screenshots again executing:
./gradlew executeScreenshotTests -Precord
To verify the correct behaviour of your code you can execute:
./gradlew executeScreenshotTests
To be able to get a deterministic test scenario all our tests will be executed on the same emulated device. You can use the Travis-CI configuration to get the same emulator working on your computer.
Your task as Android Developer is to write all the UI tests needed to check if the Application UI is working as expected.
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
kata-screenshot
branch.MainActivityTest
and watch the only test it contains pass.To help you get started, these are some test cases for MainActivity
:
SuperHeroRepository
in MainActivityTest
to return a list of some Super Heroes.MainActivity
is showing the super heroes obtained from the SuperHeroesRepository
.master
branch contains already solved tests for MainActivity
, SuperHeroDetailActivity
and SuperHeroViewHolder
.If you've covered all the application functionality using UI tests try to continue with the following tasks:
MainActivity
and test it.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.SnackBar
to indicate something went wrong.SuperHeroesRepository
test double to perform a Thread.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:
Data provided by Marvel. © 2017 MARVEL
Copyright 2017 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.