System testing

System Testing. SYSTEM TESTING is a level of software testing where a complete and integrated software is tested. The purpose of this test is to evaluate the system's compliance with the specified requirements. system testing: The process of testing an integrated system to verify that it meets specified requirements.

1. SYSTEM TESTING BY G.KARTHIGA M.SC INFOTECH NADAR SARASWATHI COLLEGE OF ARTS &SCIENCE,THENI

2. System testing involves two kinds of activities: 1. integration testing and 2.acceptance testing. Strategies for integrating software components into a functioning product include the bottom-up strategy, the top-down strategy, and the sandwich strategy . Acceptance testing involves planning and execution of functional tests, performance tests, and stress tests to verify that the implemented system satisfies its requirements. INTRODUCTION

3. Complete software system should be developed Unit testing must be completed Integration testing must be completed Specifications for the product have been completed Test scripts and schedules are ready ENTRY CRITERIA FOR SYSTEM TESTING

4. Application meets all the document requirements and functionalities Defects found during system testing should be fixed and closed All the test cases for the system should be executed No critical defects should be opened EXIT CRITERIA FOR SYSTEM TESTING

5. There are more than 50 types in system testing . The mainly using types are mainly using types are: 1. Usability testing 2. Stress testing 3. Regression testing 4. Functional testing 5. Load testing 6. Sanity testing & 7. Security testing TYPES OF SYSTEM TESTING

6. Bottom-up integration consists of unit testing, followed by subsystem testing, followed by testing of the" entire system. Unit testing has the goal of discovering errors in the individual modules of the system. A subsystem consists of several modules that communicate with each other through well-defined interfaces. Normally, a subsystem implements a major segment of the total system. INTEGRATION TESTING

7. The necessity to write and debug test harnesses for the modules and subsystems, and the level of complexity that results from combining modules and subsystems into larger and larger units. The extreme case of complexity results when each module is unit tested in isolation and all modules are then linked and executed in one single integration run. DISADVANTAGES OF BOTTOM-UP TESTING

8. System integration is distributed throughout the implementation phase. Modules are integrated as they are developed. Top-level interfaces are tested first and most often. The top-level routines provide a natural test harness. for lower-level routines. Errors are localized to the new modules and interfaces that are being added. TOP-DOWN INTEGRATION OFFERS SEVERAL ADVANTAGES:

9. Top-down integration starts with the main routine and one or two immediately subordinate routines in the system structure. Top-down integration requires the use of program stubs to simulate the effect of lower-level routines that are called by those being tested. TEST MAIN; STUBS FOR GET, PROC, PUT ADD GET; TEST MAIN, GET ADD PROC; STUBS FOR SUB 1 .SUB 2 ADD PUT; TEST MAIN, GET, PROC, PUT ADD SUB1 TEST MAIN, GET, PROC, PUT, SUB1 . ADDSUB2 Figure 5.5 Top-down integration TEST MAIN, GET, PROC, PUT, SUB 1, SUB2 testing strategy. integrated top-down integration testing. Top-down

10. SYSTEM TESTING VS INTEGRATION TESTING SYSTEM TESTING From requirement specification No visibility of code structure It is a high level testing The complete system is configured in a controlled environment INTEGRATION TESTING From interface specification Visibility of integration structure It is a low level testing Test cases are developed with the express purpose of exercising the interface exercising the interface between components

11. SYSTEM TESTING PROCESS

12. PRINCIPLES OF SYSTEM TESTING Identifies new faults that may have been introduced as current one are being corrected Verifies a new version or release still performs the same functions in the same manner as an older version or release

13. Compares the system’s actual performance with its requirements Develops test cases based on the requirements document FUNCTION TESTING

14. Used to examine the calculation the speed of response the accuracy of the result the accessibility of the data Designed and administrated by the test team PERFORMANCE TESTS

15. Enable the customers and users to determine if the built system meets their needs and expectations Written, conducted and evaluated by the customers ACCEPTANCE TESTS