Diagnostics and Error Reporting For Common Tagging Issues

• US 20080155340A1
• Filed: 10/30/2006
• Published: 06/26/2008
• Est. Priority Date: 10/30/2006
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Tsun, Stephen
• Granted Patent: US 7,644,315 B2
• Time in Patent Office: Days
• US Class Current: 714/38
• 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 method, comprising:

requesting a document containing a script at a location, the request including an indicator;

receiving the document in response to the request;

executing the script to test a status of a condition in response to receipt of the indicator; and

displaying the status of the condition.

2. The method of claim 1, further comprising:

displaying a window; and

displaying the status in the window.

3. The method of claim 2, further comprising:

determining a status state; and

color-coding the status based the status state.

4. The method of claim 2, further comprising:

displaying timing information in the window to show a length of time required complete an operation specified by the condition.

5. The method claim 2, further comprising:

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

display responses from the content server in the window.

6. The method of claim 1, wherein executing the script to test the status of the condition further comprises testing if function calls specified in the document are missing or occur in an incorrect sequence.

7. The method of claim 1, wherein executing the script to test the status of the condition further comprises determining if the document includes an incorrect slot name, out-of-sequence JavaScript tags, or attempts to fill a slot that has not been added.

8. The method of claim 1, wherein executing the script to test the status of the condition further comprises determining if a discrepancy exits 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 executing the script to test the status of the condition further comprises testing if content is successfully received by but knot 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 configurable to receive content;

a publisher server operatively coupled to the content server and configurable to determine a context from the content; and

a content repository operatively coupled to the content server and configurable for providing the content server with content associated with a context,

wherein the publisher server provides computer executable instructions to a client device upon receiving a request form the client device, the computer executable instructions being executed by the client device to determine conditions related to the communication of content from the content repository to the client device.

13. A system, comprising:

a processor configurable to request content from a remote location, the content including computer executable instructions to determine debugging information associated with the request; and

an interface operatively coupled to the processor and configurable to display the debugging information, the debugging information including errors associated with the display of the content in the interface.

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

displaying first content provided by a publisher;

displaying second content provided by a content server;

debugging instructions to obtain the second content from the content server; and

displaying results of the debugging in an interface.

15. The computer-readable medium of claim 14, where displaying results of the debugging comprises:

determining a severity of the results; and

color-coding the results based the severity.

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

17. The computer-readable medium of claim 14, where debugging instructions comprises testing if function calls are missing or occur in the wrong sequence.

18. The computer-readable medium of claim 14, where debugging instructions comprises testing if the instructions specify one of an incorrect slot name, out-of-sequence JavaScript tags, or fills a slot that has not been added.

19. The computer-readable medium of claim 14, where debugging instructions comprises testing to determine if discrepancies exist between the instructions and information stored on the content server.

20. The computer-readable medium of claim 19, where 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 specified by the instructions.

21. The computer-readable medium of claim 14, where debugging instructions comprises further comprises testing if content is successfully received but not displayed.

22. A system, comprising:

means for receiving a document provided by a remote publisher;

means for executing instructions contained in the document, where the instructions fetch content from a content server;

means for debugging the instructions to determine errors in the fetching of content from the content server; and

means for displaying the errors.

23. A method, comprising:

examining a request for a document to determine a presence of errors, the document including a script to debug requests for content; and

writing error conditions to a user interface presented to the content requestor.