System for testing markup language applications

Patent metadata

Field	Value
Publication number	US-9268668-B1
Application number	US-201213721632-A
Country	US
Kind code	B1
Filing date	Dec 20, 2012
Priority date	Dec 20, 2012
Publication date	Feb 23, 2016
Grant date	Feb 23, 2016

Abstract

A system is described for remotely testing markup language and script language based applications executing on a computing device. A development device such as a desktop computer executes one or more development tool modules. A communication module and an unpack module are deployed to a computing device which executes the application under test. These modules serve to connect the development tool module executing on the development device to an embedded test tool executing on the computing device. Using this connection, the development tool module is able to interactively test and interact with the application executing on the computing device.

First claim

What is claimed is:

1. A system comprising:
at least one processor;
at least one memory coupled to the at least one processor and storing instructions configured for execution on the at least one processor, the instructions comprising:
a user interface for testing options;
a markup language application including a first set of instructions expressed with one scripting language and a second set of instructions expressed with a markup language;
a selected scripting language engine configured to interpret the one scripting language, wherein the selected scripting language engine is selected for a debugging session from among a plurality of scripting language engines using the user interface of testing options, wherein each scripting language engine of the plurality of scripting language engines is configured to interpret the one scripting language;
a communication module configured to receive at least packed command data associated with the debugging session;
an unpack module configured to:
generate unpacked command data based on the received packed command data; and
provide the unpacked command data to an embedded test tool; and

the embedded test tool configured to:
interact with the selected scripting language engine; and
generate debugging output responsive to the unpacked command data, the debugging output generated through execution of the markup language application.

2. The system of claim 1 , wherein the communication module is further configured to send, at least a portion of the debugging output responsive to the unpacked command data.

3. The system of claim 1 , wherein the markup language application comprises hypertext markup language (“HTML”).

4. The system of claim 1 , wherein the communication module comprises a hypertext transport protocol (“HTTP”) server.

5. The system of claim 1 , wherein the markup language application is executed in a web browser application.

6. The system of claim 1 , the communication interface comprising a universal serial bus (“USB”) interface, and wherein the communication module is configured to support transmission control protocol (“TCP”) over the USB interface.

7. The system of claim 1 , wherein the external device is configured to execute a development tool module configured to generate the packed command data and receive the debugging output.

8. A computer-implemented method, comprising:
executing an application under test in a layout engine module, wherein the application under test comprises one or more instructions in one scripting language, wherein a selected scripting language engine is configured to interpret the one or more instructions in the one scripting language, and wherein the selected scripting language engine is selected using a user interface of testing options;
initializing, in the layout engine module, a debugging session for the application under test, wherein the debugging session is configured to generate output data for the application under test, wherein the debugging session is based on a testing option that selects the selected scripting language engine from among a plurality of scripting language engines, and wherein each scripting language engine of the plurality of scripting language engines is configured to interpret the one scripting language;
executing a communication module configured to receive at least packed command data associated with the debugging session; and
executing an unpack module configured to establish communication between the communication module and the layout engine module at least to provide unpacked command data based on the packed command data to the layout engine module.

9. The method of claim 8 , further comprising sending the output data received from the layout engine module using the connection.

10. The method of claim 8 , wherein the layout engine module comprises one or more test tools, and wherein the one or more test tools comprise at least one of: a runtime editing tool, a memory allocation information tool, and a platform resource usage information tool.

11. The method of claim 8 , the application under test further comprising one or more instructions expressed as a markup language.

12. The method of claim 8 , wherein the markup language application comprises hypertext markup language (“HTML”).

13. The method of claim 8 , the initializing the debugging session comprising placing the layout engine module into an inspection mode.

14. The method of claim 8 , wherein the application under test comprises a plurality of runtime instances.

15. The method of claim 8 , wherein the communication module comprises a hypertext transport protocol (“HTTP”) server.

16. The method of claim 8 , wherein providing unpacked command data based on the packed command data comprises:
generating the unpacked command data using the unpack module by at least extracting payload data from one or more packets; and
sending the unpacked command data to the layout engine module.

17. The method of claim 16 , wherein generating the unpacked command data comprises:
removing transmission control protocol headers; and
generating a string configured for processing by the layout engine module.

18. The method of claim 16 , wherein the packed command data is generated at least in part by a development tool.

19. The method of claim 8 , further comprising:
during the debugging session, determining a hierarchy view of the application under test, the hierarchy view including a plurality of objects associated with the application under test;
accessing a class reference included in the hierarchy view; and
modifying the executing of the application under test within the debugging session, based at least partly on the class reference.

20. One or more non-transitory computer-readable media storing instructions which, when executed by at least one processor, instruct the at least one processor to perform actions comprising:
executing an application under test in a layout engine module, wherein the application under test comprises one or more instructions in one scripting language;
initializing, in the layout engine module, a debugging session for the application under test, wherein the debugging session is configured to generate output data for the application under test, wherein the debugging session is based on a testing option to select a selected scripting language engine from among a plurality of scripting language engines, wherein the testing option to select the selected scripting language engine is selected using a user interface of testing options, and wherein each scripting language engine of the plurality of scripting language engines is configured to interpret the one scripting language;
during the debugging session, determining a hierarchy view of the application under test, the hierarchy view including a plurality of objects associated with the application under test;
accessing a class reference included in the hierarchy view; and
modifying execution of the application under test within the debugging session, based at least partly on the class reference.

21. The one or more non-transitory computer-readable media of claim 20 , wherein modifying execution of the application under test further comprises:
inspecting a testing option indicating that at least one graphics library is disabled; and
setting a value of the testing option to enable the at least one graphics library during the debugging session.

22. The one or more non-transitory computer-readable media of claim

Assignees

• Google Inc

Inventors

• Lachwani Manish
• Srinivasan Jay
• Patnaik Pratyus

Classifications

• G06F11/3698 Primary

  Environments for analysis, debugging or testing of software · CPC title

• G06F8/51

  Source to source · CPC title

• G06F11/3664 Primary

  Physics · mapped topic

• G06F9/455

  Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines · CPC title

• G06F11/3688

  for test execution, e.g. scheduling of test suites · CPC title