ExamGecko
Login
Home / Google / Associate Android Developer / List of questions
Ask Question

Google Associate Android Developer Practice Test - Questions Answers, Page 3

Add to Whishlist

List of questions

Question 21

Report Export Collapse

To automate UI tests with Android Studio, you implement your test code in a separate Android test folder. Folder could be named:

app/androidTest/java
app/androidTest/java
app/src/androidTest/java
app/src/androidTest/java
app/java/androidTest
app/java/androidTest
Suggested answer: B
asked 18/09/2024
Sharanjit Kareer
46 questions

Question 22

Report Export Collapse

Once your test has obtained a UiObject object, you can call the methods in the UiObject class to perform user interactions on the UI component represented by that object. You can specify such actions as: (Choose four.)

click() : Clicks the center of the visible bounds of the UI element.
click() : Clicks the center of the visible bounds of the UI element.
touch() : Touch the center of the visible bounds of the UI element.
touch() : Touch the center of the visible bounds of the UI element.
dragTo() : Drags this object to arbitrary coordinates.
dragTo() : Drags this object to arbitrary coordinates.
moveTo() : Move this object to arbitrary coordinates.
moveTo() : Move this object to arbitrary coordinates.
setText() : Sets the text in an editable field, after clearing the field's content. Conversely, the clearTextField() method clears the existing text in an editable field.
setText() : Sets the text in an editable field, after clearing the field's content. Conversely, the clearTextField() method clears the existing text in an editable field.
swipeUp() : Performs the swipe up action on the UiObject. Similarly, the swipeDown(), swipeLeft(), and swipeRight() methods perform corresponding actions.
swipeUp() : Performs the swipe up action on the UiObject. Similarly, the swipeDown(), swipeLeft(), and swipeRight() methods perform corresponding actions.
Suggested answer: A, C, E, F
asked 18/09/2024
Pranoy Bej
39 questions

Question 23

Report Export Collapse

If you want to access a specific UI component in an app, use the UiSelector class. This class represents a query for specific elements in the currently displayed UI. What is correct about it? (Choose two.)

If more than one matching element is found, the first matching element in the layout hierarchy is returned as the target UiObject.
If more than one matching element is found, the first matching element in the layout hierarchy is returned as the target UiObject.
If no matching UI element is found, an IOException is thrown.
If no matching UI element is found, an IOException is thrown.
If more than one matching element is found, the last matching element in the layout hierarchy is returned as the target UiObject.
If more than one matching element is found, the last matching element in the layout hierarchy is returned as the target UiObject.
If no matching UI element is found, a UiAutomatorObjectNotFoundException is thrown.
If no matching UI element is found, a UiAutomatorObjectNotFoundException is thrown.
Suggested answer: A, D
asked 18/09/2024
Victor Chacon
41 questions

Question 24

Report Export Collapse

Each time your test invokes onView(), Espresso waits to perform the corresponding UI action or assertion until the following synchronization conditions are met: (Choose three.)

The message queue is empty.
The message queue is empty.
The message queue is not empty.
The message queue is not empty.
There are some instances of AsyncTask currently executing a task.
There are some instances of AsyncTask currently executing a task.
There are no instances of AsyncTask currently executing a task.
There are no instances of AsyncTask currently executing a task.
Some developer-defined idling resources are not idle.
Some developer-defined idling resources are not idle.
All developer-defined idling res
All developer-defined idling res
Suggested answer: A, D, F
asked 18/09/2024
Mpho Ntshontsi
43 questions

Question 25

Report Export Collapse

To run your local unit tests, follow these steps:

Be sure your project is synchronized with Gradle by clicking Sync Project in the toolbar.
Be sure your project is synchronized with Gradle by clicking Sync Project in the toolbar.
Run your test in one of the following ways (select possible): (Choose three.)
Run your test in one of the following ways (select possible): (Choose three.)
To run a single test, open the Project window, and then right-click a test and click Run .
To run a single test, open the Project window, and then right-click a test and click Run .
To test all methods in a class, right-click a class or method in the test file and click Run .
To test all methods in a class, right-click a class or method in the test file and click Run .
To run all tests in a directory, right-click on the directory and select Run tests .
To run all tests in a directory, right-click on the directory and select Run tests .
To run all tests in Project, open the Project window, and then right-click a test and click Run .
To run all tests in Project, open the Project window, and then right-click a test and click Run .
Suggested answer: A, B, C
asked 18/09/2024
jim eagleton
38 questions

Question 26

Report Export Collapse

To create a basic JUnit 4 test class, create a class that contains one or more test methods. A test method begins with the specific annotation and contains the code to exercise and verify a single functionality in the component that you want to test. What is the annotation?

