I tend to believe that QA should focus equally on function and experience. Consequently, I'd: 1. Unit test both front and back end code. This thread is full of

I tend to believe that QA should focus equally on function and experience. Consequently, I'd: 1. Unit test both front and back end code. This thread is full of great examples for tools that will make that process easier. 2. Use a tool (I like jmeter) to frequently test how your project performs. You would be surprised how often small changes result in massive slowdowns, especially under load. 3. Bring basic usability testing into the QA fold. Web dev is extraordinarily client facing - projects live and die according to the whims of clients. Consequently, if you bring things like simple hallway testing into the development flow, your whole team will recognize how important it is to make things elegant and simple to use.