I've been in a few web projects and all had a testing phase just as any other projects: creating test plans based on the requirements and specification, doing f

I've been in a few web projects and all had a testing phase just as any other projects: creating test plans based on the requirements and specification, doing functional testing, integration testing, load testing, and so on. For what is worth, most of these applications were internal apps for large companies (users are the employees, not customers) and might as well have been developed as desktop or client-server apps. I see no reason why the choice of architecture/deployment would affect the QA policies. It might affect the particular way of testing (tools, etc) but not whether to test or not. I can't see quite see why is this even a question. Perhaps your colleagues are assuming that all web apps are like the typical apps they might use: B2C, free or "freemium", etc. Other things being equal, these are more likely to be released without careful testing.