Hi friends this is Samar from software testing material comm in this video we are going to see whether the testers write test cases for all the types of testing or not as per is dqb there are 4 software test types namely functional non functional structural and change related some of the testing types come under functional testing type they are smooth testing and santé testing and.
Then coming to non functional testing type some of the testing types come under this they are performance testing load testing reliability testing stress testing usability testing localization and globalization structural testing is also known as white box testing and coming to the fourth testing type that is changed later regression and retesting commander this testing type.
Let's see do the testers really write test cases for all the types of testing here I am going to give a short note on some of the testing types and I also specify whether we write test cases or not I will confine myself to the widely user testing types in this video first smoke testing smoke testing is a type of testing which will be done to verify whether the raised build is testable or.
Not this is just to test whether the build which was released by development team is testable so we just test the basic features like login to do smoke testing we pick up the test cases which we have already written we do not write test cases particularly to do smoke testing next sanity testing santé testing will be done during the release phase to verify the main functionalities.
Of the application without going deeper to do this we pick up the test cases which we have already written same as a smoke testing and we don't write test cases particular linked to do Santee testing functionality testing we do test each and every feature of the software application to make sure that the each feature is behaving as prepared in the.
Requirement document to do functionality testing we do write test cases next integration testing integration testing is the process of testing the interface between two software units to do integration testing we do write test cases system testing testing the fully integrated application to ensure that the application works as intended or not to row system testing we have to write.
Test cases acceptance testing this is done by the end users along with the testers to validate the functionality of the application most probably acceptance testing will be done by customers so they may write test cases to do acceptance testing next compatibility testing it is to deploy and check whether the application is working as expected in a different.
Combination of environmental components test cases which were already written will be used to do compatibility testing ad hoc testing ad hoc testing is quite opposite to the formal testing it is an informal testing time in ad hoc testing testers randomly test the application without following any documents and test design techniques so we do not write any test cases for ad hoc testing.
Performance testing performance is concerned with achieving response times throughput and resource utilization levels that made the performance objectives of the product even though we use tools like lode runner we pick up some scenarios and write test cases to do performance testing performance testing test cases are not similar to functionality.
Think test cases usability testing to verify whether an application is user friendly or not main focus will be on look and feel of the application we follow a check list to test the look and feel of the application so we don't write specific test cases to do usability testing next accessibility testing to verify whether a user is able to use it comfortably or not we follow a.
Checklist to test the look and feel of the application same like usability testing so we don't try specific test cases to do accessibility testing reliability testing in terms of reliability testing we do perform testing on the application continuously for long period of time in order to verify the stability of the application we don't write manual test cases to do.
Reliability testing we use automation tools to do this by picking up some scenarios regression testing repeated testing of an already tested program after modification to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software components we use already written test cases to do.
Regression testing so we don't write specific test cases to do regression testing next Z testing we do retesting to ensure that the defects which were found and posted in the earlier build per fixed or not in the current build we don't write test cases to do retesting we use bug report to do retesting recovery testing we do recovery testing to determine how quickly the system.
Could recover from crashes to do recovery testing we write test cases globalization testing globalization is a process of designing a software application so that it can be adapted to various languages entry agents without any changes to do globalization testing we write test cases and last localization testing localization is a process of adapting.
Globalization software for a specific region or language by adding local specific components s we write test cases to do localization testing thank friends if you have any queries please comment below if you did enjoy this video they short to like the video don't forget to subscribe this channel by clicking the subscribe button I will see you soon in the next video thank you.
Have a good day you