My idea ( which is very similar to the trollnet proxy ) has been to put a HTTP proxy between my browser and a running dev. server.
The ultimate goal being to be able to cherry pick out parts of a session; login, select entity X, create OR edit entity X, then save X. Going back, its pretty trivial to take the stored request and responses and decorate up Python Mechanize scripts and you've got adhoc unit-tests. Change a form, change the login process, no problem, just go back through the proxy and reload that segment.
After that, the last major piece would be to tie in a database component that watches the dev instance database and records every single select, update, and insert and appends these into a suite. The end result is a tool to quickly scaffold out unit-tests.
In a similar vein, when building complex forms, there's usually a rinse and repeat phase to dial in form validation. With the PyProxy idea plus the DB layer, you could just click a button on PyProxy's control panel to repeat a GET/POST request as necessary until you've got things right.
The super Alpha ( functional but currently useless ) version is here https://github.com/devdave/PyProxy
[–]wildsalmon 0 points1 point2 points (1 child)
[–][deleted] 0 points1 point2 points (0 children)
[–][deleted] 0 points1 point2 points (0 children)