I'm not sure if I'm confusing myself on unit versus acceptance testing.
Currently my test directory structure looks like:
tests/All.php
tests/acceptance-tests/All.php
/<moduleName>/All.php
/<long multi-page process test>
/unit-tests/All.php
/classes/All.php
/<class hierarchy>/All.php
/<assorted tests cases>
/web/All.php
/<moduleName/All.php
/<ModuleFunctionality>/All.php
/<little test cases>
/include/test_setup.inc
/<Custom Subclasses of Unit/Web TestCases>
/sql/<preload scripts>
/var (holding space for temp files, etc)
As you notice web stuff gets tested directly in both the unit and acceptance trees. My code is still a mix of procedural/OOP. Most of the serveable pages somewhat like a PageController with TemplateView, combined. Some are self-submitting and some have better logic/display seperation.
In either case I "needed" the unit-test webtests to drive the development of the user visible web-page and processing -- ie assertField in order to have a test for a field on a form, before adding the field, etc.
The acceptance tests on the other hand are long tests of a multipage form process.
I can see how as more and more of the code fets refactored, I'll have less need for the web unit tests as they'll move into classes and thus into the class subtree.
In the meantime, is this a logical distinction between unit/acceptance tests for the web side of the house?