Types of Testing

Maintenance Testing

Maintenance Testing is done on the already deployed software. The deployed software needs to be enhanced, changed or migrated to other hardware. The Testing done during this enhancement, change and migration cycle is known as maintenance testing. Once the software is deployed in operational environment it needs some maintenance from time to time in order(…)

Globalization Testing

In the current scenario of the global marketplace, it is very important to make software products which are sensitive to the different location and cultural expectations of users around the world. Most non-English-speaking customers have operating system in their native language and they expect that computer programs will not fail on their computers, also they(…)

Interoperability Testing

Interoperability means the capability of the software to interact with other systems/software’s or software components. Interoperability testing means testing the software to check if it can inter-operate with other software component, software’s or systems.

Exploratory Testing

As the name suggests exploratory testing is about exploring more into the software and finding about the software. In exploratory testing tester focuses more on how the software actually works, testers do minimum planning and maximum execution of the software by which they get in depth idea about the software functionality, once the tester starts(…)

Confirmation Testing or Re-testing

Confirmation testing is also known as re-testing. Confirmation Testing is done to make sure that the tests cases which failed in last execution are passing after the defects against those failures are fixed. For Example: Suppose you were testing some software application and you found defects in some component.

Usability Testing

Usability means the software’s capability to be learned and understood easily and how attractive it looks to the end user. Usability Testing is a black box testing technique. Usability Testing tests the following features of the software.

Smoke Testing

Smoke testing is done for the software in order to verify that the software is stable enough for further testing. it has a collection of written tests that are performed on the software prior to being accepted for further testing. Smoke testing “touches” all areas of the application without getting too deep, tester looks for(…)

Sanity Testing

When there are some minor issues with software and a new build is obtained after fixing the issues then instead of doing complete regression testing a sanity is performed on that build. You can say that sanity testing is a subset of regression testing. Sanity testing is done after thorough regression testing is over, it(…)

Beta Testing

Beta Testing is done after alpha testing. Testing done by the potential or existing users, customers and end users at the external site without developers involvement is know as beta testing. It is operation testing i.e. It tests if the software satisfies the business or operational needs of the customers and end users.

Alpha Testing

Alpha Testing is done to ensure confidence in the product or for internal acceptance testing, alpha testing is done at the developers site by independent test team, potential end users and stakeholders. Alpha Testing is mostly done for COTS(Commercial Off the Shelf) software to ensure internal acceptance before moving the software for beta testing.

Security Testing

Security Testing tests the ability of the system/software to prevent unauthorized access to the resources and data. Security Testing needs to cover the six basic security concepts: confidentiality, integrity, authentication, authorization, availability and non-repudiation. Confidentiality A security measure which protects against the disclosure of information to parties other than the intended recipient that is by(…)

Install Testing

Install Testing is done to ensure that the software and its components get installed successfully and function properly post installation. While doing Installation testing, test engineer should keep in mind the following points: Product Installer should check for the pre-requisites needed for the software. Product Installer should give user the default install location of the(…)