Lukas Smith looks, in a new post today, asking for some of the current thoughts and feelings surrounding the process of QA-ing PHP applications.
He goes through five different steps in a QA process that can help you find the issues with your application long before any user gets their hands on it:
- using testing tools like PHPUnit or phpt (including code coverage
- moving on to Selenium or BadBoy (or similar testing tools) to check the runtime flow
- making ample documentation with things like phpDocumentor or Doxygen
- Providing debugging tools for frameworks to make locating errors easier than digging through code and comments
- use code analyzers to check for attacks/vulnerabilities like cross-site scripting or SQL injections
So what am I missing? Any tool I should have mentioned, team management approach? I am sure I have since I just wrote this blog post very quickly and I do not have a check list yet. Speaking of checklist, that sounds like a good thing to have when doing QA.