In general, Testing is in order to check or evaluating the software which is created by the developer is working as per the customer requirement specification is called testing, If the Tester noticed any deviation in the functioning of the software which is created by the developer is called Issue or Bug or Defect. This unexpected behaviour of the software is also called as Error.
Testing the software which is created by the developer is working as per the customer requirement specification by without using any Automation Tools, there are various kinds of testing methods available in Manual Testing yet, Manual testing plays an important role in the Software testing even for a company which has automated most of its task successfully. In this post, we will discuss in brief about various Testing types:
Types of Testing
⁃ White Box Testing (WBT)
⁃ Black Box Testing (BBT)
⁃ Functional Testing (FT)
⁃ Integration Testing (IT)
⁃ System Testing (ST)
⁃ Acceptance Testing (AT)
⁃ User Acceptance Testing (UAT)
⁃ Unit Testing
⁃ Performance Testing
⁃ Usability Testing
⁃ Soak Testing
⁃ Adhoc Testing
⁃ Smoke Testing
⁃ Sanity Testing
⁃ Regression Testing
⁃ Alpha Testing
⁃ Beta Testing
⁃ Internationalisation Testing
⁃ Localisation Testing
⁃ Statement Coverage
⁃ Condition Testing
⁃ Stress Testing
⁃ Mutation Testing
White Box Testing
-Testing is done by the developer, they can do the testing in the source code of the application which is created is working properly or not.
Black Box Testing
-Testing is done on the application which is created by the developer is working properly or not is called black box testing, its done by the testing team or tester.
-Checking for the each and individual component of the software is working properly or not is called functional testing. Eg.login button.
-Checking for the communication happens from one module to another module in the software is called Integration testing. Eg.Login page to Welcome page
-Checking the software with different environments and its also testing it End to End. Eg.Login page to Logout page
-Checking whether the software created satisfies the customer requirements without any issue or not. This testing is done on by the tester within the company.
User Acceptance Testing
-Once the software is created by the company, the customer can do the testing in particular software in their place with their environment and specification. In order to ensure that the software satisfies their requirements and works as per their expectations.
-Unit testing, a testing technique using which individual modules are tested to determine if there are any issues with the developer himself. The main aim is to isolate each unit of the system to identify, analyse and fix the defects. Reduce Defects in newly developed features in the existing application and it’s often done by the programmer.
-Checking the Time taken for a particular application to respond and perform well under the expected workload is called performance testing.
-Checking the user-friendly nature of the application or software, flexibility in handling controls and ability of the system to meet its objectives.
-Applying a certain load over a particular period of time and test that how far the application is able to handle it perfectly.
-Adhoc Testing means testing is done without any proper planning and documentation, ad-hoc testing is the least formal test method.
-Testing that the given build by the developer in the testable format and also to ensure that the most important function of the software is working properly as per the requirement.
-Testing done when we do not have enough time to test is called sanity testing and it is also called surface-level testing to verify the most important functions and commands available in the product is works fine.
-Re executing all the test case which is created in the module wise structure is called regression testing and also ensures that the newly added feature does not affect the existing functionality of the application.
-Executing the failed test cases(i.e.)The issue which we have reported to the developer team is once got fixed we will do re-execute the failed test-cases and check the issue got fixed and its work as per the requirements is called Retesting.
-Testing the software which is created by the developer by setting the user environment within the company and do the testing by testing team and also calling the customer to the company, its also called as user acceptance testing.
-Testing is done on with the application by installing and checking whether it satisfies the customer requirements without any deviation in the requirement is called beta testing.
-Developing and Testing the internationalised software and its able to adapt for different countries with different languages is called internationalised software, we do testing in the internationalised software is called internationalisation testing.
-Adopting an internationalised software to the specific region and specific country is called localisation, testing that software is called localisation testing.
-Checking each and every line of the statement if it is working properly or not is called statement coverage.
-Checking the true or false conditions if it is working properly is called condition testing.
-Applying a load over than the desired load and checking how far the application able to handle is called stress testing.
-We purposely change the source code of the application which is created by the developer and do WBT. If the WBT get passed then the application which is created is totally wrong if the WBT gets failed the application which is created is 100% perfect, this kind of testing is called mutation testing.
In this blog, we have seen about the Testing types and hence it could be useful and I will be with another new topic in my next blog.