Let DM run unit tests.
authorcommit-bot@chromium.org <commit-bot@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81>
Wed, 26 Feb 2014 16:31:22 +0000 (16:31 +0000)
committercommit-bot@chromium.org <commit-bot@chromium.org@2bbb7eff-a529-9590-31e7-b0007b416f81>
Wed, 26 Feb 2014 16:31:22 +0000 (16:31 +0000)
commit0dc5bd149a8b69e8dc6d3b4713b827659c9b0a6b
tree53fdc1e7747c8ed33c275deb6f24802bc41d365a
parent1e762d39bb6383d33d8e1f04a296f164aa2a6beb
Let DM run unit tests.
  - refactor GYPs and a few flags
  - make GPU tests grab a thread-local GrContextFactory when needed as we do in DM for GMs
  - add a few more UI features to make DM more like tests

I believe this makes the program 'tests' obsolete.

It should be somewhat faster to run the two sets together than running the old binaries serially:
  - serial: tests 20s (3m18s CPU), dm 21s (3m01s CPU)
  - together: 27s (6m21s CPU)

Next up is to incorporate benches.  I'm only planning there on a single-pass sanity check, so that won't obsolete the program 'bench' just yet.

Tested: out/Debug/tests && out/Debug/dm && echo ok
BUG=skia:

Committed: http://code.google.com/p/skia/source/detail?r=13586

R=reed@google.com, bsalomon@google.com, mtklein@google.com, tfarina@chromium.org

Author: mtklein@chromium.org

Review URL: https://codereview.chromium.org/178273002

git-svn-id: http://skia.googlecode.com/svn/trunk@13592 2bbb7eff-a529-9590-31e7-b0007b416f81
17 files changed:
dm/DM.cpp
dm/DMGpuTask.cpp
dm/DMGpuTask.h
dm/DMReporter.cpp
dm/DMReporter.h
dm/DMTask.cpp
dm/DMTask.h
dm/DMTaskRunner.cpp
dm/DMTaskRunner.h
dm/DMTestTask.cpp [new file with mode: 0644]
dm/DMTestTask.h [new file with mode: 0644]
gyp/dm.gyp
gyp/tests.gyp
gyp/tests.gypi [new file with mode: 0644]
tests/Test.cpp
tests/Test.h
tests/skia_test.cpp