When testing new features, like buttons and the processes behind these buttons, unexpected behavior can occur.
How can I debug processes?
One way to find bugs is by starting a trace analysis. A trace analysis is like a long HTML file where nearly every action that is executed in an application is logged.
One can see the value of variables, which processes have been started with which parameters, which SQL has been executed (etc…) and how long each action took.
Read this post to find out more about how to set up a trace for an application.
To make the trace more readable, to immediately jump to errors and for finding the performance bottlenecks use the Traceformatter browser plugin.
It recognizes Novulo traces and adds extra features that facilitate finding bugs:
Firefox: https://addons.mozilla.org/en-GB/firefox/addon/novulotraceformatter/
Chrome: https://chrome.google.com/webstore/detail/novulotraceformatter/aoncjcaidgjomhdkjfkbflaeejlamdif
Screenshot of a formatted trace file
The important addition: the Novulo trace formatter has a new feature that allows you to quickly find out from which component a form row or a grid comes. This works in any 3.8 Novulo application that ends in “default.aspx”.
If you already have the latest version of the trace formatter, this option will be added in the menu of an application:
After reloading, “Architect links” and tootltips will appear.
Via the links you can open the corresponding component revision in the architect with 1 click:
If you have already installed the trace formatter but no new option appears, restart your browser so that you get version 4.0 or higher. Otherwise, you can also add the extension to your browser via one of the links above.