Black box testing: Internal system design is not considered in this type of testing. Tests are based on requirements and functionality. technical skills or programming knowledge is not essential

 

White box testing: This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.

 

Unit testing: Testing of individual software components or modules typically done by the programmer and not by testers as it requires detailed knowledge of the internal program design and code may require developing test driver modules or test harnesses.

 

The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. A unit test provides a strict, written contract that the piece of code must satisfy.

 

Incremental integration testing: Bottom up approach for testing i.e. continuous testing of an application as new functionality is added; Application functionality and modules should be independent enough to test separately, done by programmers or by testers.

 

Integration testing: Testing of integrated modules to verify combined functionality after integration. Modules are typically code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

 

Types of integration testing are:

 

1.      Big Bang:

 

In this approach, all or most of the developed modules are coupled together to form a complete software system or major part of the system and then used for integration testing. The Big Bang method is very effective for saving time in the integration testing process. However, if the test cases and their results are not recorded properly, the entire integration process will be more complicated and may prevent the testing team from achieving the goal of integration testing.

 

2.      Bottom Up

 

All the bottom or low-level modules, procedures or functions are integrated and then tested. After the integration testing of lower level integrated modules, the next level of modules will be formed and can be used for integration testing. This approach is helpful only when all or most of the modules of the same development level are ready. This method also helps to determine the levels of software developed and makes it easier to report testing progress in the form of a percentage.

 

 

Functional testing: This type of testing ignores the internal parts and focus on the output is as per requirement or not. Black-box type testing geared to functional requirements of an application.

 

System testing: Entire system is tested as per the requirements. Black-box type testing that is based on overall requirements specifications, covers all combined parts of a system.

 

End-to-end testing: Similar to system testing, involves 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.

 

Smoke testing:

• Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
• A smoke test is scripted, either using a written set of tests or an automated test
• A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
• Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification).
• Smoke testing is normal health check up to a build of an application before taking it to testing in depth.

 

Sanity testing:

• A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
• A sanity test is usually unscripted.
• A Sanity test is used to determine a small section of the application is still working after a minor change.
• Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
• Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

 

Regression testing: Testing the application as a whole for the modification in any module or functionality difficult to cover all the system in regression testing so typically automation tools are used for these testing types.

 

Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements. User or customers do this testing to determine whether to accept application.

 

Load testing: It's a performance testing to check system behavior under load. Testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system’s response time degrades or fails.

 

Stress testing: System is stressed beyond its specifications to check how and when it fails performed under heavy load like putting large number beyond storage capacity, complex database queries, continuous input to system, or database load.

 

Performance testing: Term often used interchangeably with ’stress’ and ‘load’ testing to check whether system meets performance requirements. Use different performance and load tools to do this.

 

Usability testing: User-friendliness check. Application flow is tested, Can new user understand the application easily, Proper help documented whenever user stuck at any point. Basically system navigation is checked in this testing.

 

Install/uninstall testing: Tested for full, partial, or upgrade install/uninstall processes on different operating systems under different hardware, software environment.

 

Recovery testing: Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

 

Security testing: Can system be penetrated by any hacking way. Testing how well the system protects against unauthorized internal or external access. Check if system database is safe from external attacks.

 

Compatibility testing: Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above.

 

Comparison testing: Comparison of product strengths and weaknesses with previous versions or other similar products.

 

Alpha testing: In house virtual user environment can be created for this type of testing. Testing is done at the end of development. Still minor design changes may be made as a result of such testing.

 

Beta testing: Testing typically done by end users or other final testing before releasing the application for commercial purposes.

 

Mutation testing - a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.