testing

Developer's Guide to Testing in WebGUI
All tests live in the t/ directory, /data/WebGUI/t.
Development Best Practices
One of WebGUI's greatest strengths is that it works on many operating systems and can connect to many external resources such as LDAP, Database, and web servers. If you're planning on writing plug-ins for or making core changes to WebGUI you should follow the coding guidelines presented here to ensure maximum compatibility. In addition, WebGUI has been built with performance in mind; we try to keep our code neat and elegant, so should you.
Smoke Tests
Smoke testing in WebGUI has the goal of testing WebGUI on as many user situations as possible. That would basically mean these categories:
Testing and Troubleshooting
Now it's time to test all of your labor to see if it all worked. The following tips are not meant to cover all possible installation and configuration problems that may occur, but rather to give you a shove in the right direction. If all else fails contact Plain Black under a support program for help.
WWW::Mechanize
If you're looking for a swiss knife to acces, test, to expand content or get reports from your WebGUI server or if you like to use the browser functions from within a program, have a look at WWW::Mechanize.