From 648161bb0edfc3d43db63caed5cc5213bc6cb78f Mon Sep 17 00:00:00 2001
From: The Android Open Source Project Test for Bug 20385: Firebug command line extensions interfere with existing objects. To test, execute "$()" in the Inspector's Console. Also trying setting $. Test for Bug 19134: Inspector should support console.assert. To test, click the buttons below and look at the Inspector's Console. Test for Bug 17234: Inspector should link console.{log,warn,info,error} back to call site. To test, open the Inspector's Console and verify that all console messages have correct resource URLs and line numbers. Also verify that errors and warnings show up inline as bubbles in the resource source view. Test for Bug 17228: console.{log,warn,info,error} should support format strings, variable arguments. Open the Inspector (right-click and choose "Inspect Element"), then click the "Run Tests" button. Test for Bug 19159: Inspector should support console.time/console.timeEnd. Open the Inspector (right-click and choose "Inspect Element"), then click the "Run Tests" button. Test for Bug 20284: JavaScript can be executed even though debugger is running and at a break point. To test, open the Inspector and start a debugging session. Set a break point inside the stepOne() function. Now click the Step One button in the page. The breakpoint should be hit. While paused at the breakpoint click on the Step Two button. You should not see an alert dialog. Test for Bug 19053: Source code not visible when script is paused before onload fires. To test, open the Inspector and start a debugging session. You should see this file and execution line in the Scripts panel. Test for Bug 19173: Tool tips for Inspector debugger status bar buttons are wrong/missing. To test, open the Inspector and go to the Scripts panel. Check that the tool tips for the debugger's two status bar buttons make sense when each button is toggled on and off. Test for Bug 18837: Database panel fails to display tables if any value is NULL. To test: If the contents of the table appear (a single row with the value
-" Test for Bug 19438: Transaction errors are never displayed in database query view. To test: If the line of text you entered remains and an error line is output below
-it, you have passed the test. If the line of text you entered disappears and no error line is output, you
-have failed the test. If the line of text you entered remains and no error line is output, then
-the test has become invalid and needs to be modified to cause the error
-callback passed by the Inspector to Test for Bug 6590: Web Inspector shows stale DOM tree if the DOM changes after the inspector has loaded. To test, open the Inspector and watch the DOM change to match the page. Clicking the buttons will navigate the subframe, and the all the subframe child nodes should change. Test for Bug 18650:
-Errors/warnings in Inspector should be visible outside of Resources. To test, open the Inspector and click one of the buttons below. You should
-see an error and/or warning count in the Inspector's status bar. Clicking on
-the error/warning count should open the Console. Hovering over the
-error/warning count should show you a tooltip that matches the text in the
-button you clicked. Note: You must reload the page between each button press. Test for Bug 19065:
-Resources with a space in their URL don't get error/warning bubbles. To test, open the Inspector and refresh this page. There should be a red
-bubble with the number "1" in it next to the main resource in the Resources
-panel. Clicking the button below should change the "1" to a "2".
-
diff --git a/WebCore/manual-tests/inspector/debugger-pause-during-load.html b/WebCore/manual-tests/inspector/debugger-pause-during-load.html
deleted file mode 100644
index 631cafc..0000000
--- a/WebCore/manual-tests/inspector/debugger-pause-during-load.html
+++ /dev/null
@@ -1,5 +0,0 @@
-
-
-Start a debugging session in the Web Inspector and open this file. When the debugger breaks, select the (program) node
-in the call stack, you should see the execution line on the call to test().
-
-Also set a breakpoint on the call to test(), and reload. It should break before the test() function is called.
diff --git a/WebCore/manual-tests/inspector/debugger-pause-on-for-in-statements.html b/WebCore/manual-tests/inspector/debugger-pause-on-for-in-statements.html
deleted file mode 100644
index c0c24e0..0000000
--- a/WebCore/manual-tests/inspector/debugger-pause-on-for-in-statements.html
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-Test for Bug 22004: Can't set a breakpoint on the statement after a single line "for".
-
-Start a debugging session in the Web Inspector and open this file. When the debugger breaks, select the (program) node
-in the call stack, you should see the execution line on the call to test().
-
-Also set a breakpoint on the call to test(), and reload. It should break before the test() function is called.
diff --git a/WebCore/manual-tests/inspector/debugger-pause-on-for-statements.html b/WebCore/manual-tests/inspector/debugger-pause-on-for-statements.html
deleted file mode 100644
index 43a63e2..0000000
--- a/WebCore/manual-tests/inspector/debugger-pause-on-for-statements.html
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-Test for Bug 22004: Can't set a breakpoint on the statement after a single line "for".
-
-Start a debugging session in the Web Inspector and open this file. When the debugger breaks, select the (program) node
-in the call stack, you should see the execution line on the call to test().
-
-Also set a breakpoint on the call to test(), and reload. It should break before the test() function is called.
diff --git a/WebCore/manual-tests/inspector/debugger-status-bar-buttons-state.html b/WebCore/manual-tests/inspector/debugger-status-bar-buttons-state.html
deleted file mode 100644
index 31ca3b1..0000000
--- a/WebCore/manual-tests/inspector/debugger-status-bar-buttons-state.html
+++ /dev/null
@@ -1,2 +0,0 @@
-
-
-DisplaySQLNull
table inside the InspectorTest
databasenull
" in the test
column), you have passed the
-test.
-
-InspectorTest
databaseINSERT INTO DisplaySQLTransactionError (test) VALUES (NULL)
db.transaction
to be called.
Test for Bug 20042: UI frozen when the debugger is paused.
-Open the inspector and start debugging in the Scripts panel. While paused, try to open the Console. The Console should animate open fully.
diff --git a/WebCore/manual-tests/inspector/highlight-source-line.html b/WebCore/manual-tests/inspector/highlight-source-line.html deleted file mode 100644 index 2520485..0000000 --- a/WebCore/manual-tests/inspector/highlight-source-line.html +++ /dev/null @@ -1,4 +0,0 @@ -Test for Bug 19204: Inspector should highlight source lines when following links to them.
-To test, open the Inspector and reload this page. Then open the Inspector's Console and click the link for the markup error. You should see the line containing the error briefly highlighted in the source view.
- -This line contains a markup error.
diff --git a/WebCore/manual-tests/inspector/multiple-console-messages.html b/WebCore/manual-tests/inspector/multiple-console-messages.html deleted file mode 100644 index 842e6aa..0000000 --- a/WebCore/manual-tests/inspector/multiple-console-messages.html +++ /dev/null @@ -1,86 +0,0 @@ - - - - - -This test generates warnings, errors, and logs to test the grouping of repeated -messages in the Web Inspector. To check this test open the Web Inspector and see -that there are never any repeated messages that don't have a number next to them. -Test for Bug 19038: Crash in JavaScriptDebugServer::returnEvent when inspecting an attached Inspector.
-To test, open and attach the Inspector's debugger, then click the button below. If you don't crash, you have passed the test.
- diff --git a/WebCore/manual-tests/inspector/styled-error-bubbles-in-scripts.html b/WebCore/manual-tests/inspector/styled-error-bubbles-in-scripts.html deleted file mode 100644 index 0049cef..0000000 --- a/WebCore/manual-tests/inspector/styled-error-bubbles-in-scripts.html +++ /dev/null @@ -1,6 +0,0 @@ - -Test for Bug 19065: -Error bubbles are clobbered when syntax highlighting JavaScript resources.
-To test, open the Inspector. There should be a red bubble with the number "1" -in it next to the the only script resource in the Resources panel. Clicking the -resource should show syntax highlighted JavaScript with a red error bubble.
-- cgit v1.1