@RunWith
@RunWith
@LargeTest
@LargeTest
@Rule
@Rule
@Test
@Test
Suggested answer: D
asked 18/09/2024
Tiffany Peterson
44 questions

Question 27

Report Export Collapse

Google Associate Android Developer image Question 27 27414 09182024191140000000

The Testing Pyramid, shown in the Figure, illustrates how your app should include the three categories of tests: small, medium, and large. Medium tests are integration tests that:

validate your app's behavior one class at a time.
validate your app's behavior one class at a time.
validate either interactions between levels of the stack within a module, or interactions between related modules.
validate either interactions between levels of the stack within a module, or interactions between related modules.
validate user journeys spanning multiple modules of your app.
validate user journeys spanning multiple modules of your app.
Suggested answer: B
asked 18/09/2024
Mathias Gontek
46 questions

Question 28

Report Export Collapse

Google Associate Android Developer image Question 28 27415 09182024191140000000

The Testing Pyramid, shown in the Figure, illustrates how your app should include the three categories of tests: small, medium, and large. Small tests are unit tests that :

validate your app's behavior one class at a time.
validate your app's behavior one class at a time.
validate either interactions between levels of the stack within a module, or interactions between related modules.
validate either interactions between levels of the stack within a module, or interactions between related modules.
validate user journeys spanning multiple modules of your app.
validate user journeys spanning multiple modules of your app.
Suggested answer: A
asked 18/09/2024
Md Hossain
49 questions

Question 29

Report Export Collapse

Google Associate Android Developer image Question 29 27416 09182024191140000000

What is illustrated in the picture?

Logcat window with filter settings
Logcat window with filter settings
Debugging native code using LLDB
Debugging native code using LLDB
The Variables and Watches panes in the Debugger window
The Variables and Watches panes in the Debugger window
The Breakpoints window lists all the current breakpoints and includes behavior settings for each
The Breakpoints window lists all the current breakpoints and includes behavior settings for each
Adding a watchpoint to a variable in memory
Adding a watchpoint to a variable in memory
Suggested answer: C
asked 18/09/2024
Rudy Raijmakers
44 questions

Question 30

Report Export Collapse

Google Associate Android Developer image Question 30 27417 09182024191140000000

What is illustrated in the picture?

Logcat window with filter settings
Logcat window with filter settings
Debugging native code using LLDB
Debugging native code using LLDB
The Variables and Watches panes in the Debugger window
The Variables and Watches panes in the Debugger window
The Breakpoints window lists all the current breakpoints and includes behavior settings for each
The Breakpoints window lists all the current breakpoints and includes behavior settings for each
Adding a watchpoint to a variable in memory
Adding a watchpoint to a variable in memory
Suggested answer: E
asked 18/09/2024
Francesco Balducci
40 questions
Total 128 questions
Go to page: of 13
Search
Open VPLUS File
Convert VPLUS to PDF

Related questions

Select four different types of app components. (Choose four.)
What statements about InputStreamReader (java.io.InputStreamReader) are correct? (Choose two.)
When your code execution reaches the breakpoint, Android Studio pauses execution of your app. You can then use the tools in the Debugger tab to identify the state of the app. With Step Out you can
In a class extended PreferenceFragmentCompat. What method is used to inflate the given XML resource and add the preference hierarchy to the current preference hierarchy?
As an example. Our MutableLiveData<Long> object, named mLapseTime, is not connected to a Room database, etc. How can we change the value in mLapseTime?
The Log class allows you to create log messages that appear in logcat. Generally, you could use the following log methods: (Choose five.)
DRAG DROP In a common Paging Library architecture scheme, move instances to the correct positions.
DRAG DROP With recommended app architecture. Fill the following diagram, which shows how all the modules usually should interact with one another after designing the app (drag modules to correct places).
An example. In our ViewModelFactory (that implements ViewModelProvider.Factory) we have an instance of our Repository, named mRepository. Our ViewModel has such constructor: public MyViewModel(MyRepository myRepository)... Next, in our ViewModelFactory create ViewModel method (overriden) looks like this: @NonNull @Override public <T extends ViewModel> T create(@NonNull Class<T> modelClass) { try { //MISSED RETURN VALUE HERE } catch (InstantiationException | IllegalAccessException | NoSuchMethodException | InvocationTargetException e) { throw new RuntimeException("Cannot create an instance of " + modelClass, e); }} What should we write instead of "//MISSED RETURN VALUE HERE"?
If you added to your build.gradle file a room.schemaLocation: android { defaultConfig { javaCompileOptions { annotationProcessorOptions { arguments = ["room.schemaLocation": "$projectDir/schemas".toString()] } } }} Then, you build your app or module. As a result you got a json file, with such path to it: app/schemas/your_app_package/db_package/DbClass/DB_VERSION.json What are the correct statements about this file? (Choose all that apply.)