1. Commercial Database Applications Testing

2. Test Plan Testing Strategy Testing Planning Testing Design (covered in other modules) Unit Testing (covered in other modules) System Testing System Integration Testing Acceptance Testing Regression Testing Negative Testing

3. Testing Strategy Objectives: Vary depending on the project scenario Ensure that all tests to be performed have been identified Formal processes and procedures have been developed to cover all test cases

4. Evaluation Criteria Testing Strategy Testing strategy should include the following: An outline of the aims and objectives agreed with the business and IT management Detailed testing scenarios to be performed Roles and responsibilities assigned to each member The approach the organisation is going to follow to ensure the testing phase is addressed accordingly Any requirements, either organisation specific or regulatory which must be implemented during the testing phases

5. Testing Planning Objectives Ensures that an implementation plan is developed to cover Operational testing function Done at the beginning of the software development.

6. Evaluation Criteria When designing overall test plan consider stages Requirements stage Specification stage Design Stage Implementation Stage Operational testing Post Implementation review

7. Design & Unit Testing Covered in: CS22120 Programming Modules

8. System Testing Objectives Tests system in its entirety Ensures that the business function for which it was originally intended is being met Functional and performance testing only complete and precise as designed from the design requirements

9. Evaluation Criteria Systems Testing Checklist headings Function System should meet specified requirements and hence supports business requirements Load/Stress Software should be tested at varying loads Volume High volumes of input data should be run under continuous load conditions have been entered Hardware configuration and portability Software should operate correctly across various hardware configurations

10. Evaluation Criteria Systems Testing cont… Database Loading and data conversion Security Security features should ensure access, integrity and recovery features operate as expected Performance System should be operating as required under peak and continuous loads Availability IT service meets reliability objectives. If not, time taken to repair / downtime should be measured Race Conditions Entering transactions out of sequence to identify whether software reacts correctly

11. System Integration Testing Objectives Designed to confirm: All coding changes addressed to improve business critical functions operate correctly Multiple applications or systems simultaneously

12. Evaluation Criteria Systems Integration Testing Integration Testing include: Point to Point Very accurate and timely transmission of data between systems End to End Testing Performed when a system is a chain has been replaced or modified

13. Acceptance Testing Objectives: After system testing and integration testing To provide assurance that all system changes and performance issues have been identified during previous test stages Design changes meet original system / user specifications Get Sign Off

14. Evaluation Criteria Acceptance Testing Ideally carried after sign-off of system and integration testing have been completed Acceptance testing procedures should demonstrate: To users and computer operations staff system as installed meets the contract conditions and/or acceptance test criteria such that the user is prepared to authorise a system acceptance document. The software does not affect either the functions or service levels of other IT services.

15. Regression Testing The objective is to Replicate system transactions and processes to ensure / verify that the “optimised/smarter” code functions correctly Ensure no impact on any other modules within the overall system and therefore created further potential costly errors

16. Negative Testing Used in all types of testing It identifies how a system responds to incorrect or inappropriate information being included within a text or numeric field. Performed to ensure that the system is able to handle inconsistent information