documentation: Writing Unit and Rendering Tests

site/dev/contrib/submit.md

 How to submit a patch
 =====================
 
 
 Making changes
 --------------
 
 First create a branch for your changes:
 
 ~~~~
@@ skipping 14 matching lines @@
 $ gclient sync
 ~~~~
 
 
 Adding a unit test
 ------------------
 
 If you are willing to change Skia codebase, it's nice to add a test at the same
 time. Skia has a simple unittest framework so you can add a case to it.
 
-Test code is located under the 'tests' directory. Assuming we are adding
-tests/FooTest.cpp, The test code will look like:
+Test code is located under the 'tests' directory.
 
-<!--?prettify?-->
-~~~~
-/*
- * Copyright ........
- *
- * Use of this source code is governed by a BSD-style license that can be
- * found in the LICENSE file.
- */
-
-#include "Test.h"
-
-DEF_TEST(TestFoo, reporter) {
-   int x = 2 * 3;
-   if (x != 6) {
-       ERRORF(reporter, "x should be 6, but is %d", x);
-       return;
-   }
-   REPORTER_ASSERT(reporter, 1 + 1 == 2);
-}
-~~~~
-
-And we need to add this new file to gyp/tests.gyp. Note that file names are
-sorted alphabetically.
-
-<!--?prettify?-->
-~~~~
-'sources': [
-  '../tests/AAClipTest.cpp'
-  '../tests/FooTest.cpp',
-  '../tests/XfermodeTest.cpp',
-],
-~~~~
+See [Writing Unit and Rendering Tests](tests) for details.
 
 Unit tests are best, but if your change touches rendering and you can't think of
 an automated way to verify the results, consider writing a GM test or a new page
 of SampleApp. Also, if your change is the GPU code, you may not be able to write
 it as part of the standard unit test suite, but there are GPU-specific testing
 paths you can extend.
 
-
 Submitting a patch
 ------------------
 
 For your code to be accepted into the codebase, you must complete the
 [Individual Contributor License
 Agreement](http://code.google.com/legal/individual-cla-v1.0.html). You can do
 this online, and it only takes a minute. If you are contributing on behalf of a
 corporation, you must fill out the [Corporate Contributor License Agreement](http://code.google.com/legal/corporate-cla-v1.0.html) 
 and send it to us as described on that page. Add your (or your organization's) 
 name and contact info to the AUTHORS file as a part of your CL.
@@ skipping 151 matching lines @@
 
 git-cl will squash all your commits into a single one with the description you used when you uploaded your change.
 
 ~~~~
 git cl land
 ~~~~
 or
 ~~~~
 git cl land -c 'Contributor Name <email@example.com>'
 ~~~~