Software Testing Type

There are various type of Software Testing. Here i am provide you brief idea regarding these software testing type. Later i will provide you detailed description for your understanding.

Here i am listing all the type because you can find all definition in one page and it is easy for you guys to compare all the types.

• Black Box Testing: In this type of Testing, Testing team need not to be aware regarding the internal structure of the software. Testing Team do not need any knowledge regarding the code to perform this type of Testing. Testing team just focus on the requirement and the functionality. Testing team just focus over the actual result and matching that result with the expected result.

• White Box Testing: Another name of this testing is Glass Box Testing. Like s transparent glass everything is visible inside the glass. Just like in this type of Testing, Testing team need to know about the internal structure and code of the Software. Testing are based on the Code coverage, Branch coverage, Path coverage.

• Gray Box Testing: This testing is the combination of White Box Testing and Black Box Testing. In this testing, Tester have some knowledge about the code and based on this knowledge, Tester create the Test Case.  Now when application comes under testing then tester execute those test cases as a black box tester. So in Gray Box Testing , Tester create the Test Cases understand the code comes in category of White Box Testing and when Tester execute the Test cases then this comes under the category of Black Box Testing.

• Unit Testing: This type of Testing comes under white Box Testing and it is performed by the Developer. Unit is the smallest part of the Software . In this testing, Developer verified that the outcome of unit or component or code that he/she written matching with the expected result or not.

• Integration Testing: Integration Testing is next level of Testing after Unit Testing. In this type of Testing the component are combined and then, Tester test them to check the output of combined product and the interaction between the different component. In this type of Testing interaction between software and hardware also tested if hardware and software component have any relation. This comes under both White Box and Black Box Testing.

• System Testing: System Testing is the next level after Integration Testing. In this testing all part of software are combined and tested as per teh requirement of the Software. This comes under Black Box Testing.

• Acceptance Testing: Acceptance Testing generally done from client side to verify that the software meeting the requirement or not. In this testing client want to verify that is the software working as per his/her expectation. This testing comes under Black Box Testing.

• Functional Testing: This type of testing just to ensure the output as per the requirement mentioned in the detail proposal. In Function Testing, Test test the functional part of the software. In functional Testing, Tester do not have focus over the internal structure of the software. This testing comes under Black Box Testing.

• Graphical User Interface Testing: In GUI Testing, we verify the user interface of the software and to check this user interface with the specified requirement. User interface means the color, font, font size, Text format, Text Box, Radio Button, Checkbox, Buttons, icons, alignment, links , pop up , contents etc. 

• Usability Testing: In Usability Testing, we verify that the system should be easy to use for the end users. The Main Focus in this testing to make software easy to use, flexible and system should meet it's objective. Usability Testing done with end user perspective and this is the Non-Functional Testing type.  

• Alpha Testing : Alpha Testing is the type of Acceptance Testing. Alpha Testing occur when the development part is about to complete and some small design changes are happening. The main intention of Alpha Testing to check the complete software before release it to the customer or the end user. 

• Beta Testing: Beta Testing comes after the Alpha Testing. In Beta Testing, product is release outside from the organization ( Outside from the Testing Team) for the public users to find out the issues or fixes or feature which left from the developer and tester team within the organization. Beta Testing is the testing which is perform by the real world users in real environment and it is perform at client location or end user of the software.

• Smoke Testing: In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.

• Sanity Testing: Sanity Testing is perform when QA team received the build after fixes of minor bugs or some new functionality added. In Sanity Testing, QA team check that the bugs that generated in last build should be fix and due to those bug fixes there should be no new bugs generated. So in Sanity Testing first QA team check the regression testing and after regression testing QA team verify the previous bugs.

• Performance Testing: Performance Testing is the testing in which Test Team determine how the system will perform in terms of responsiveness and when the system will be overloaded. In Performance Testing , we validate or verify the scalability, reliability and how the system uses the available resources. These all are the quality attribute of the system.

• Load Testing: Meaning of Load Testing is to provide constantly or steadily  load for a software to check that how software is responding in increasing load without significant performance degradation. Load Testing is put load over the system to check the response. We increase the limit until the threshold limit. In Load Testing we determine the system limit in normal load and peak load limit of the system.

• Soak Testing: Also known as Endurance Testing. In this testing, we provide the continues significant load for significant time to test the application. Suppose you are testing a function in 1 hour and then you testing the same function for 3 hours so when more time then there may be chance of Memory Leaks issue. 

