Functional System Testing Techniques
Explain following Functional System Testing Techniques.
1. Requirements Testing Technique
2. Regression Testing Technique
FUNCTIONAL SYSTEM TESTING TECHNIQUES -
1. Requirements Testing Technique:
| Usage | * To ensure that system performs correctly * To ensure that correctness can be sustained for a considerable period of time. * System can be tested for correctness through all phases of SDLC but incase of reliability the programs should be in place to make system operational. |
| Objectives | * Successfully implementation of user requirements * Correctness maintained over considerable period of time * Processing of the application complies with the organization’s policies and procedures. * Secondary users needs are fulfilled - Security officer DBA Internal auditors Record retention Comptroller |
| How to Use | * Test conditions created These test conditions are generalized ones, which becomes test cases as the SDLC progresses until system is fully operational. Test conditions are more effective when created from user’s requirements. Test conditions if created from documents then if there are any error in the documents those will get incorporated in Test conditions and testing would not be able to find those errors. Test conditions if created from other sources (other than documents) error trapping is effective. * Functional Checklist created. |
| When to use | * Every application should be Requirement tested * Should start at Requirements phase and should progress till operations and maintenance phase. * The method used to carry requirement testing and the extent of it is important. |
| Examples | * Creating test matrix to prove that system requirements as documented are the requirements desired by the user. * Creating checklist to verify that application complies to the organizational policies and procedures. |
2. Regression Testing Technique:
| Background | * One segment of system is developed and thoroughly tested. * Another segment is changed which has disastrous effect on the tested segment. * The implemented change, new data or parameters have created change in the already tested segment. |
| Usage | * All aspects of system remain functional after testing. * Change in one segment does not change the functionality of other segment. |
| Objectives | * Determine - system documents remain current System test data and test conditions remain current. Previously tested system functions properly without getting effected though changes are made in some other segment of application system. |
| How to Use | * Test cases, which were used previously for the already tested segment is, re-run to ensure that the results of the segment tested currently and the results of same segment tested earlier are same. * Test automation is needed to carry out the test transactions (test condition execution) else the process is very time consuming and tedious. * In this case of testing cost/benefit should be carefully evaluated else the efforts spend on testing would be more and payback would be minimum. |
| When to use | * When there is high risk that the new changes may effect the unchanged areas of application system. * In development process: Regression testing should be carried out after the pre-determined changes are incorporated in the application system. * In Maintenance phase : regression testing should be carried out if there is a high risk that loss may occur when the changes are made to the system |
| Examples | * Re-running of previously conducted tests to ensure that the unchanged portion of system functions properly. * Reviewing previously prepared system documents (manuals) to ensure that they do not get effected after changes are made to the application system. * Obtaining printout of data dictionary to ensure that the data elements reflect the changes being incorporated. |
| Disadvantage | * Time consuming and tedious if test automation not done. |
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.