Skip to content

Home

Development

IDEs

API Explorer

Releases

Release notes

Martini Runtime

Martini Desktop

Martini Online

Feature requests

Bug reports

Debugging a Gloop template

Debugging is similar to running a Gloop template, except it allows you to stop/resume the rendering of a web page at certain points. This makes it possible to analyze a template step by step, so you could identify the cause of a bug more quickly. During debugging, you can check variable values and rendered web content per breakpoint.

Debugging a Gloop template with the Gloop services debugger

Gloop templates use the same debugger Gloop services use. So to debug your Gloop template, you need to use the [Gloop services debugger]]gloop-service-debugging.

There are many ways you can debug a Gloop template:

  • using the context menu from the Navigator;
  • using the context menu from the step editor;
  • using toolbar in the step editor; and
  • using the shortcut key in Martini Desktop; in Martini Online.

Debugging a template using the Navigator context menu

Debugging a template using the Navigator context menu

Debugging a template using the step editor

Debugging a template using the step editor

Previewing the rendered web page while debugging

Just like when you run a Gloop template, you can preview the rendered web page in a browser. But since you can pause the execution of the template manually or using breakpoints, you can see your template being generated step by step, and tag by tag.

Debugging a Gloop template

Debugging a Gloop template