Types of Software Testing

What is smoke testing?

Testing is done when the build/application is ready to test and deployed in the test servers / environments. This is an adhoc kind of testing to cross check and make sure the functionalities which are important in the application are working as expected without throwing any server errors or exception errors.
This is a kind of check on developers to make sure they do unit testing from their side when releasing the build to testing.

What is Functional testing?

Testing each and every function which are in scope of testing in the application and make sure it is working as per the requirement (as per approved requirement document).

What is Integration testing?

Testing whether all the modules are combined or not and together working successfully as defined in the requirement document. Generally issues come when there are multiple developers working on the task. Sometimes developers may take the code which is not the updated or may forget to deploy the changes that are made by the other developer.

What is Regression testing?

1. When a new functionality or a feature is added in the application, testers need to make sure that the newly added feature / functionality does not break the other functionalities of the application.
2. Or when defects (bugs) are fixed by the development team, testers need to make sure that the bug fix made by the developer has not broken the other functionalities in the application.

What is Retesting?

Testing is done on the resolved bugs. When testers complete testing the build, testers will log the bugs in bug tracking tool. Developer will fix the bugs and release them again to test the bugs. Now its tester who retests the bug and close if that works fine or re-open it if it is not working as expected.

What is System testing?

Black box type testing that is based on overall requirements specifications; covers all combined parts of a system.

What is End-to-end testing?

Similar to system testing; the ‘macro’ end of the test scale; 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.

What is Black box testing?

Tests are performed based on requirements and functionality and performed by a Test Engineer who will not have any coding knowledge. Testers will test the application with the requirements that are defined and reports bugs if there are.

What is White box testing?

To perform a white box testing, testers should have knowledge on the internal logic of the application. Tests are performed based on coverage of code and conditions.
There are few scenarios where a tester also needs to perform white box testing to check if the code is implemented as per requirement.
There may be no effect to the front end or to any functionality after implementing the code. But the code is required for tracking for internal purposes of client or may be reflections will be in third party applications where you cannot perform testing activities.

In these scenarios we need to check for the code if the code if that is implemented

What is Usability testing?

Testing for ‘user-friendliness’ of the application. Clearly this is subjective, and will depend on the targeted end-user or customer.

What is Load testing?

Testing the user’s response time with number of users using same single business scenario of the same application at the same time.

What is Performance testing?

Testing the user’s response time with number of users using multiple business scenarios of the application at the same time.

What is Stress testing?

The application is tested against heavy load such as complex numerical values, large number of data inputs, large number of request and queries etc. which checks for the stress/load the applications can withstand.

What is User acceptance testing (UAT)?

The application is handed over to the client in order to check if the software meets his/her expectations and works as expected. Generally UAT testing is done by the clients. Once the client confirms that there are no issues in UAT, then application will move to Live.

What is Acceptance testing?

Final round of testing based on specifications of the end-user or customer, or based on use by end –users/customers over some limited period of time.

What is Alpha testing?

Testing the application when development is almost near to completion. Minor design changes may still be made as a result of such testing. Normally done by end – users or others, not by programmers or testers who involved in the development of the application.

What is Beta testing?

Testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Normally done by end-users or others, not by programmers or testers who involved in the development of the application

Software Testing: 

Add new comment