10 Steps Toward Better Black Box Testing

Document, document, document. Document your test plan. Document each step you take. Document how and when each issue occurred so the developer can later recreate the scenario. Use text and screen captures to provide developers with as much information as possible.
Don't forget the basics. Check for spelling and grammatical errors. Verify that the changes follow your organization's rules and conventions for applications. When users encounter "obvious" mistakes, that experience may adversely affect their perception of your organization as a whole.
Report all errors. Don't make the mistake of identifying "only the important errors." Oftentimes you will be unable to determine which errors are related to significant problems. Better to mention all errors and let the developers evaluate them than to explain later why you failed to report an issue that had more severe consequences than you realized.
Focus on facts. Present your evaluation in the most objective and unemotional language possible. No one wants to think their work is flawed, or that they have made careless mistakes. Identify issues without assigning blame or implying ignorance. Foster cooperation and mutual respect so you and your developers can function efficiently as a team.
Recognize your limitations. It may sound like heresy, but it is important to remember that no application can be completely tested. Every delay in development affects the time remaining for testing, squeezing the test schedule ever tighter. The best testing methodology uses risk analysis to determine where errors can cause the most damage and focuses test efforts there, then supplements with more broad range testing.

And finally, a word of encouragement to all financial transaction testers... Despite the sometimes adversarial relationship between developers and testers, they do share a common goal: produce the best product in the least amount of time. As a tester, you are charged with giving each new feature the final stamp of approval. In essence, by thoroughly evaluating the usability and performance of the feature, you guarantee that everyone involved successfully reaches their goals. Coding errors can result in loss of income as well as loss of credibility for your organization. You are your organization's insurance against those losses. Take pride in the important role you play in your organization's success.

About Paragon Application Systems

Paragon Application Systems is a leading global provider of ePayment simulation, configuration and testing software tools to the financial industry. More than 400 financial institutions in over 80 countries use Paragon tools to improve quality and reduce time-to-market. Paragon's broad customer base includes major interchanges, processors, leading software providers, banks and credit unions. Visit Paragon Application Systems at www.paragonedge.com.

About the Author

Lynn Tjepkema, ePayment Specialist in Paragon's Professional Services department, is responsible for analyzing customer requests and developing working solutions to address testing needs. Lynn is ISTQB certified and has over 20 years of software development and testing experience in the financial services industry. She has extensive knowledge of financial network message protocols as well as authorization and settlement processing, with special emphasis on Visa, MasterCard and American Express.

Page 2 of 2

< Previous Page 1 2