|
Software Testing Methods
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
(Continued from previous part...)
FUNCTIONAL SYSTEM TESTING TECHNIQUES
Control Testing Technique :
|
Background
|
" One half of total system development effort is directly attributable to controls.
" Controls include:
Data validation
File integrity
Audit trail
Back up and recovery
Documentation.
Other aspects of system related to integrity
" Control is system within a system.
" Control looks at the totality of the system.
|
|
Usage
|
" Control is a management tool to ensure that processing is performed in accordance to what management desire or intents of management.
|
|
Objectives
|
" Accurate and complete data
" Authorized transactions
" Maintenance of adequate audit trail of information.
" Efficient, effective and economical process.
" Process meeting the needs of the user.
|
|
How to Use
|
" To test controls risks must be identified.
" Develop risk matrix, which identifies the risks, controls; segment within application system in which control resides.
" Testers should have negative approach i.e. should determine or anticipate what can go wrong in the application system.
|
|
When to use
|
" Should be tested with other system tests.
|
|
Examples
|
" file reconciliation procedures work
" Manual controls in place.
|
Parallel Testing Technique :
|
Usage
|
" To ensure that the processing of new application (new version) is consistent with respect to the processing of previous application version.
|
|
Objectives
|
" Conducting redundant processing to ensure that the new version or application performs correctly.
" Demonstrating consistency and inconsistency between 2 versions of the application.
|
|
How to Use
|
" Same input data should be run through 2 versions of same application system.
" Parallel testing can be done with whole system or part of system (segment).
|
|
When to use
|
" When there is uncertainty regarding correctness of processing of new application where the new and old version are similar.
" In financial applications like banking where there are many similar applications the processing can be verified for old and new version through parallel testing.
|
|
Examples
|
" Operating new and old version of a payroll system to determine that the paychecks from both systems are reconcilable.
" Running old version of application to ensure that the functions of old system are working fine with respect to the problems encountered in the new system.
|
Error - Handling Testing Technique :
|
Background
|
" Pre determination of Error handling features is the basic difference between Automated and manual systems.
" Manual System: can deal with problems as they occur.
" Automated Systems: Must pre program error handling.
|
|
Usage
|
" It determines the ability of applications system to process the incorrect transactions properly
" Errors encompass all unexpected conditions.
" In some system approx. 50% of programming effort will be devoted to handling error condition.
|
|
Objectives
|
" Determine:
" Application system recognizes all expected error conditions.
" Accountability of processing errors has been assigned and procedures provide a high probability that errors will be properly corrected.
" During correction process reasonable control is maintained over errors.
|
|
How to Use
|
" A group of knowledgeable people is required to anticipate what can go wrong in the application system.
" It is needed that all the application knowledgeable people assemble to integrate their knowledge of user area, auditing and error tracking.
" Then logical test error conditions should be created based on this assimilated information.
" The error handling testing technique should test -
Error
Processing of error
Control condition
Reentry of condition is proper or not.
" The iterative process should be used where first the errors in the system trapped should be corrected and then the corrected system should be re-tested to check the authenticity of application operation and to complete the error handling testing cycle.
" Tester should think negatively to trap errors.
" Testers should determine how the system should fail so that they can test to determine if the software can properly process the erroneous data.
|
|
When to use
|
" Throughout SDLC
" Impact from errors should be identified and should be corrected to reduce the errors to acceptable level.
" Used to assist in error management process of system development and maintenance.
|
|
Examples
|
" Create a set of erroneous transactions and enter them into the application system then find out whether the system is able to identify the problems.
" Using iterative testing enters transactions and trap errors. Correct them. Then enter transactions with errors, which were not present in the system earlier.
|
(Continued on next part...)
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
| 