e3f6c81c31
* Added new 'Getting Started with Testing' training to contain common
information on how to configure and run tests with Android Studio.
* Removed the obsolete 'Testing Your Activity' training.
* Deleted obsolete testing content under 'Tools > Workflow'.
* Moved accessibility testing checklist to 'Implementing accessibility'
training section.
* Moved content provider and service testing topics into a new
'Testing App Integrations' training.
* Updated the service testing training to reflect our recommended
approach of using ServiceTestRule, instead of ServiceTestCase.
* Renamed 'Testing from Other IDEs' topic to
'Testing from the Command Line' and moved it under 'Testing Tools'.
* Revised 'Testing Fundamentals' topic and moved it under 'Testing Tools'.
* Updated the landing page fo 'Best Practises for Testing' to provide a
central location for testing-related resources.
bug: 20722624
Change-Id: Ic1cbc79b48916dcae1c09bf5114ba8aef13d6f27
56 lines
2.1 KiB
Plaintext
56 lines
2.1 KiB
Plaintext
page.title=Android Testing Tools
|
|
@jd:body
|
|
|
|
<div id="qv-wrapper">
|
|
<div id="qv">
|
|
<h2>See also</h2>
|
|
<ol>
|
|
<li><a href="{@docRoot}training/testing/index.html">Best Practices for Testing</a></li>
|
|
</ol>
|
|
</div>
|
|
</div>
|
|
|
|
<p>
|
|
Testing is a critical software development activity because it helps you
|
|
improve the quality of your apps, ensure better user satisfaction, and
|
|
reduce overall development time spent on fixing defects.
|
|
</p>
|
|
|
|
<p>The following sections describe tools that help
|
|
you test your mobile apps for the Android platform.</a>
|
|
|
|
<dl>
|
|
<dt><strong><a href="{@docRoot}tools/testing-support-library/index.html">Android
|
|
Testing Support Library</a></strong></dt>
|
|
<dd>This library provides a set of APIs that allow
|
|
you to quickly build and run test code for your apps, including JUnit 4 and functional user
|
|
interface (UI) tests. The Android Testing Support Library includes the following test automation
|
|
tools:
|
|
|
|
<ul>
|
|
<li><a href="{@docRoot}tools/testing-support-library/index.html#AndroidJUnitRunner">AndroidJUnitRunner</a>:
|
|
JUnit 4-compatible test runner for Android
|
|
</li>
|
|
|
|
<li><a href="{@docRoot}tools/testing-support-library/index.html#Espresso">Espresso</a>:
|
|
UI testing framework; suitable for functional UI testing within an app
|
|
</li>
|
|
|
|
<li><a href="{@docRoot}tools/testing-support-library/index.html#UIAutomator">UI Automator</a>:
|
|
UI testing framework; suitable for cross-app functional UI testing across system and installed apps
|
|
</li>
|
|
</ul>
|
|
</dd>
|
|
|
|
<dt><strong><a href="{@docRoot}tools/help/monkey.html">Monkey</a></strong></dt>
|
|
<dd>This tool runs on your emulator or device and generates pseudo-random streams of user
|
|
events such as clicks, touches, or gestures, as well as a number of system-level events. You can
|
|
use the Monkey tool to stress-test applications that you are developing, in a random yet
|
|
repeatable manner.
|
|
</dd>
|
|
|
|
<dt><strong><a href="{@docRoot}tools/help/monkeyrunner_concepts.html">monkeyrunner</a></strong></dt>
|
|
<dd>This testing system provides an API for writing programs that control an Android device or
|
|
emulator from outside of Android code.</dd>
|
|
|
|
</dl> |