Android-Testing

Project under the "Engineering Maintainable Android Apps" course on Coursera.

Installation

• Clone this repository.
• Open it in Android-studio and sync the project.

The requirement was to write unit tests and UI tests using Espresso for the following requirements

• The LoginActivity must have a place for the user to enter their email address
• The LoginActivity must have a place for the user to enter their password
• The LoginActivity must not display the password in plain text
• The LoginActivity must have a login button that displays the text "Login"
• The LoginActivity must have a way to display an error message to the user
• When the login button is clicked, the activity should check that the password is at least 8 characters long and display the error message "The provided password is too short" if the password is too short
• When the login button is clicked, the activity should check that the password is not all spaces and display the error message "The provided password is invalid" if the password is all spaces
• When the login button is clicked, the activity should check that the email address: a) has an "@" sign, b) has at least 1 character before the "@" sign, and c) has at least 3 characters, including a "." after the "@" sign
• If any of the rules from #8 are violated, the LoginActivity should display the error messagefgfg "Invalid email address"
• The LoginActivity must have a way to display a success message (can be the same mechanism used to display the error message)
• If the email address and password are valid, the success message "Login success" should be displayed
• You must have Espresso tests demonstrating the UI requirements
• Where possible, you must have JUnit tests to test aspects of the app that do not require integration with Android (hint: password checking rules)
• You must have JUnit tests demonstrating all non-UI requirements.
• Optional: You are not required to implement a test to show that the password is not displayed as plain text, but you can add this test as an additional challenge
• You must create a README.md file that lists requirements 1-11 and the fully qualified class name of the tests that are used to verify each requirement
• To demonstrate that all requirements are covered, the test methods that check a given requirement should have a method-level comment indicating the requirements being tested, as shown below:

Screenshots