• Volume Testing: In this type of Testing, We put the huge load for the limited time to check the behavior of the Application. Suppose you want the Volume Test then you need to increase the size of the database so that it can accept the heavy load so in this testing we check the performance of database with increasing volume.

• Stress Testing: Stress Testing is the testing to verify the response/output of the software beyond the breaking point of the system.  Stress Testing, test team focus on robustness, availability and the error handling under the heavy load rather then correct behavior under normal circumstances. It is the type of non functional testing.

• Spike Testing: Spike Testing is the testing in which suddenly Test Team increase/decrease the load over the system by a varying number of users and then observing the behavior of the system. The Objective of this sudden increase of load to check weather performance will suffer, system get crash or it handled this sudden increase/decrease load.

• Scalability Testing : Scalability Testing is the non functional Testing. In this Testing we check the capability of the system in scale up or scale down. Scale Up and Scale down to means to check the capability of the system or Network to check the growing amount of work in order to accommodate that growth. In Scalability Testing we measure the system capability in terms of growing the workload per user, Growing the concurrent users or the size of the database.

• Configuration Testing: Configuration Testing is the testing type in which test team test the software with every combination of the supported Software and the hardware.  In configuration testing we define with the software guideline of supported version (Software and Hardware) in which software will work. We run all test cases with these combination to verify the result.

• Isolation Testing: In the Isolation Testing, Test team break the system in the different modules so that bug can be easily visible in the software.  We use Isolation Testing where bug is not spotted easily.

• Compatibility Testing: Compatibility Testing is the software non functional testing in which we check the relationship of the software with the computing environment. In Compatibility Testing, One can verify that how your software is working with the Operating Systems, Other Hardwares, Network and other devices.

• Positive Testing: In this type of testing, Test team always put the positive set of data in the input values to check the output and check the behavior of the application.  With input set the data the application should give the error when it is specified and should not provide an error when not specified. Suppose one input field which can only accept the value between 1-100. Now when we are trying to the value in between range it should not provide any error but when we trying to put the value out of the range it should shown an error. The intension of Positive Testing to check that software meeting the client requirement.

• Negative Testing: In Negative Testing, Test team check the software in Invalid set of data to use as input field and to check the output. The intention of Negative Testing is to ensure that the application should not respond the error which should not be the case. As per the example explain above if i put the value 101 then if is showing the error that value is not valid then it is fine but suppose it is accepting the value and later throw an exception then this fall under the category of bug which should be resolved. 

• Buddy Testing: In Buddy Testing, 2 members test the application together. In 2 members one from development team and other from Testing Team. They start testing together so for both it is good to develop the proper Test Cases and it is good to developer to fix the design issue earlier. This type of testing start after completion of Unit Testing.

• Pair Testing:  In Pair Testing, 2 testers work on same machine to find out defects. Both can share ideas. One Tester will execute the Test Cases and other will write the records of finding issues.

• Monkey Testing: In Monkey Testing, Test the application without any goal. As name applies like Monkey moves tree randomly. No one know on which tree Monkey will move. The testing is like same. Tester test the application randomly without any proper guild line. 

• End-To-End Testing: End to end Testing define that the flow of the software should be work as per the describe in the software requirement. End to end testing verifies that the for any input the right out put should be generated and that output used as a input to other system component to verifies the interaction between the component of the software.

• Accessibility Testing: Accessibility Testing is the testing which is verify that the person who have the disabilities is able to use the software or not. Disabilities may be difficulties with sight, hearing, movement , talking or mental disabilities etc.

• Ad Hoc Testing: Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.

• Regression Testing: When developer assign a new built for the QA team to test and QA team find some bugs in that build they assigned those bugs to the Dev Team to fix. Developer team fixes those bugs and assigned back for the QA team to test. Now QA team will verify the new build to check weather assigned bugs fixes or not and QA team need to validate the related areas of assigned bugs to verify that weather all previous functionality is working fine due to changes done on the software build.  In terms of definition Regression Testing is the type of testing which cover to verify the working functionality (functional and Non functional) that can be changed or wrongly working after enhancement and bug fixes.This is the Verification Method.

• Structural Testing: Structural Testing is the type of testing in which user should have the knowledge of the code because in this testing user need to check the structure of the system. Structural Testing is White Box Testing.

• Age Testing: Age Testing is the type of testing in which we check that how the software will perform in future, How the software performance going down as per the time passes, How the software dependencies will fall. This all comes under Age Testing.

• Requirements Testing: The testing in which Test Data, conditions and the procedure generated from the requirement, that testing is called Requirements Testing. Requirements Testing includes function and Non Functional Testing.