One of the most powerful features of Dradis is our 1-click reporting engine.
When you are working with a custom report template, there will come a time when you need to do some debugging to understand how things are working or why you are not getting the results you expected.
In this guide you will learn how to debug issues with your template and how to identify problems with your content that are causing your template to fail.
This is a template debugging and troubleshooting guide. It covers:
If you're not getting an error message but instead missing content or having trouble getting tool output exporting into your reports, check to make sure your Plugin Manager is correctly configured for your Report template.
After you click Export, the on-screen log should update until "Worker process completed" appears. If the on-screen log isn't updating with any progress, the background worker may need a restart. To do this, run the following in the console as dradispro:
$ cd /opt/dradispro/dradispro/current
$ ps aux | grep resque
kill -9 all the processes (they'll auto-spawn).
Finally, test the export in the web app again. If that doesn't do the trick, try the command line export instructions.
If you don't have a report template yet and want to create your first one, I'd recommend these resources:
Next help article: Common problems →