Effective immediately, every WebGUI developer (including myself) is on report!</colbert> For too long have we been lenient regarding improving our automated test suite or even running our automated test suite.

Starting now, every commit to WebGUI stable and beta branches will be required to include regression tests. To enforce this, any commit that (1) causes a failing test, (2) does not include tests, or (3) reduces test coverage, will be immediately reverted. Once the patch is fixed, it can be recommitted. 

There will be no exceptions to this rule. We are all responsible for keeping WebGUI as bug-free as possible. Each version of WebGUI should be more stable than the last.

If there are any questions or grievances, you can direct them to (doug AT plainblack.com). Requests for exemptions will probably be denied, there is very little in the API that cannot be tested in some way. If you don't know how to test something, ask the #webgui IRC channel, ask the WebGUI Developers Mailing List, or ask me personally.

More information on:

• Selenium -- Make tests using your browser
• WGDev -- Tool for running tests with coverage
• Devel::Cover -- Perl module for detecting coverage

• UI-level testing
  While it is possible using Selenium and/or other techniques, the UI is too much of a moving target. So templates need not be tested.
• Upgrades
  There is currently no good way to thoroughly test upgrades. This will be coming soon.