Writing Quality Software: A Primer - System Testing (Page 7 of 7 )
System testing is what we are all used to, and what we all may or may not enjoy. System testing involves firing up our web browsers and hoping for the best. We ensure the interface displays correctly and we confirm that data is being stored, retrieved and manipulated properly.
When system testing, take one chunk at a time. If your application is large, focus on a particular page. Before moving to the next, make sure the page is absolutely 100% correct. Focusing on too many elements of your application at once causes confusion and increases the chances of overlooking common errors.
When testing the system, pay special attention to unexpected data. Make your application handle the unexpected data, just like you did in a unit test. But in this case, ensure that your interface remains consistent and a clear error message is presented. Error messages should both explain what the error is and how to fix it. Users need to be guided.
System testing is usually the last step in writing quality software. Once all modules and control structures are thoroughly screened and the interface tested, quality software is right around the corner.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 23 
