in reply to Large Web Application Ponderings

You'll likely get a lot of good advice from your questions, but the truly wise are those that seek answers to the questions they didn't even know to ask.

That would be your question #4.

These coalesce into a higher order problem of version/revision control and roll-out/roll-back that will bite hard later on. When the apps get large and heavily used, rolling out a new version that doesn't break everything can be a real pain.

Replies are listed 'Best First'.
Re^2: Large Web Application Ponderings
by saberworks (Curate) on Nov 09, 2007 at 17:13 UTC
    Good points, I would definitely recommend looking into Selenium ( It's a tool that lets you record a browser session and then export it as a test (you can export to a number of languages, including perl). The tests can then be rerun at any time to make sure you didn't break anything. It's not only good for automated web interface testing, but also for things like populating a new install with data so you can run your tests against populated systems.