smain@google.com 97f483b4ca Move conceptual test info into "Getting Started with Testing" and ...

move the procedural information into the corresponding guides for creating
unit tests.

This is part of a cleanup for the Android Studio test docs, simplifying the
amount of content covered with Android Studio to be strictly how to create
and run tests. Bug: 28470079
Related: https://critique.corp.google.com/#review/125115510

Change-Id: I8b9590045b42a03c618e7011e0c3741aede77cd8

2016-06-22 11:13:54 -07:00

..

android_test_framework.png

…

eclipse_new_android_project_complete_callouts.png

…

eclipse_new_android_testproject_complete_callouts.png

…

eclipse_test_results.png

…

eclipse_test_run_failure.png

…

hwtest_create_test_class_menu_callouts.png

…

hwtest_junit_success.png

…

hwtest_new_test_class_dialog_complete_callouts.png

…

hwtest_new_test_project_dialog_complete_callouts.png

…

hwtest_new_test_project_menu.png

…

hwtest_runas_menu_callouts.png

…

spinner_create_test_class_callouts.png

…

spinnertest_junit_panel_fail_callouts.png

…

spinnertest_junit_panel_failtrace_callouts.png

…

spinnertest_junit_panel.png

…

spinnertest_junit_success.png

…

spinnertest_new_class_callouts.png

…

spinnertest_runas_menu_callouts.png

…

test-types_2x.png

…

test-types.zip

…

testing-icon.png

…

UIAutomatorViewer.png

…