drgreen/android_frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

am aa0d43ba: Merge "Doc change: Link to AVDs docs from tablet quality checklist." into jb-dev-docs

Browse Source 
* commit 'aa0d43ba2581bb97f9ee955ea185b4f2759055c6':
  Doc change: Link to AVDs docs from tablet quality checklist.
This commit is contained in:
Dirk Dougherty
2012-10-09 15:50:12 -07:00
committed by Android Git Automerger
parent f19e4b420d aa0d43ba25
commit 28a40e01fe
2 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/html/distribute/googleplay/quality/core.jd
View File

@ -589,8 +589,9 @@ rather, you should focus on a small number of representative devices, even using
one or two devices per form factor. </p>
<p>If you are not able to obtain actual hardware devices for testing, you should
set up emulated devices (AVDs) to represent the most common form factors and
hardware/software combinations. </p>
<a href="{@docRoot}tools/devices/index.html">set up emulated devices (AVDs)</a>
to represent the most common form factors and
hardware/software combinations.</p>
<p>To go beyond basic testing, you can add more devices, more form factors, or
new hardware/software combinations to your test environment. You can also

3
docs/html/distribute/googleplay/quality/tablet.jd
View File

@ -528,7 +528,8 @@ one or two devices per form factor. The table below provides an overview of
devices you could use for testing.</p>
<p>If you are not able to obtain actual hardware devices for testing, you should
set up emulated devices (AVDs) to represent the most common form factors and
<a href="{@docRoot}tools/devices/index.html">set up emulated devices (AVDs)</a>
to represent the most common form factors and
hardware/software combinations. See the table below for suggestions on the emulator
configurations to use. </p>