|
|
Electronic Payments Testing:
A Testing Terminology Primer
| Testing Class |
What |
When |
Who |
Integrated
Testing |
Testing of multiple, integrated units. Integration testing reveals defects in the interfaces and interactions of the various units of code. Ideally, after unit testing is completed, the tested units are integrated and tested in various combinations until all modules in the process have been tested. Testing can be conducted top-down (integrating and testing the highest-level units first and thus testing high-level logic and data flow), bottom-up (integrating and testing the utility-level units first) or in an umbrella fashion (which uses some aspects of both top-down and bottom-up testing to test along data flow paths). |
Any time there has been a change to or addition to the code. (Ideally after unit testing is completed.)
Would be performed multiple times as each unit is incorporated. May also be coupled with regression testing for the previously integrated and tested units as new units are added for integrated testing.
|
Developers and
QA testers
|
Functional
Testing |
Testing the functional capabilities of the component or system from the user's perspective, particularly as dictated by the functional design specifications and by industry standards - for example, ensuring the program works as described in the design specifications and includes all the specified menu options. Functional testing is distinguished from Acceptance testing in that Functional testing objectively determines that the required functionality is included, while Acceptance testing typically involves the user’s approval of the system. |
Any time changes are made to add or modify a feature or system. Initially, some testing may be done using a prototype before the final coding changes are complete. |
Developers (initially), but most often QA testers, Acceptance testers, and System testers (or other internal users). |
Copyright © 1996-2010, Paragon Application Systems
|
