Add Chrome for Android UI overview doc

Initial draft aggregating pointers and resources for Chrome for Android
UI development.

BUG=1009781

Change-Id: I8f085bcae520c251166502d33975fac554915d65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832487
Commit-Queue: Theresa  <twellington@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#701368}

docs/README.md

@@ -274,6 +274,8 @@ used when committed.
     How to build Android app bundles for Chrome.
 *   [Dynamic Feature Modules (DFMs)](android_dynamic_feature_modules.md) - How
     to create dynamic feature modules.
+*   [Chrome for Android UI](ui/android/overview.md) - Resources and best practices for
+    developing UI
 
 ### Misc iOS-Specific Docs
 *   [Continuous Build and Test Infrastructure for Chromium for iOS](ios/infra.md)

docs/ui/android/mvc_testing.md

+# So, you want to test MVC...
+
+## Overview
+This document is intended to go over the best practices of testing the various MVC components.
+
+If you are new to MVC, read the intro guide here: [So, you want to MVC...](mvc_architecture_tutorial.md)
+
+
+## Testing principles
+Keep your tests small and isolated to just the component you are testing.
+
+Keep the number of large integration tests to a minimum (e.g. testing the full coordinator together).
+
+Test each element of your component independently (where possible).  The Mediator should be testable without a View, View without the Mediator.
+
+### General Best Practices
+
+assertTrue/assertFalse should only be used for methods that return booleans.  Here are some examples of the bad usage of assertTrue and their most descriptive and useful counterparts:
+  * assertTrue(foo == null);
+    * assertIsNull(foo);
+  * assertTrue(“test”.equals(foo));
+    * assertEquals(“test”, foo);
+  * assertTrue(foo.endsWith(“blah”));
+    * assertThat(foo, endsWith(“blah”));
+    * Look at [Hamcrest Matchers](http://hamcrest.org/JavaHamcrest/javadoc/1.3/org/hamcrest/Matchers.html) for more magical assertion help
+
+
+## Testing your Mediator
+The core business logic of your component should live within your mediator.
+
+Ideally, the Mediator should be testable using Robolectric on the host machine (TODO: link to general Robolectric/Junit test guide).
+
+### Best practices for testability for your Mediator:
+
+ * Pass in all dependencies via the constructor
+    * This allows you to mock any necessary external components
+ * Do not add native dependencies in the Mediator directly.
+    * Put all of your native calls in a separate file that allows you to mock out the JNI calls without spinning up all of native.
+ * Your mediator should not need to be extended, spied or mocked for testing.  If you find yourself needing to extend the Mediator to stub out a method, you should move the dependency to something that can be passed in.
+
+### Good examples of Mediator/Test pairs:
+
+ * [TabListMediator](/chrome/android/features/tab_ui/java/src/org/chromium/chrome/browser/tasks/tab_management/TabListMediator.java) / [TabListMediatorUnitTest](/chrome/android/features/tab_ui/junit/src/org/chromium/chrome/browser/tasks/tab_management/TabListMediatorUnitTest.java)
+ * [TabSwitcherMediator](/chrome/android/features/tab_ui/java/src/org/chromium/chrome/browser/tasks/tab_management/TabSwitcherMediator.java) / [TabSwitcherMediatorUnitTest](/chrome/android/features/tab_ui/junit/src/org/chromium/chrome/browser/tasks/tab_management/TabSwitcherMediatorUnitTest.java)
+
+
+## Testing your View
+
+The View/ViewBinder should be tested as an independent unit.
+
+### Best practices for testability for your View:
+
+ * Tests for UI should be based on the [DummyUiActivity](/chrome/test/android/javatests/src/org/chromium/chrome/test/ui/DummyUiActivity.java).  This activity does not have any dependencies on the Chrome browser and allows you to test your UI in isolation.  This ensures you are not competing against other Chrome tasks and can write a test that is much faster and less flaky than legacy UI instrumentation tests.
+ * When adding tests for your UI component, add a [RenderTest](/chrome/test/android/javatests/src/org/chromium/chrome/test/util/RENDER_TESTS.md) to ensure the UI is consistent from release to release unless you explicitly changed it.
+
+### Useful helpers / Links
+
+ * To test a single View/ViewBinder normally used in a RecyclerView, this PropertyModelChangeProcessor.ViewBinder implementation, [TestRecyclerViewSimpleViewBinder.java](/chrome/android/features/tab_ui/javatests/src/org/chromium/chrome/browser/tasks/tab_management/TestRecyclerViewSimpleViewBinder.java), allows to test individual UI element without needing to build a full RecyclerView.
+
+### Good examples of View/Test pairs:
+ * [TabGridViewBinder](/chrome/android/features/tab_ui/java/src/org/chromium/chrome/browser/tasks/tab_management/TabGridViewBinder.java), [TabStripViewBinder](/chrome/android/features/tab_ui/java/src/org/chromium/chrome/browser/tasks/tab_management/TabStripViewBinder.java) / [TabListViewHolderTest](/chrome/android/features/tab_ui/javatests/src/org/chromium/chrome/browser/tasks/tab_management/TabListViewHolderTest.java)
+

docs/ui/android/overview.md

+# Chrome for Android UI
+
+## Ramping-up
+
+Android has a number of [developer guides](https://developer.android.com/guide) that are helpful for getting ramped up on general Android development. We recommend reading the following as primers for developing UI:
+
+ * [Application fundamentals](https://developer.android.com/guide/components/fundamentals)
+ * [Providing resources](https://developer.android.com/guide/topics/resources/providing-resources.html)
+ * [Layouts](https://developer.android.com/guide/topics/ui/declaring-layout)
+ * [Introduction to activities](https://developer.android.com/guide/components/activities/intro-activities)
+
+
+## Colors and text styles
+
+Chrome for Android has a color palette defined in [//ui/android/java/res/values/color_palette.xml](/ui/android/java/res/values/color_palette.xml) and a set of reusable semantic colors defined in [//ui/android/java/res/values/colors.xml](/ui/android/java/res/values/colors.xml). The semantic colors from colors.xml should be used to ensure colors adapt properly for dark mode and can be consistently and easily updated during product-wide visual refreshes.
+
+For more information on selecting the right color, see [Night Mode on Chrome Android](night_mode.md).
+
+## Widgets
+
+The Chromium code base contains a number of wrappers around Android classes (to smooth over bugs or save on binary size) and many UI widgets that provide Chrome-specific behavior and/or styling.
+
+These can be found in [//chrome/browser/ui/android/widget/](/chrome/browser/ui/android/widget/), [//ui/android/](/ui/android/), and [//chrome/android/java/src/org/chromium/chrome/browser/widget/](/chrome/android/java/src/org/chromium/chrome/browser/widget/). There is an ongoing effort to consolidate all widgets in //chrome/browser/ui/android/widget/.
+
+## MVC
+
+UI development should follow a modified Model-View-Controller pattern. MVC base classes live in [//ui/android/java/src/org/chromium/ui/modelutil](/ui/android/java/src/org/chromium/ui/modelutil/).
+
+The following guides introduce MVC in Chrome for Android:
+
+ * [So, you want to do MVC...](mvc_architecture_tutorial.md)
+ * [Simple Lists in MVC Land](mvc_simple_list_tutorial.md)
+ * [Simple RecyclerView use in MVC](mvc_simple_recycler_view_tutorial.md)
+ * [So, you want to test MVC...](mvc_testing.md)

docs/ui/navbar.md

@@ -5,6 +5,7 @@
 * [Aura](/docs/ui/aura/index.md)
 * [Compositor](/docs/ui/compositor/index.md)
 * [Views](/docs/ui/views/overview.md)
+* [Android UI](/docs/ui/android/overview.md)
 * [Product Excellence](/docs/ui/product_excellence/index.md)
 * [UI Devtools](/docs/ui/ui_devtools/index.md)