2. Instrumented Tests: <\/strong>These tests employ APIs from the Android framework to run on real or emulated Android devices to verify user behaviors like button clicks. Espresso & AndroidX Tests are frequently used for the same purpose.<\/p>\n\n\n\n 3. Unit Tests:<\/strong> Unit tests are crucial for ensuring that every operation and process in the application is tested. The most popular tools for unit testing are Hamcrest, Mockito, and JUnit.<\/p>\n\n\n\n Verifying the correctness of code is the primary goal of unit testing, which aims to fix issues early in the development cycle. This blog will explain Mockito and walk through how to use it for unit testing in Android applications.<\/p>\n\n\n\n Let\u2019s take a simple example of computations like addition, subtraction, etc to understand the Mockito framework.<\/p>\n\n\n\n We will create a file ComputationActivity.kt<\/em> to display all computations upfront. For managing all operations we will create object class Operations.kt which will be passed to ComputationActivity<\/em> class as a param in the primary constructor.<\/p>\n\n\n\n By default, module-name\/src\/test<\/em> will be having source files for local unit tests.<\/p>\n\n\n Now, we will add test functions in our ExampleUnitTest.kt <\/strong>file<\/p>\n\n\n\n Here, Operators is a object which has set of functions of calculator operations<\/p>\n\n\n and Calculator is a class,<\/p>\n\n\n Here, Calculator is mockito example that takes the operator object as a parameter in the primary constructor. So, we return operator function as return param for the functions in the Calculator class.<\/p>\n\n\n\n Inside the test folder, we will create a package called calculator same as we did in the java folder. Here, you can see we have not created OperatorsTest as we have to test only CalculatorTest here.<\/p>\n\n\n\n So, in Calculator Test,<\/p>\n\n\n Here, we have annotated with MockitoJUnitRunner::class <\/em><\/strong>that means it provides the Runner to run the test.<\/p>\n\n\n\n Now, we will setup the calculator class<\/p>\n\n\n Here, in construct we need to pass the operators. So, we won’t create an object of the operator as,<\/p>\n\n\n\n Also, @Before <\/strong>means, that even before performing the test we need to setup the dependency.<\/p>\n\n\n\n So, here we have to mock <\/strong>the operator like,<\/p>\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n In Mockito, we mock any class using @Mock <\/strong>annotation.<\/p>\n\n\n\n By Mocking any class, we are creating an mock object of that speicifc class. In the above code, Operators is mocked to provide dependency for Calculator class. Now, lets perform some test now,<\/p>\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n <\/p>\n\n\n\n Here, to perform tests we need to annotate the function with @Test.<\/strong><\/p>\n\n\n\n Now, we will create two variables, a and b with values 10,20 and then we will call,<\/p>\n\n\n\n calculator.addTwoNumbers(a, b)<\/strong><\/p>\n\n\n\n and to verify if the correct function was called or not from the mocked class, we will just use,<\/p>\n\n\n\n verify(operators).add(a, b)<\/strong><\/p>\n\n\n\n Here, verify means that you want to check if a certain method of a mock object has been called or not.<\/p>\n\n\n\n Now, to run the test we can click on the function like,<\/p>\n\n\n\n Now, to fail the case, just replace<\/p>\n\n\n\n verify(operators).subtract(a, b)<\/strong><\/p>\n\n\n\n Now, to run test on all the functions,<\/p>\n\n\n\n This blog discussed using Mockito for unit testing Android applications. Mocking is a potent tool for creating efficient Android unit tests. It enables you to independently verify the behavior of distinct code units, resulting in more dependable and manageable tests.<\/p>\n\n\n\n Because unit testing identifies defects early in the development process and makes refactoring and code modifications easier, Android applications need to be reliable, maintainable, and stable. If you also want to use Mockito development for Android unit testing, hire Android developers<\/a> with CMARIX.<\/p>\n","protected":false},"excerpt":{"rendered":" Unit testing for Android allows us to test a specific section of code to ensure that it meets our requirements. The code fragment is pushed to the repository to be combined with the current code if it passes. If it doesn’t work, the developers correct the problem and try again until it does. One of […]<\/p>\n","protected":false},"author":2,"featured_media":501,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,9],"tags":[],"class_list":["post-445","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mobile","category-android"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/posts\/445","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/comments?post=445"}],"version-history":[{"count":9,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/posts\/445\/revisions"}],"predecessor-version":[{"id":466,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/posts\/445\/revisions\/466"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/media\/501"}],"wp:attachment":[{"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/media?parent=445"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/categories?post=445"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cmarix.com\/qanda\/wp-json\/wp\/v2\/tags?post=445"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Steps: Unit Testing Using Mockito in Android
<\/h2>\n\n\n\nTo Add Mockito to Your Project (Using Android Studio and Gradle):<\/h2>\n\n\n\n
build.gradle.kts(app level)<\/strong>\ntestImplementation (\"junit:junit:4.13.2\")\ntestImplementation (\"org.mockito:mockito-core:2.25.0\")\ntestImplementation (\"org.mockito:mockito-inline:2.13.0\")\n\nbuild.gradle(app level) <\/strong>\ntestImplementation 'junit:junit:4.13.2'\ntestImplementation 'org.mockito:mockito-core:2.25.0'\ntestImplementation 'org.mockito:mockito-inline:2.13.0'<\/code><\/pre>\n\n\n\n\n
![\"Module](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/module-name-src-test.png\")
<\/figure>\n<\/div>\n\n\n\n
![\"set](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/set-of-functions-of-calculator-operations.png\")
<\/figure>\n<\/div>\n\n\n![\"Mockito](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/mockito-example.png\")
<\/figure>\n<\/div>\n\n\nLet’s Start Testing the Calculator Class,<\/h2>\n\n\n\n
In that, we will create only one class called CalculatorTest.kt.<\/p>\n\n\n![\"CalculatorTest](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/calculatortest-kt.png\")
<\/figure>\n<\/div>\n\n\n![\"Calculator](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/calculator-test.png\")
<\/figure>\n<\/div>\n\n\n![\"setup](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/setup-calculator-class.png\")
<\/figure>\n<\/div>\n\n\n\n
![\"mock\"](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/mock.png\")
<\/figure>\n<\/div>\n\n\n![\"creating](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/creating-an-mock-object.png\")
<\/figure>\n<\/div>\n\n\n![\"certain](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/certain-method-mock-object.png\")
<\/figure>\n\n\n\n![\"verify(operators)](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/verify-operators-subtract.png\")
<\/figure>\n\n\n\nimport com.app.mocktest.Calculator\nimport com.app.mocktest.Operators\nimport org.junit.Before\nimport org.junit.Test\nimport org.junit.runner.RunWith\nimport org.mockito.Mock\nimport org.mockito.Mockito.verify\nimport org.mockito.junit.MockitoJUnitRunner\n\n@RunWith(MockitoJUnitRunner::class)\nclass CalculatorTest {\n @Mock\n lateinit var operators: Operators\n\n lateinit var calculator: Calculator\n\n @Before\n fun onSetup() {\n calculator = Calculator(operators)\n }\n\n\n @Test\n fun givenValidInput_whenAdd_shouldCallAddOperator() {\n val a = 10\n val b = 20\n calculator.addTwoNumbers(a, b)\n verify(operators).add(a, b)\n\n }\n\n @Test\n fun givenValidInput_whenSubtract_shouldCallSubtractOperator() {\n val a = 10\n val b = 20\n calculator.subtractTwoNumbers(a, b)\n verify(operators).subtract(a, b)\n\n }\n @Test\n fun givenValidInput_whenMultiply_shouldCallMultiplyOperator() {\n val a = 10\n val b = 20\n calculator.multiplyTwoNumbers(a, b)\n verify(operators).multiply(a, b)\n\n }\n @Test\n fun givenValidInput_whenDivide_shouldCallDivideOperator() {\n val a = 10\n val b = 20\n calculator.divideTwoNumbers(a, b)\n verify(operators).divide(a, b)\n\n }\n}\n<\/code><\/pre>\n\n\n\n![\"run](\"https:\/\/www.cmarix.com\/qanda\/wp-content\/uploads\/2024\/06\/run-test-on-all-the-functions.png\")
<\/figure>\n\n\n\nConclusion<\/h2>\n\n\n\n