I'd like to use Behavior Driven Development (BDD) to develop an Android app. I'm thinking of using jBehave with Robolectric. Someone wrote about using jBehave with Robotium but does anyone know if Robolectric can be used instead of Robotium with jBehave?
Any known issues?
Robotium is a tool for unit/acceptance testing on emulator or real device, Robolectric is library to unit test android code on desktop jvm. I think it would be possible to pair jBehave with Robolectric but again as for me it would be something that doesn't fit well.
As example simple behaviour test on android:
Activity A with list, user press item at position 2, user see Activity B details
for for the second object in the list.
Test on Robotium will:
press on activity A list item
check that activity B shown with UI that represents details
Tests with Robolectric are smaller:
you could check that pressing item on A will fire Intent for launching new activity with specified details
another test would check that B will show details
So you could try with jBehave map "see item details" to Robolectric “Intent fired” but this check is misleading because there so many things could happen from firing Intent to showing Activity with details.
You could in Robolectric also try to fire activity and check details but this level of mocking is too much for BDD which suppose to have as less mocking as possible.
Related
Q. How to capture screenshots while writing the UI test cases in android studio using espresso tool, kotlin language and robolectric test cases using act, arrange and assert
For mobile android application -
1. I am writing the test cases using android studio, kotlin language and robolectric form- act, arrange and assert android UI Test cases.
Running test cases on - emulator, real device
In act- login the app
In arrange - Go to specific screen and perform click function
In assert- validating the UI with specific fields and column text fields and value.
I want to capture the screenshots in between where the assert commands failed or code exit with an error. I was new to kotlin but now learnt how to write the code, need help in how to capture the screenshot in this case.
I had searched helping code on google and try out to find some hint but didn't get much to understand.
Below is the code -
#Test
fun loginSuccess() {
// arrange
// act
onView(withId(R.id.login)).perform(click())
// assert
onView(withId(R.id.logoImg)).check(matches(isDisplayed()))
}
You can refer to this article. There is not a single method which handles everything for you.https://medium.com/#mohitgupta92/custom-failure-handler-for-android-espresso-c8c99eb65a32
I have a farm of about 20 android devices to run instrumentation UI tests. I use Espresso. Sometimes different system dialogs appear and lead tests to fail.
E.g. USSD result dialog, dialog of lost internet connection, dialog of request to update OS and etc.
Is there a way to catch any dialog and close the one?
This intent doesn't help.
Intent.ACTION_CLOSE_SYSTEM_DIALOGS
it’s simple to click back button event
onView(isRoot()).perform(ViewActions.pressBack());
Add this to your gradle:
androidTestCompile 'com.android.support.test.uiautomator:uiautomator-v18:2.1.2'
And then do this in your test:
UiDevice mDevice = UiDevice.getInstance(InstrumentationRegistry.getInstrumentation());
mDevice.pressBack();
and if you like more in Espresso UI testing, View Expresso Demo Project on GitHub: https://github.com/ranaNarin/Espresso-Android
In this demo project, implemented espresso in all Scenarios:- EditText, Button, options menu click, navigation drawer Open and close, click on recycler view item, open camera and click image using Espresso UI Testing
I've been researching this. The popups have an id and can be dismissed using the test framework. So far I've found how to do it using appium and there is another GitHub that has to this using instrumentation but I haven't implemented this yet.
https://github.com/jamesknowsbest/aws-device-farm-sample-app-for-android
onView(withId(R.id.BUTTON))
.perform(click())
.check(matches(withContentDescription(R.id.my_layout)));
onView(withId(R.id.tp_layout))
.check(matches(isDisplayed()));
I am trying to test whether button click migrates to next screen or not..
how can I match, with this only first test is running and it displays tests failed.
You can use an Espresso extension - Espresso-Intents.
Here is the official tutorial.
Quick quote:
Espresso-Intents is an extension to Espresso, which enables validation
and stubbing of intents sent out by the application under test. It’s
like Mockito, but for Android Intents.
If your app delegates functionality to other apps or the platform, you
can use Espresso-Intents to focus on your own app's logic while
assuming that other apps or the platform will function correctly. With
Espresso-Intents, you can match and validate your outgoing intents or
even provide stub responses in place of actual intent responses.
I have a scenario to test:
In my app, click a button - say, btn1.
btn1 click uses an intent action=VIEW, uri=http://www.m10v.com, category=DEFAULT to launch another activity. This activity belongs to another package (e.g.: browser)
How do I:
Ensure that an application with an activity this intent filter is installed?
How do I test that the activity actually started?
Robolectric should be used for unit testing your code. It stubs out the android runtime, allowing for a fast test/refactor cycle. Tests run on the JVM and not on an emulator or device. Therefore you cannot use it for interacting with other components in the system.
For your scenario there are two options:
Write a unit test and only verify interactions, i.e. checking Intent attributes. You can use Robolectric or ActivityUnitTestCase for that.
Write a functional Ui test using the UiAutomator Framework (Api 16) or use the new UIAutomation Apis introduced with Api 18.
I'm developing Activity which works on data passed in Intent in extras.
This Activity is supposed to be launched by other activities in my app.
However, during development/debugging, I launch this Activity directly, and want to simulate extras in Intent (obtained from getIntent) to pass in desired testing params (sort of command-line parameters).
In Eclipse Run configurations, I can just select Launch action, but no additional data.
Is there some way? Or I must hardcode testing params in java, and not forget to comment them out when testing is finished?
I think eclipse is just using something comparable to the am start method to launch an application. You should be able to do this manually via adb and specify extras; then once you have it working from the command line you can put it behind a button using eclipse's extensibility features.
Here's a writeup found during a brief search: http://learnandroid.blogspot.com/2008/01/run-android-application-from-command.html
I think you may want to just write some proper tests for this purpose.
Take a look at this:
Android Testing fundamentals
You could then be running your test during development, which would launch the Activity as you want it.