Types of testing 1.

Unit testing : It is usually done by developers It focuses on the smallest unit of software In this testing, particular unit of software is tested Individual components are tested to ensure that they operate correctly This particular unit is considered as a whole system and tested accordingly and is made bug free. 2. Integrated testing : It is usually done by developers In this technique, several units are integrated together to form a single system and the whole integrated system is tested It validates that multiple parts of the system interact according to system design It delivers portion of system ready for testing with other portions of the system. 3. System testing : Testing on the system is started Test cases are made according to the user and implemented Also, non-functional tests are made

 Functional and structural testing comes under system testing. 4. Functional testing : It is sometimes called as Black box testing because no knowledge of internal logic of the system is used to develop test cases In this technique, testing is done to check the functionality of software Functionality is tested as per functional requirements It is designed to ensure that system functional requirements and specifications are achieved. The process normally involves creating test conditions for use in evaluating correctness of the application Advantages It simulates actual system usage Does not make any structure assumptions Disadvantages Chances of missing logical errors in the software Does not make any structure assumptions Regression testing : It involves assurance that all aspects of an application system remain functional after testing

 The objective of this testing is to determine that the previously tested system functions properly after changes are introduced into the application system It also determines that the system test data and test conditions remain constant Regression testing is done to confirm the correct working of whole software after doing extra additions or changes in the basic software Software is tested again and again completely after each change. 5. Usability testing : It tests for the easy navigation controls or interfaces of the software As the designs of the web applications cannot be controlled, it should be tested for the usability. 6. Performance testing : It tests the capability of the system to perform the requested performance The characteristics that are normally tested are response time, execution time. For web applications, various conditions at client side, the number of users or what the users are doing with the application. 7. Stress testing :

 This is breaking of the application or the site in order to see how the system reacts It tests the system limitations to peak volume of data in a short time It determines whether system performs with expected output or not. 8. Load testing : This testing is done to measure the performance at a given load level to assure that the site works within the requirements It is used to estimate the number of users per time period, data transactions etc. 9. Volume testing : This test is performed to determine whether the program can handle the required volumes of data request This testing is done where the system is subjected to large volumes of data The creation of specific types of test data in order to test predetermined system limits to verify how system functions when those limits are reached or exceeded 10. Compatibility testing : It tests compatibility of the software with different operating systems, machine configurations or external database

 It is useful in case of web testing. 11. Configuration testing : It is used to determine whether the program operates properly when the hardware and software are configured in a required manner. 12. Reliability testing : It verifies that the system operates under stated conditions for a specified time period. 13. Serviceability testing : It tests working of the internal maintenance information such traces, diagnostic messages work properly 14. Installation testing : This test is used to identify the base in which procedure lead to incorrect results. It is an important testing type as it makes first impression on end user. 15. Parallel testing : This testing is for comparing the performance of the new system with the old one to be replaced The outputs of both the systems are thoroughly tested This testing is conducted to determine that the results of new application are consistent with the processing of the previous application or version of the application

 The objectives are to conduct redundant processing to ensure that the new version or application performs correctly demonstrates consistency and inconsistency between two versions of the same application system This testing requires that the same input data be run through two versions of the same application 16. Execution testing : It is designed to determine whether the system achieves the desired level of proficiency in a production status It determines the performance of system structure, optimum use of hardware and software 17. Recovery testing : It is done to test ability of the user to recover data or restart the application after failure It is used to ensure that the operations can be continued after a disaster The objectives of the recovery testing includes preservation of adequate backup data, locating backup data in secured location, documentation of recovery process, training of recovery personnel, development and availability of recovery tools 18. Operations testing :

 It is primarily designed to determine whether the system is executable during normal systems operations. It s specific objectives include determining the completeness of computer operator documentation, ensuring that necessary support mechanisms have been prepared and functions properly It evaluates the completeness of operator training, testing to ensure that operators can in fact operate the system 19. Sanity testing : The main concern in this testing is to see the basic functionality of all features of the software. 20. Compliance testing : It is performed both to ensure compliance to the methodology and to encourage & help IT professionals to comply with the methodology The objectives of this testing include determining that the system development and maintenance methodologies are followed It ensures compliance to departmental standards, procedures & guidelines, evaluating the completeness & reasonableness of application system documentation 21. Security testing : Security is the protection system that is needed for both secure confidential information and for competitive

purposes to assure third parties that their data will be protected This testing is designed to evaluate the adequacy of the protective procedures and countermeasures Security defects do not become as obvious as other type of defects The objective of this testing is to identify defects that are very difficult to identify Even failures in the security system operation may not be detected, resulting in loss or compromise of information without knowledge of that loss This is the testing of data security linked to directory set up, logins, firewalls and log files It is particularly important in web application area, as lot of personal information is filled up by customer which should be secured 22. Static and dynamic testing : Static testing refers to testing without running, that means examining and reviewing the software Dynamic testing is normally done by running and using the software. 23. Independent testing : Testing done by individuals other than those involved in the development of the product or system.

24.

Manual and automated testing : Manual testing is performed by people As there is greater reliance on people to analyze, document and develop computer system manually, the more it becomes necessary to test manually Automated testing is performed by computer The more automated the developmental process, the easier it becomes to automate the test process

25.

Requirement testing : It must verify that the system can perform its function correctly and that the correctness can be sustained over a continuous period of time The system can be tested for correctness throughout the life cycle, but it is difficult to test reliability until the program becomes operational The objectives of this testing are to see whether the requirements are implemented, whether correctness is maintained over extended period of time, whether application processing complies with organizations policies and procedures

26.

Error handling testing : It determines the ability of the application system to properly process incorrect transactions Errors encompass all unexpected conditions

 The objectives are to determine that the accountability for processing errors has been assigned & that the procedures provide a high probability that the error will be properly corrected It also determines that reasonable control is maintained over errors during the correction process. 27. Manual support testing : It involves all the functions performed by people in preparing data for and using data from automated applications The objectives are to verify that manual support procedures are documented and complete Determines that manual support responsibility has been assigned Determines that manual support people are adequately trained Determines that manual support and the automated segment are properly interfaced. 28. Intersystem testing : This test is designed to ensure that the interconnection between applications function properly This process is time consuming and costly The objectives are to determine that the proper parameters and data are correctly passed between applications

 Ensuring the proper coordination and timing of functions exist between the application systems Determines that the documentation for the involved systems is accurate and complete 29. Control testing : Controls include data validation, file integrity, audit trail, back up & recovery, documentation and other aspects of system related to integrity Control is a management tool to ensure that processing is performed in accordance with the intents of management Objective: 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. 30. Smoke testing : In this, the main concern is to see the basic functionality of important features of the software Thus by checking the basic functionality of the software, the next procedures of testing are done 31. Acceptance testing :

 These are final stages of testing before the system is accepted for the operational use It validates both the functional and non-functional needs of the software, which satisfies the user needs and system performance. The customer or end user usually performs it after the testing group has satisfactorily completed the usability, function and system testing It usually involves running and operating software in the production mode for a pre-specified period Types of acceptance testing Alpha testing : This is done at developer site by the customer. Developer records errors and usage problems. They are conducted under controlled conditions that are similar to the client side environment Beta testing : This is done at client side by the end user of the software. The developer cannot control the application environment. Customer records all the problems encountered and reports to developer at regular intervals. 32. Globalization Testing

It makes sure that the code can handle all international support without breaking functionality that would cause either data loss or display problems. Globalization testing checks proper

functionality of the product with any of the culture/locale settings using every type of international input possible. 33. Localization Testing

Localization testing checks how well the build has been translated into a particular target language.