{"id":699,"date":"2020-01-29T20:20:41","date_gmt":"2020-01-29T19:20:41","guid":{"rendered":"http:\/\/blog.ansuz.nl\/?p=699"},"modified":"2020-01-29T20:20:42","modified_gmt":"2020-01-29T19:20:42","slug":"cucumber-android","status":"publish","type":"post","link":"http:\/\/blog.ansuz.nl\/index.php\/2020\/01\/29\/cucumber-android\/","title":{"rendered":"Cucumber & Android"},"content":{"rendered":"\n

A while ago, the agile\/scrum team I was part of was looking for a way to record functional requirements for the app we were working on. After looking around for a bit, we came across Behaviour-Driven Development<\/a> (BDD) and Cucumber<\/a>.<\/p>\n\n\n\n

Although documentation and automated tests are produced by a BDD team, you can think of them as nice side-effects. The real goal is valuable, working software, and the fastest way to get there is through conversations between the people who are involved in imagining and delivering that software. <\/p>Cucumber.io on BDD<\/a>

<\/cite><\/blockquote>\n\n\n\n

Since we wanted to test the Android and iOS using the same Gherkin scenarios, we set up Cucumber together with Appium<\/a>. Personally I find working with Appium too cumbersome. In a private project I’ve therefore set up Cucumber with Android and left Appium out of the equation.<\/p>\n\n\n\n

In this article I’ll explain how to set up Cucumber for Android.<\/p>\n\n\n\n

Set up cucumber-android<\/h2>\n\n\n\n

Add the “cucumber-android<\/a>” library to your project:<\/p>\n\n\n\n

androidTestImplementation \"io.cucumber:cucumber-android:$cucumberVersion\"<\/code><\/pre>\n\n\n\n
Custom TestRunner<\/h2>\n\n\n\n
To configure Cucumber we’ll create a custom “TestRunner<\/em>‘:<\/p>\n\n\n\n
private const val PLUGIN_KEY = \"plugin\"\nprivate const val REPORTS_DIR = \"reports\/cucumber\"\n\nprivate const val REPORTER_PLUGIN_PATTERN =\n    \"junit:%s\/cucumber-junit.xml--\" +\n    \"html:%s\/cucumber-html--\" +\n    \"json:%s\/cucumber.json\"\n\n\/**\n * The CucumberOptions annotation is mandatory for exactly one of the classes in the test project.\n * Creating a custom test Runner seems the simplest way to achieve that.\n *\/\n@CucumberOptions(\n    features = [\"cucumber\/features\"],\n    glue = [\"nl.ansuz.android.test\"]\n)\nclass CucumberRunner : CucumberAndroidJUnitRunner() {\n\n    override fun onCreate(bundle: Bundle?) {\n        bundle?.putString(PLUGIN_KEY, getPluginConfiguration())\n        super.onCreate(bundle)\n    }\n\n    private fun getPluginConfiguration(): String {\n        val path = getReportsPath()\n        return REPORTER_PLUGIN_PATTERN.format(path, path, path)\n    }\n\n    private fun getReportsPath(): String =\n        File(targetContext.getExternalFilesDir(null), REPORTS_DIR).absolutePath\n}<\/code><\/pre>\n\n\n\n
Permissions<\/h2>\n\n\n\n
To make reporting work, we need to give our app permission to write to the external storage. Since Cucumber will run under the “androidTest<\/em>”  flavor, you can add the extra permissions in “src\/androidTest\/AndroidManifest.xml<\/em>” to avoid polluting your production app with unnecessary permissions.<\/p>\n\n\n\n
<uses-permission android:name=\"android.permission.WRITE_EXTERNAL_STORAGE\" \/><\/code><\/pre>\n\n\n\n
Now Cucumber can save test reports on the external storage.<\/p>\n\n\n\n
Writing Gherkin<\/h2>\n\n\n\n
The next step is to write some scenarios so there is something for Cucumber to test.  
The cucumber.io<\/a> website comes with plenty of examples, so I’ll leave this as an exercise for the reader.<\/p>\n\n\n\n
Note:<\/em><\/strong> The “cucumber-android” plugin expects all feature files to be created under “app\/src\/androidTest\/assets<\/em>“. You can tweak the base path by changing the “features” property of the “CucumberOptions<\/em>” annotation in the custom “TestRunner<\/em>” we created earlier.<\/p>\n\n\n\n
Running tests<\/h2>\n\n\n\n
Now that everything is set up and we have a first test, we can run it. Because of the custom test runner, I had to create a Gradle task that will run instrumentation tests with it.<\/p>\n\n\n\n
task runCucumberInstrumentationTests(type: Exec) {\n     description 'Runs instrumentation tests with Cucumber'\n     group 'verification'\n     dependsOn 'installDebug', 'installDebugAndroidTest'\n     commandLine 'adb', 'shell', 'am', 'instrument', '-w', 'nl.ansuz.android.test\/nl.ansuz.android.test.CucumberRunner'\n }<\/code><\/pre>\n\n\n\n
When you run this new task, no tests pass, but the Cucumber reports are generated anyway. To make the tests pass,we have to create some “glue”.<\/p>\n\n\n\n
Writing the glue<\/h2>\n\n\n\n
In the custom “TestRunner<\/em>” we’ve also defined where the “cucumber-android<\/em>” library can find the “glue” to match scenarios with step definitions.<\/p>\n\n\n\n
The easiest way to write your step definitions is to annotate the appropriate methods in your Espresso<\/a> tests with Cucumber annotations, e.g.<\/p>\n\n\n\n
@When(\"the Maker starts a game\")\nfun startGame() {\n  ...\n}<\/code><\/pre>\n\n\n\n
Pulling Cucumber reports<\/h2>\n\n\n\n
Now that you have written some tests, can run them and they pass, you want to be able to have a look at the Cucumber report(s) as well. Pulling the reports is fairly simple, all we need to do is add a Gradle task that uses “adb pull<\/em>” to do this for us.<\/p>\n\n\n\n
task pullCucumberReports(type: Exec) {\n    description 'Pulls the Cucumber reports from the emulator.'\n    group 'verification'\n    dependsOn 'runCucumberInstrumentationTests'\n\n    workingDir buildDir\n    commandLine 'mkdir', '-p', 'reports'\n    commandLine 'adb', 'pull', '\/mnt\/sdcard\/Android\/data\/nl.ansuz.android\/files\/reports\/cucumber', 'reports'\n}<\/code><\/pre>\n\n\n\n
The reports path is set in the “REPORTS_DIR<\/em>” constant in the custom “TestRunner<\/em>” from earlier. Make sure that the paths in the test runner and the Gradle task match.<\/p>\n\n\n\n
Cleaning up<\/h2>\n\n\n\n
So far we are able to run Cucumber tests and pull the reports from the device. What is missing is a way to clean up after testing has finished. Again we’ll add a new Gradle task to do this for us.<\/p>\n\n\n\n
task uninstallCucumberTest() {\n    description 'Uninstalls the debug and debugAndroidTest apps.'\n    group 'install'\n    dependsOn 'uninstallDebug', 'uninstallDebugAndroidTest'\n}<\/code><\/pre>\n\n\n\n
Tying it all together<\/h2>\n\n\n\n
Because we are good developers and we are lazy, we don’t want to execute three different Gradle tasks to run tests, pull reports and clean up. Let’s introduce one last Gradle task to make our lives even easier.<\/p>\n\n\n\n
task cucumberCheck() {\n    description 'Installs regular and instrumentation apps, runs Cucumber tests, pulls reports ' +\n            'and then uninstall both apps.'\n    group 'verification'\n    dependsOn 'pullCucumberReports'\n}\n\ncucumberCheck.finalizedBy uninstallCucumberTest<\/code><\/pre>\n\n\n\n
I hope this helps you to get you started on using BDD for your Android project with Cucumber.<\/p>\n\n\n\n
Bonus: IntelliJ \/ Android Studio plugins<\/h2>\n\n\n\n
To make working with Cucumber and Gherkin easier, you can install the following plugins for IntelliJ or Android Studio:<\/p>\n\n\n\n