9ea53f93e7
That way when declaring a test with DEF_TEST() macro, you don't have to
uniquify the test name because it might colide with the class it is
being testing.
For example, if you are testing SkBase64 and do:
DEF_TEST(SkBase64, reporter) {
}
That will generate an error because the macro will declare a function
named SkBase64 which colides with the type SkBase64.
By adding Test to the function name we avoid this problem.
Fixed the entries found with the following command line:
$ git grep "Test, r" | grep DEF
BUG=None
TEST=make tests && out/Debug/tests
R=mtklein@google.com
Author: tfarina@chromium.org
Review URL: https://codereview.chromium.org/345753007
30 lines
810 B
C++
30 lines
810 B
C++
/*
|
|
* Copyright 2014 Google Inc.
|
|
*
|
|
* Use of this source code is governed by a BSD-style license that can be
|
|
* found in the LICENSE file.
|
|
*/
|
|
|
|
#include "Test.h"
|
|
|
|
#include "../include/record/SkRecording.h"
|
|
|
|
// Minimally exercise the public SkRecording API.
|
|
|
|
DEF_TEST(SkRecording, r) {
|
|
EXPERIMENTAL::SkRecording recording(1920, 1080);
|
|
|
|
// Some very exciting commands here.
|
|
recording.canvas()->clipRect(SkRect::MakeWH(320, 240));
|
|
|
|
SkAutoTDelete<const EXPERIMENTAL::SkPlayback> playback(recording.releasePlayback());
|
|
|
|
SkCanvas target;
|
|
playback->draw(&target);
|
|
|
|
// Here's another recording we never call releasePlayback().
|
|
// However pointless, this should be safe.
|
|
EXPERIMENTAL::SkRecording pointless(1920, 1080);
|
|
pointless.canvas()->clipRect(SkRect::MakeWH(320, 240));
|
|
}
|