|
|
|
Electronic Payments Testing:
|
||||||||||
| Situation | Examples of Testing From Each Test Classification |
| Adding a new report | Unit Testing: A developer uses a driver to feed report data into the reporting system, then a stub to create the new report. The output is extracted from the system and examined. The developer (or a QA tester) ensures that the report is formatted correctly, and that the report data is accurate. Integrated Testing: After unit testing is completed, the tester manually triggers each step in the process of generating and distributing the new report and examines the results. (For example, rather than adding the report to the automated report generator, the tester might use line commands to generate the report and to print it.) The tester verifies the ability to display the report online as well as examining the printed report for proper line feeds, page breaks, etc. Functional Testing: A tester examines the new report to ensure it satisfies both the user's specifications and the organization's standards; for example, examining headings, content, totals, spelling, line and page breaks, page layout, etc. Regression Testing: The tester ensures that generating the new report does not adversely affect existing report generation. System Testing: The tester verifies the setup for the new report’s distribution and that there is ample space for report storage. Acceptance Testing: After the new report has been tested and included in production, but prior to sending it to a client, an internal tester (such as a Business Analyst or an internal user) examines the report. Alternatively, developers or QA may work with a representative client to confirm that the report includes all the necessary data, is formatted as expected, and so forth. |
| Page 7 of 9 | < Previous Page 1 2 3 4 5 6 7 8 9 Next > |
Copyright © 1996-2012, Paragon Application Systems
