System Testing – What to test?
You can’t test everything. That is a given. Even with some of the simplest software, the number of permutations for which tests could be written is astronomical. There is also a limited amount of time to execute your tests for them to be practical. Some engines perform faster than others. Still, if it takes two weeks to perform and evaluate tests, they may not longer be useful.
Since I like lists, here are a few of the ways I address the question, “What shall we Test?”
- Test Core Features which if not working, your application is useless
- Test security vulnerabilities such as HTML and SQL Injection
- Test edge cases requiring many steps to setup a scenario
Business Analysts are great resources for identifying meaningful test cases. They are often aware of the core features.
Edge cases are often available from your QA and/or support teams. They frequently have firsthand knowledge of those rare scenarios that happen when someone does something a little different than most users.
Security scenarios are frequent blog topics as well as training opportunities. Be sure to follow up on injection techniques for your applications.
I’m just touching the surface here. Why not send in your suggestions for What to Test in an Email to btaylor@sswug.org.
Cheers,
Ben
$$SWYNK$$
Featured White Paper(s)
All-At-Once Operations
Written by Itzik Ben-Gan with SolidQ
SQL supports a concept called all-at-onc… (read more)