Remove use of SkBitmap::Config (deprecated) from Source/web/tests/.

Source/web/tests/DragImageTest.cpp

Index: Source/web/tests/DragImageTest.cpp
diff --git a/Source/web/tests/DragImageTest.cpp b/Source/web/tests/DragImageTest.cpp
index 3277f07ded0243fa89d3ae067a5037ed5b95f139..31b379d5ad982fd9539fa697bb196e462463554c 100644
--- a/Source/web/tests/DragImageTest.cpp
+++ b/Source/web/tests/DragImageTest.cpp
@@ -64,9 +64,7 @@ public:
         , m_size(size)
     {
         m_nativeImage = NativeImageSkia::create();
-        m_nativeImage->bitmap().setConfig(SkBitmap::kARGB_8888_Config,
-                                          size.width(), size.height(), 0);
-        m_nativeImage->bitmap().allocPixels();
+        m_nativeImage->bitmap().allocN32Pixels(size.width(), size.height());

[reed1, 2014/03/21 15:18:40]

ASSERT_TRUE() ?

[jbroman, 2014/03/21 15:39:34]

Unfortunately, this isn't directly in the test or its SetUp/TearDown.
ASSERT_TRUE works by emitting a message (by accessing a singleton) and then
returning. (But this is in a constructor.)

I look a  little more closely at exactly how gtest handles ASSERT_TRUE and
EXPECT_TRUE. Apparently it *is* okay to put a non-fatal EXPECT_TRUE here, so I'm
adding that (even though it will still result in more errors later in the test,
this might help in debugging), but I don't think it's worth the complexity of
plumbing the boolean back to the test to ASSERT_TRUE.

     }
 
     virtual IntSize size() const OVERRIDE