Exploratory Testing
When the test is characterized by poorly written specification documentation, and/or a short time for execution then manual testing is, preferable. Exploratory testing requires tester’s knowledge, creativity, analytical skills, and experience. Basically, we need human skills to execute the testing process in this scenario which is possible by executing tests manually.
Usability Testing
In usability testing, testers need to measure how user-friendly, efficient, or convenient the software or product is for the end users. This again requires human intuition and experience and cannot be performed by tools and has to be strictly supervised manually. So a manual approach is preferable.
Black-Box Testing
As the name suggests in black-box testing the tester does not have knowledge about the code or structure of the application. He just interacts with the application and tests the functional and non-functional behavior of the application. There are various black-box techniques that can be used by the tester to find bugs and defects.
White-Box Testing
In white-box testing, tester knows about the code and structure of the application. Hence this type of testing is often known as glass box testing. Mostly, this type of testing is used by developers to perform unit testing. There are various white-box techniques that can be used by the tester to find bugs and defects.
Unit Testing
Unit Testing is a way of testing the smallest piece of code referred to as a unit that can be logically isolated in a system. It is mainly focused on the functional correctness of standalone modules. A unit can be almost anything you want it to be – a specific piece of functionality, a program, or a particular method within the application.
Integration Testing
Its performed after unit testing when different units, components, and modules of the software are integrated together. The main purpose here is to verify the functionality, stability, and reliability of the modules. The focus of integration testing is to check the correctness of communication among all the modules.
System Testing
System testing is the next step after integration testing. It is carried out on a complete, fully integrated software product to evaluate the behavior of the system and examine the full working of an integrated software computer system against requirements. There are various system testing techniques like functionality, performance, scalability, stress, and regression testing.
Acceptance Testing
User Acceptance Testing is the formal testing that is performed based on user requirements and function processing. This type of testing covers end-user real-world scenarios. It needs to be done correctly because it will provide you with the result on the basis of which software product will be either approved or rejected by senior management.
Security Testing
Security testing of any system is about searching for all the possible loopholes and weaknesses of the system which might result in a breach in the security.
For Example, it can be a loss of information, revenue, or the reputation of the organization. The main focus of this testing is to keep your software away from any threats or vulnerabilities so that your system does not get exploited. It will help you to detect such problems and solving them.
Load Testing
Load Testing is a type of Performance Testing that determines the performance of the system under real life conditions. It examines how the system behaves during normal and high loads and determines if a system, piece of software, or computing device can handle high loads given a high demand of end users.
Load Testing is used to identify the following :
- The maximum operating capacity of an application
- Determine whether the current infrastructure is sufficient to run the application.
- Sustainability of application with respect to peak user load.
- Number of concurrent users that an application can support, and scalability to allow more users to access it.
RE-TESTING
Retesting means testing the functionality or bug again to ensure the code is fixed. If it is not fixed,
Defect needs to be re-opened. If fixed, the Defect is closed.
Cross Browser Testing
It is very necessary to check the compatibility and performance of the websites on different browsers and operating systems as the behavior of the website differs from browser to browser.Cross-browser compatibility is the ability of a website or web application to function across different browsers and operating systems.
Data Driven Testing
In Data Driven Testing, We test the same functionality with the different set of data. Simple example can be testing the login functionality with different set of Credentials.
automationworld.home.blog 