Types of Testing		Description
Database Testing		The most ‘micro’ scale of testing to test particular functions or tables which are links to modules. It is performed during the coding stage of the project by developers, and requires detailed knowledge of the internal program design and code (white-box) table structure, SQL Statements, PLSQL, Triggers.
System testing		Black-box type of testing that is based on overall requirement specifications; covers all combined parts of a system. This testing verifies the operational integrity of the application changes for each component system in the project. It focuses on testing the changes made to each system in isolation of each other.
Integration testing		An orderly progression of testing of incremental pieces of the software program in which various software and hardware elements integrate, and are combined and tested until the entire system shows compliance with the program design, capabilities, and requirements of the system.
User Acceptance testing		Determining if the software is satisfactory to an end-user or customer, in that it meets all of the user requirements. From a user perspective, this test validates the system’s ability to produce correct outputs, accept inputs, and produce expected results.
End-to-End testing		Testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
Regression testing		Re-testing after fixes or modifications of the software or its environment. It ensures that the functionality of the system that existed prior to the enhancements or defect fixes has not been altered or affected. Automated testing tools can be especially useful for this type of testing.
Embedded		This is a special purpose computer system designed to perform a dedicated function like MP3 player, AC, DVD Player, Video game consoles. Testing Embedded process using multiple Temb FMEA method is- Grapesoft expertise.
Telecom testing		Testing which covers VOIP, Handset, Application, with specific Testing Techiques.
Security testing		Testing how well the system protects against unauthorised internal or external access, willfull damage, etc; may require sophisticated testing techniques Tests are performed that attempt to break the system’s security, such as access by unauthorised users.
Performance testing		This is technical testing to verify that the changes introduced by the project to traffic volumes and system/interface throughout have not degraded processing performance and response times.
Load testing		This testing subjects the application/system under test to virtual user loads beyond the anticipated or target loads goal is to determine and ensure that the system functions properly and the maximum loads do not compromise any designated sensitive elements.
Stress testing		Stress testing intends to find error due to extended usage of the application under test, when the application is subjected to maximum virtual user loads for extraordinary periods of time. If the application functions adequately under these conditions, it can be assumed that it will function properly with a normal volume of work. This can help identify potential system failures.
Volume testing		Volume testing subjects the application under test to large amounts of data.The goal is to determine if the high volume limits can be obtained without degrading the performance of the application. This can be used to predict future production loads.
Limit testing		Limit testing is carried out for each of the documented application / system limits (such as memory, number of files open, number of users, etc). These tests are designed to investigate how the application/system reacts to maximal or nominal data to attain specified required limits.
Disaster and Recovery testing		Disaster testing is a mechanism that simulates problems in the production environment to test that alternative processing environments can be used. While it is not possible to simulate all environments into which an application system may be moved, verifying that it can transfer between two different environments provides a higher probability that other moves will not cause major complications.
Compatibility testing		Compatibility of existing data to a higher version of software being developed. This is especially true for packaged products where an enhancement should be compatible with the old data used by users.
Consistency testing		The data and results are verified to be consistent across the application. For example, the sales column in stock reports and the total sales in region wise reports must match.
Reliability testing		Testing for reliability requires periods of prolonged use at varying loading levels, or constant values at peak levels. If the reliability level (mean time between failures) is desired to be for long periods such as years, the test is conducted for short periods and the results are extrapolated into years.
Useability/Sociability testing		Testing for ‘user-friendliness’ such as consistency, ability to navigate through the applications, and procedural aspects of the system. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used.
User Interface testing		User interface testing is intended to verify the synchronisation of the user manuals, on-line help, etc. with the Software Requirements Specifications. It determines where the user manuals do not describe the interface correctly or in sufficient detail.
Installation testing		The ease and consistency of installation is checked by performing installation testing. Wherever installation counts are applicable, the number of installations specified (or more) is tested. Uninstalling the system is likewise covered. Migration of data from older versions to new versions is verified. If the software is to work on multiple platforms, then all the platforms or, as a minimum, the critical platforms are also tested.
Conversion testing		Testing to validate that existing data converts or is given a new value as a result of the introduction of a new algorithm.
Platform testing		Testing that the software being released acts consistently across different platforms such as Windows XP, Windows NT, etc.
Product testing		Develop a set of tests based on your requirements and standards, existing tests, advertised product features, and our own experience in testing similar products and run the tests using a variety of hardware and operating system configurations.