Testing is always a good way to discover errors in the UI, backend code, or logic. It helps to understand the reason for crashes. Here, we have learned about two powerful frameworks. One is JUnit and another is Espresso. In this chapter, we have seen how to add the dependencies for testing. We have learned how to implement the JUnit into a project. We saw how to use the logic in our test case and how to check to see the pass or fail result of a test case. Additionally, we have seen how to connect the database for testing. Then, we saw how to insert a demo object into a database, and subsequently, fetch it from the database, after which we have matched the object.

In Android testing, we have used the Espresso framework to test the UI. Finally, we have seen some uses of the Espresso APIs and how to handle and connect them with a specific activity. This chapter gave you a brief idea of testing so that you can use test cases to perfect your project. If you want to learn more, please see our reference book under the Further reading section.

If you are reading this paragraph, that means you have finished this book and are ready to build a server-based and client-based projects alone. Now you are a one-man army, able to create a server and mobile application with security, databases, and testing. I hope you enjoyed reading this book and that it will be a reference point in your upcoming projects.