Types of Testing

Types of Testing:

Unit testing: it is a white box testing conducted by developer. It is used to test most micro scale of testing to test particular function or code modules.

Unit: Smallest testable piece of software.
Unit testing done to show that the unit doesn’t satisfy the functional specification and /or its implemented structure doesn’t match the intended design structure.

Smoke Testing: it is used to test or validate the every basic functionality of the system.

Or

Smoke Testing: It is an initial type of testing once testing team gets a build needs to do the BVT (Build verification testing) or smoke testing for verifying the major functional component of the build. This has to be done based on the requirement.

Functional Testing: It is used to test each and every module is functionally stable entire module is tested by functional testing.

Regression Testing: testing to ensure that code changes have not had an adverse effect to the other module or an existing function.

Re -Testing: Testing in which one will perform testing on the same function again and again with multiples sets of data in order to come to a conclusion whether functionality is working fine or not.

Integration Testing: is the phase of software testing in which individual modules are combined and tested as a group. It follows unit testing and proceeds system testing.
Different types: big bang, top down, button-up.

System Testing: System is a big component.
Testing that attempts to discover defects that are properties of the entire rather than of its individual components.
Concern: Issues, behavior that can only be exposed by testing the entire integrated system (e.g. performance, security, recovery).

Stress Testing: Testing system functionality while the system is under unusually heavy or peak load. It is carried out at high stress environment. This requires that you make some prediction about expected load levels of your website.

Load Testing: Testing an application under heavy load such as the testing of a website under a range of loads to determine at what point the system response time degrades or fails.

Performance Testing: is conducted to indentify the operating condition where system exhibits the best response time.

Volume Testing: is done to find weakness in the system w.r.t its handling of large amount of data during short time periods.

Usability Testing: Usability means that system are easy and fast learn, efficient to use, easy to remember, cause no operating errors and offer a high degree of satisfaction for the user.
Usability means bringing the usage perspective into focus the side towards the user.

Security Testing: Testing how well system protects against unauthorized internal or external users will full damage etc… This type of testing may requires sophisticated testing techniques.

Alpha Testing: Testing of an application when development is nearly completion minor design changes may still be as result of such testing.
Typically done by end user or other not by programmers or testers.

Beta Testing: Testing when development and testing are essential completed and final bugs and problems need to found before final release. Typically done by end-user or other not by programmers.

UAT: Software is handed over to the user in order to find out, if the software meets the user expectation and work as it’s expected. This is the final testing conducted before the customer accepts the products.