kaushikgopal/movies-usf-android

feat: add a single ui instrumentation test

Open

#2 opened on Sep 24, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Kotlin (44 forks)github user discovery
help wanted

Repository metrics

Stars
 (229 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The view state tests are the more interesting ones imho, but for this to be fully "complete", we'd definitely need UI instrumentation tests to make sure:

  1. the output "view state" is being bound properly to our Android Views
  2. the android views are generating the correct input "events"

A single espresso tests should suffice for that.

Contributor guide

Research direction
Create an Espresso UI test in the Android test directory. Launch the main activity, simulate a search query, and verify that the UI updates correctly. Follow the repository's existing test patterns if available.
Tech stack
kotlin
Domain
mobile dev
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
AndroidKotlinEspressoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70