Diagnostics and error reporting for common tagging issues

• US 7,644,315 B2
• Filed: 10/30/2006
• Issued: 01/05/2010
• Est. Priority Date: 10/30/2006
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Tsun, Stephen
• Primary Examiner(s): Baderman; Scott T
• Assistant Examiner(s): Leibovich; Yair
• Application Number:
  US11/554,397
• Publication Number:
  US 20080155340A1
• Time in Patent Office: 1,163 Days
• Field of Search: 714/38
• US Class Current: 714/38.14
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 16/93 Document management systems

Abstract

Content requests are debugged in accordance with a presence of a flag in a request to a publisher. A document received from the publisher contains a script to debug requests for content to a content provider. The requests are examined to determine the presence of informational, warning and error conditions. The conditions are written to a debugging user interface.

Claims

1. A computer-implemented method, comprising:

requesting, at a client device, a document referencing a script stored at a location, the script including content processing instructions and diagnostic instructions;

receiving, at the client device, the document and the script in response to the request;

executing, at the client device, the content processing instructions of the script to process content requests for requesting content to be displayed with the document;

executing, at the client device, the diagnostic instructions of the script to determine whether the request included an additional debug indicator and only in response to determining that the request included the additional debug indicator;

performing, at the client device, diagnostic tests related to the processing of the content requests for the document;

generating, at the client device, a debugging user interface; and

displaying in the debugging user interface results of the diagnostic tests.

2. The method of claim 1, wherein:

the document is a web page; and

further comprising displaying the web page in a first browser window on the client device;

wherein generating, at the client device, a debugging user interface comprises generating a second browser window separate from the first browser window on the client device.

3. The method of claim 2, further comprising:

determining a status state of a result of a diagnostic test; and

color-coding the result based the status state.

4. The method of claim 2, further comprising:

displaying timing information in the second browser window to show a length of time required complete an operation tested by a diagnostic test.

5. The method of claim 2, further comprising:

displaying requests made to a content server in the second browser window; and

display responses from the content server in the second browser window.

6. The method of claim 1, wherein performing diagnostic tests related to the processing of the content requests comprises testing if function calls specified in the document are missing or occur in an incorrect sequence.

7. The method of claim 1, wherein performing diagnostic tests related to the processing of the content requests comprises determining if the document includes an incorrect slot name, or out-of-sequence JavaScript tags.

8. The method of claim 1, wherein performing diagnostic tests related to the processing of the content requests comprises determining if a discrepancy exists between information specified by the document and information stored on a content server.

9. The method of claim 8, wherein the discrepancy comprises one of differences between tags specified in the document and information on the content server, latency issues caused by delays in the content server, or disabled slots in the document.

10. The method of claim 1, wherein performing diagnostic tests related to the processing of the content requests comprises testing if requested content is successfully received by the client device but not displayed.

11. The method of claim 1, wherein the request is a Uniform Resource Locator (URL) of the document and the indicator is a flag added to the URL.

12. A system, comprising:

a content server configured to receive content requests from a client device and provide content in response to the content requests, and further configured to receive script requests from the client device and provide a script in response to the request;

wherein the content requests and the script requests are sent from the client device in response to rendering a web page provided to the client device from a publisher server in response to a page request from the client device, the web page including instructions that cause the client device to send the content requests and script requests; and

a repository operatively coupled to the content server and storing the content and the script;

wherein the script includes diagnostic instructions that are executed by the client device and cause the client device to determine if the web page request for the web page included an additional debug indicator, and only in response to determining that the web page request included the additional debug indicator, perform the operations of;

performing, at the client device, diagnostic tests related to the processing of the content requests for the web page;

generating, at the client device, a debugging user interface; and

displaying in the debugging user interface results of the diagnostic tests.

21. The system of claim 12, wherein:

the web page is rendered in a first window at the client device; and

generating, at the client device, a debugging user interface comprises generating a second browser window separate from the first browser window on the client device.

22. The system of claim 12, wherein performing diagnostic tests related to the processing of the first content requests comprises:

testing for syntax errors in the web page; and

testing for semantic errors in the web page.

23. The system of claim 12, wherein displaying in the debugging user interface results of the diagnostic tests comprises:

displaying a status level of a result of each diagnostic test;

displaying a message detailing the result of each diagnostic test; and

color-coding each message according to the status of the result.

13. A computer-readable medium having instructions stored thereon, which, when executed by a client device, causes the client device to perform the operations of:

processing first content requests for requesting first content to be displayed with a web page provided by a publisher, the web page having been received at the client device in response to a web page request;

determine whether the web page request included an additional debug indicator and only in response to determining that the web page request included the additional debug indicator;

performing diagnostic tests related to the processing of the content requests for the web page;

generating a debugging user interface; and

displaying in the debugging user interface results of the diagnostic tests.

14. The computer-readable medium of claim 13, where displaying results of the diagnostic tests comprises:

determining a severity of the results; and

color-coding the results based the severity.

15. The computer-readable medium of claim 13, where displaying results of the diagnostic tests comprises displaying timing information in the debugging user interface to show a length of time required complete a predetermined instruction.

16. The computer-readable medium of claim 13, wherein performing diagnostic tests related to the processing of the first content requests comprises testing if function calls are missing or occur in the wrong sequence.

17. The computer-readable medium of claim 13, wherein performing diagnostic tests related to the processing of the first content requests comprises testing for an incorrect slot name, or out-of-sequence JavaScript tags.

18. The computer-readable medium of claim 13, wherein performing diagnostic tests related to the processing of the first content requests comprises testing to determine if discrepancies exist between the instructions and information stored on the content server.

19. The computer-readable medium of claim 18, wherein the discrepancies include differences between tags specified in the instructions and information on the content server, latency issues caused by delays in the content server, or disabled slots in the web page.

20. The computer-readable medium of claim 13, wherein performing diagnostic tests related to the processing of the first content requests comprises further comprises testing if content is successfully received but not displayed.