Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(120)

Unified Diff: third_party/WebKit/LayoutTests/fast/canvas/webgl/framebuffer-test-expected.txt

Issue 1601093008: Remove duplicated WebGL layout tests. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/LayoutTests/fast/canvas/webgl/framebuffer-test-expected.txt
diff --git a/third_party/WebKit/LayoutTests/fast/canvas/webgl/framebuffer-test-expected.txt b/third_party/WebKit/LayoutTests/fast/canvas/webgl/framebuffer-test-expected.txt
deleted file mode 100644
index 872111154d2346ba269d4cb78883698f8c7c67f2..0000000000000000000000000000000000000000
--- a/third_party/WebKit/LayoutTests/fast/canvas/webgl/framebuffer-test-expected.txt
+++ /dev/null
@@ -1,38 +0,0 @@
-This tests framebuffer/renderbuffer-related functions
-
-On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-
-
-Canvas.getContext
-PASS context exists
-
-Checking framebuffer/renderbuffer stuff.
-PASS calling getFramebufferAttachmentParameter on the default framebuffer should generate INVALID_OPERATION.
-PASS calling checkFramebufferStatus on the default framebuffer should generate FRAMEBUFFER_COMPLETE.
-PASS trying to attach a texture to default framebuffer should generate INVALID_OPERATION.
-PASS trying to detach default renderbuffer from default framebuffer should generate INVALID_OPERATION.
-PASS allocating renderbuffer storage of a newly created renderbuffer should succeed.
-PASS trying to attach a renderbuffer to the default framebuffer should generate INVALID_OPERATION.
-PASS binding a newly created framebuffer should succeed.
-PASS calling getFramebufferAttachmentParameter with target = READ_FRAMEBUFFER should generate INVALID_ENUM.
-PASS calling checkFramebufferStatus with target = READ_FRAMEBUFFER should return 0.
-PASS calling checkFramebufferStatus with target = READ_FRAMEBUFFER should generate INVALID_ENUM.
-PASS calling bindFramebuffer with target = READ_FRAMEBUFFER should generate INVALID_ENUM.
-PASS calling bindFramebuffer with target = READ_FRAMEBUFFER should not change FRAMEBUFFER_BINDING.
-PASS calling getFramebufferAttachmentParameter with target = READ_FRAMEBUFFER should generate INVALID_ENUM.
-PASS calling framebufferTexImage2D with target = READ_FRAMEBUFFER should generate INVALID_ENUM.
-PASS calling framebufferRenderbuffer with target = READ_FRAMEBUFFER should generate INVALID_ENUM.
-PASS calling framebufferTexImage2D with attachment = COLOR_ATTACHMENT1 should generate INVALID_ENUM.
-PASS calling framebufferRenderbuffer with attachment = COLOR_ATTACHMENT1 should generate INVALID_ENUM.
-PASS calling getFramebufferAttachmentParameter with pname = GL_FRAMEBUFFER_ATTACHMENT_COLOR_ENCODING should generate INVALID_ENUM.
-PASS attaching a texture to a framebuffer should succeed.
-PASS detaching a texture from a framebuffer should succeed.
-PASS calling framebufferTexture2D with non-zero mipmap level should generate INVALID_VALUE.
-PASS attaching a renderbuffer to a framebuffer should succeed.
-PASS detaching a renderbuffer from a framebuffer should succeed.
-PASS binding default (null) framebuffer should succeed.
-
-PASS successfullyParsed is true
-
-TEST COMPLETE
-

Powered by Google App Engine
This is Rietveld 408576698