Testing

Application testing should ferret out code failures, features that do not work correctly, navigational dead ends, usability issues, problems with data, security holes, performance problems, and any issues concerning assumptions made earlier in the project. Some organizations are more rigorous than others when it comes to testing practices and documentation, and naturally you will work within such guidelines, if they exist. In situations where you are left to your own devices, do as much testing as is possible within the time and resource constraints of the project.

As a developer, you work on a series of projects over time, and every project requires testing. Many aspects of QA are the same for every project. So setting up a rich testing environment and a consistent testing protocol that can be used repeatedly will save time over the long haul and will contribute to more uniform testing results.

Topics in this section cover some general strategies which you should consider. Follow...